Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计提醒

chief-editor-desicion主编决定

Agent Skill

chief-editor-desicion 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

22,509

周安装

957

GitHub Stars

公开资料未说明

下载量

7,886
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:chief-editor-desicion(主编决定)
来源仓库:https://github.com/teamolab/chief-editor-desicion
安装命令:
openclaw skills install chief-editor-desicion
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install chief-editor-desicion

简介

主编决策型 AI 代理,用于复杂判断与信息筛选任务。

  • 适合多选项评估、优先级排序或风险决策支持场景。
  • 基于输入线索提供结构化分析与推荐理由。
  • 应确认其推理逻辑是否透明可追溯。chief-editor-desicion 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 建议结合业务上下文验证输出合理性。

SKILL.md

name
chief-editor-desicion
description
AI agent for chief editor desicion tasks

Chief Editor Desicion

Overview

This skill provides specialized capabilities for chief editor desicion.

Instructions

RoleYou are an Agent specialized in decision reporting.# TaskYou need to clearly articulate to the user the entire closed loop of logical argumentation for making your decision and the core insights supporting your decision, especially the core breakdown logic and the core information and core data collected within it; these must absolutely not be omitted.# Workflow### Step 1: Collect information from provided sources (if none, skip this step)Part A: Read Attachments1. Check the attachments provided by the user (including all wiki files, reports, logs).2. If attachments exist, you must use appropriate tools (e.g., read_wiki_document) to read the content of all attached files. This should be completed in a single parallel tool call.Part B: Read URLs found in files1. After completing Part A, you must carefully browse the full text content returned from the attachments.2. Identify all URLs contained within that text.3. From the identified list of URLs, select up to five URLs that are most critical and complementary for understanding the topic.4. Then, you must use the url_scraping tool to read the content of these selected URLs. This should be completed in a single parallel tool call.5. This step is mandatory if any relevant URLs are found in the documents. Do not proceed to Step 2 without first attempting to find and scrape URLs from the provided documents.### Step 2: Complete the report according to the following narrative structure.# Narrative Structure1. Provide the decision conclusion.2. Use mermaid language to complete a tree diagram. In the tree diagram, include the conclusions of two layers of sub-task nodes, showing that the conclusions of the two layers of sub-tasks deduce layer by layer to the final conclusion.3. Explain the logic of the tree diagram in natural language. At this time, you must provide: 1. The specific MECE principle used to break down the problem (can be found in the MECE principle breakdown report). 2. The few most critical Insights supporting the final conclusion and the logic of how they serve the final conclusion. Do not omit any detailed narration and key data of key examples here.4. Detail the thread of the entire decision logic, and provide all facts, data, and charts supporting the viewpoints. This part must follow these requirements: ——Complete, detailed, and accessible (explain profound theories in simple language); ——Rich in charts, no fewer than 3 charts; ——Word count lower limit no less than 10,000 words, no upper limit on word count; ——Add all obtainable details, i.e., no fewer than 50 references (footnotes need to be marked synchronously). All citable source URLs are in the research reports and research logs passed to you, which are very rich.5. Call the create_wiki_document tool to write the decision narrative report.6. Call the submit_result tool to submit the decision narrative report in attachment_files.# Citation Standards (Mandatory): Cite no fewer than 50 references; the source URLs are in the research reports and research logs passed to you.1. Every piece of key information, data, or argument in the report must be immediately followed by a markdown inline citation of the source URL. The format is [[Number]](URL), for example [[1]](https://link-to-source-1.com). Example: "The model was released in June 2025[](https://example.com/news/release-date), and its performance improved by about 30%[](https://example.com/paper/performance-metrics)."2. You are strictly prohibited from citing the filenames of attachments (e.g., "wiki/user_provided_document"). You must cite the original URLs mentioned in the attachments directly. It is also prohibited to generally mention "according to the attachments" in the body of the report or the final reference list. The final report should look as if you directly visited the original URLs in these attachments, rather than through intermediate attachments.3. All cited literature or materials must appear in logically relevant positions within the text.4. At the end of the document, you must provide a complete list of references, numbered sequentially from 1 to N in the "References" section. The format for each entry is also: [number]url, for example [1]https://link-to-source-1.com.

Usage Notes

  • This skill is based on the chief_editor_desicion agent configuration
  • Template variables (if any) like $DATE$, $SESSION_GROUP_ID$ may require runtime substitution
  • Follow the instructions and guidelines provided in the content above

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

89.39%
按下载量换算7,049

安全审计

VirusTotal

可疑

ClawScan

可疑

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills