跳到主内容
智客 ZICQ

技能库 智客分类:文档办公 fusion-skill-authoring

Fusion Skill Authoring

创建或现代化存储器技能,具有明确的激活提示,有目的的支持文件,以及实用的审查循环. 使用for:创造出新的技能,收紧现有的技能,改进发现措辞,在真正增加价值时安排参考/资产/可选帮助代理。 不使用: 产品代码更改, 常规复制在技能之外编辑/ , 或不应成为可安装技能的文档 .

1922 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

创建或现代化存储器技能,具有明确的激活提示,有目的的支持文件,以及实用的审查循环. 使用for:创造出新的技能,收紧现有的技能,改进发现措辞,在真正增加价值时安排参考/资产/可选帮助代理。 不使用: 产品代码更改, 常规复制在技能之外编辑/ , 或不应成为可安装技能的文档 .

何时用

在 " 技能/ " 下创造出新技能时或当现有技能需要新材料时激活

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Create or Modernize Skills、When to use、When not to use、Required inputs、Mandatory、Conditional。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/assets/helper、assets/follow-up-questions.md、references/assets、references/skill-template-baseline.md、references/validation-signals.md、assets/skill-readiness-checklist.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Creates or modernizes repository skills with clear activation cues, purposeful support files, and practical review loops. USE FOR: creating a new skill, tightening an existing skill, improving discovery wording, and structuring references/assets/optional helper agents when they genuinely add value. DO NOT USE FOR: product-code changes, routine copy edits outside skills/, or documentation that should not become an installable skill.

Create or Modernize SkillsWhen to useWhen not to useRequired inputsMandatoryConditionalOptionalMetadata and structure constraintsInstructionsStep 1 — Check for installed-copy provenance before editingStep 2 — Decide whether this should be a skill at allStep 3 — Define representative requests before drafting

兼容:Works best in repositories that can inspect their local skill catalog and run catalog-specific validation commands. Optional helper agents are most useful in Anthropic-compatible runtimes or other clients that support skill-local agents/subagents. · 许可:MIT

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
fusion-skill-authoring
description
Creates or modernizes repository skills with clear activation cues, purposeful support files, and practical review loops. USE FOR: creating a new skill, tightening an existing skill, improving discovery wording, and structuring references/assets/optional helper agents when they genuinely add value. DO NOT USE FOR: product-code changes, routine copy edits outside skills/, or documentation that should not become an installable skill.
compatibility
Works best in repositories that can inspect their local skill catalog and run catalog-specific validation commands. Optional helper agents are most useful in Anthropic-compatible runtimes or other clients that support skill-local agents/subagents.
许可
MIT
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 6
  • references/assets/helper
  • assets/follow-up-questions.md
  • references/assets
  • references/skill-template-baseline.md
  • references/validation-signals.md
  • assets/skill-readiness-checklist.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「fusion-skill-authoring」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-6cbdf4d5b7d916cc-Fusion-%E6%8A%80%E8%83%BD%E5%86%99%E4%BD%9C.html
请存为 .cursor/skills/fusion-skill-authoring/SKILL.md 或 .claude/skills/fusion-skill-authoring/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/equinor/fusion-skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/equinor/fusion-skills' --list

npx skills add 'https://github.com/equinor/fusion-skills' --skill 'fusion-skill-authoring'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: fusion-skill-authoring description: 'Creates or modernizes repository skills with clear activation cues, purposeful support files, and practical review loops. USE FOR: creating a new skill, tightening an existing skill, improving discovery wording, and structuring references/assets/optional helper agents when they genuinely add value. DO NOT USE FOR: product-code changes, routine copy edits outside skills/, or documentation that should not become an installable skill.' license: MIT compatibility: Works best in repositories that can inspect their local skill catalog and run catalog-specific validation commands. Optional helper agents are most useful in Anthropic-compatible runtimes or other clients that support skill-local agents/subagents. metadata: version: "0.3.6" status: active owner: "@equinor/fusion-core" tags: - skill-authoring - scaffolding - greenkeeping mcp: suggested: - github --- # Create or Modernize Skills ## When to use Activate when creating a new skill under `skills/`, or when an existing skill needs a material authoring refresh. Typical triggers: - "Create a skill for ..." - "Scaffold `skills//SKILL.md`" - "Turn this workflow into a reusable skill" - "Improve this skill's metadata and activation cues" - "Make this skill easier to discover" - "Set up references/assets/helper agents for a skill" Implicit triggers: - Recurring task keeps requiring the same instructions or safety boundaries - Existing skill is too vague, too long, poorly routed, or missing structure - User wants a reusable workflow package, not a one-off prompt ## When not to use - Editing product or application code outside `skills/` - Tiny typo-only edits that don't need authoring workflow help - Requests better solved as docs, templates, or scripts without an installable skill - Large unrelated repo refactors - Destructive commands or hidden network automation ## Required inputs If required inputs are missing, ask concise targeted questions first. Use `assets/follow-up-questions.md` as the default question bank. ### Mandatory Collect before drafting: - Whether this is a new skill, update, or not a skill at all - Target repo path and intended skill directory - Base skill name in kebab-case before any prefix/namespace - Final skill name in kebab-case; default to `custom-` unless repo has different convention - One-sentence purpose and user outcome - Concrete activation cues: trigger phrases, domain keywords, anti-triggers - Expected output: files, commands, or decisions the skill produces - Safety boundaries and approval requirements ### Conditional Collect when relevant: - Naming prefix, namespace, or catalog convention - Skill category: capability uplift or workflow/encoded preference - Composition: standalone, orchestrator, or subordinate - Repository-specific ownership, lifecycle, or release policy - Orchestrator relationship: `metadata.orchestrator` for subordinates, `metadata.skills` for orchestrators - Target status (`active`, `experimental`, `deprecated`, `archived`) - `compatibility` text when skill has real environment constraints - MCP requirements (`metadata.mcp.required` / `metadata.mcp.suggested`) - Whether helper agents in `agents/` would sharpen scoping, review, or trigger tuning - Whether deterministic automation justifies a `scripts/` directory ### Optional Capture if useful: - `metadata.sponsor` as backup accountability if catalog uses it - Starter assets, checklists, examples, or templates - Related issue follow-up if an almost-match exists and should be improved instead of duplicated ### Metadata and structure constraints Validate before writing files: - `name`: 1-64 characters, lowercase letters/numbers/hyphens only, must match the folder name, no leading/trailing hyphen, no consecutive hyphens, no XML tags, and no reserved words - If the target repository has no prefix or namespace convention, default new skills to `custom-` - `description`: non-empty, <= 1024 chars, third-person, no XML tags, states both what the skill does and when to use it - Prefer a single-quoted YAML string with inline `USE FOR:` and `DO NOT USE FOR:` cues - Example: `description: 'Drafts release notes from validated repository context. USE FOR: release summaries, changelog preparation. DO NOT USE FOR: publishing releases or editing product code.'` - `metadata.version`: follow the target catalog's starting-version rule; if no local rule exists, `"0.0.0"` is a safe default for a new skill - `metadata.owner`: include only when the target catalog requires explicit ownership; use a stable GitHub identity or equivalent team handle - `metadata.status`: include only when the target catalog tracks lifecycle state; if used, keep it to `active`, `experimental`, `deprecated`, or `archived` - `metadata.tags`: keep tags relevant, lowercase, and kebab-case - `metadata`: use simple key/value metadata unless a relationship field explicitly needs a list or map - `license`: optional top-level field - `compatibility`: optional top-level field; only include it when the skill has real runtime, network, tool, or product constraints Repository-specific prefix rules, ownership/lifecycle requirements, release policy, and validation commands belong in repo-local instructions or catalog docs, not in the portable skill package. ## Instructions ### Step 1 — Check for installed-copy provenance before editing Before editing an existing `SKILL.md` (or its `references/`, `assets/`, `agents/`), inspect the repository's `apm.yml` and `apm.lock.yaml`. Use the lockfile's dependency provenance and deployed-file ownership to determine whether the target came from an external APM dependency. If it did, the target is an **installed copy**, not the canonical source. **If it is an installed copy:** - Do not edit in place — local edits may be overwritten by the next `apm install` or `apm update` and never reach other consumers. - Tell the user the file is installed from ``; changes belong there. - Offer to switch to `` and make the change there, or draft a bug/improvement issue against it instead. - Only edit locally if the user explicitly confirms a one-off override and accepts it won't persist. If neither APM file exists, the target has no matching deployed-file ownership, or the source matches the current repository, proceed normally. ### Step 2 — Decide whether this should be a skill at all 1. Check existing catalog first: - If an existing skill covers the request, recommend reuse or update instead of a duplicate - If a skill almost matches, recommend improving it or opening an issue 2. Don't scaffold if the request is better handled as: - plain repository documentation, - a template/checklist with no reusable agent behavior, - a standalone script with no skill-routing value, or - a tiny copy edit to an existing skill ### Step 3 — Define representative requests before drafting Capture at least three representative requests before writing long instructions: - the user request or trigger phrase, - the behavior the skill should produce, - the mistake or gap the skill must prevent. Use these as acceptance criteria. If you can't define realistic requests, the scope is underspecified or not reusable enough to become a skill. ### Step 4 — Classify the skill and choose the smallest valid structure Decide skill type: - `capability uplift`: packages domain knowledge, tools, or reference material - `workflow / encoded preference`: packages sequencing, review gates, style rules, or mutation order Decide composition: - `standalone`: no coordinating skill required - `orchestrator`: routes to companion skills, owns shared gates - `subordinate`: runs only under its orchestrator — document that dependency Choose minimum folder structure: - `SKILL.md` always - `references/` for long guidance, examples, tables, or platform-specific details - `assets/` for templates, checklists, sample outputs, and static files - `agents/` for specialized helper roles when runtime supports skill-local agents - `scripts/` only when deterministic automation materially improves safety or reliability Keep references one level deep. Don't create nested chains that force partial reads. ### Step 5 — Draft the minimum viable `SKILL.md` Write the smallest useful main document first: - concise frontmatter with strong discovery cues - `When to use` and `When not to use` - `Required inputs` - `Instructions` - `Expected output` - `Safety & constraints` Keep under 300 lines. Different runtimes have different context limits — files over 300 lines risk degradation on smaller runtimes and trigger CI warnings. Files over 500 lines fail CI. Move overflow to `references/` early. Prefer concise, specific instructions over background explanation. Assume the agent is capable; only add context it won't reliably infer. Set degree of freedom intentionally: - high freedom for context-dependent analysis or review - medium freedom when a preferred pattern exists but adaptation is expected - low freedom when workflow is fragile, safety-critical, or sequence-sensitive Include at least one concrete example in `SKILL.md` or link to one in `references/`. ### Step 6 — Add supporting files only when they reduce ambiguity Move long or specialized content out of `SKILL.md`: - `references/` for deep guidance, large examples, API/platform notes, or long checklists - `assets/` for templates and reusable artifacts - `agents/` for helper set when runtime supports skill-local agents and workflow benefits from scoped second opinion - `scripts/` for deterministic operations that should be executed instead of regenerated If you add scripts: - document dependencies and side effects, - validate inputs and fail with actionable errors, - keep network access explicit and justified, - never use remote-code execution patterns. If runtime ignores bundled helper agents, follow the same roles inline. If skill depends on MCP, declare in `metadata.mcp` and document client-specific tool naming in skill content. ### Step 7 — Validate discovery, structure, and local policy Run validation supported by the target environment after authoring changes: - inventory or schema validation for the skill catalog, if available - repo or catalog policy checks for naming, ownership, lifecycle, or composition metadata - script, GraphQL, lint, or test validation when skill touches those surfaces If no dedicated skill tooling: - read `SKILL.md` and every directly referenced file end-to-end - verify each representative request would trigger the skill correctly - verify every referenced file path and workflow assumption is valid Use representative requests from Step 3 to review: - Does the description trigger on the right requests and avoid false positives? - Can the agent locate all directly referenced files without chasing nested links? - Are outputs, approval gates, and safety constraints explicit? If subagents are available: - `agents/scoper.md` before drafting to decide create vs update vs not-a-skill - `agents/devils-advocate.md` during scoping and drafting to surface key concerns, or full structured interview when user asks to be grilled or significant ambiguity detected - `agents/reviewer.md` after drafting to review discovery, structure, safety, and validation evidence - `agents/trigger-tuner.md` when the main risk is weak activation cues After portable package is correct, apply any repository-specific release or versioning rules. ### Step 8 — Report what changed and what still needs input Return authoring result as explicit contract: - what was created or updated, - how the skill was classified, - which representative requests were used as acceptance criteria, - which helper agents were used, if any, - which validation commands ran and what they proved, - any unresolved questions or recommended follow-up issues. ## Core behavior to preserve - Installed-copy provenance check before editing an existing skill - Reuse before creation - Portable first, repository overlays second - Representative requests before long-form wordsmithing - Progressive disclosure instead of overloading `SKILL.md` - Explicit safety and approval gates for risky actions - Real validation evidence instead of assumed correctness ## Optional helper agents Borrowed from Anthropic `skill-creator` pattern but narrowed to Fusion-specific scoping, review, and trigger tuning. - `agents/scoper.md` — decide new skill vs update vs not a skill; choose smallest folder structure - `agents/reviewer.md` — review drafted skill against discovery, structure, safety, and validation - `agents/trigger-tuner.md` — sharpen description wording; compare activation-cue variants - `agents/devils-advocate.md` — always-on quality collaborator; moderate mode during authoring, interrogator mode when asked or significant ambiguity detected If runtime offers no subagents, keep the same review loop inline. ## Examples - User: "Create a skill for drafting incident retrospectives." - Result: create a new workflow-oriented skill in the target catalog, define at least three retrospective authoring scenarios, scaffold `SKILL.md`, and add `assets/` only if templates are needed. - User: "Improve the activation cues and structure of `fusion-skill-authoring`." - Result: update the existing skill, refresh supporting references/assets, and run the target repository's validation flow. - User: "Add a new CLI flag to the application." - Result: do not use this skill because the request is product-code work, not skill authoring. ## Expected output Return: - Created or updated file paths - Skill classification: new/update/not-a-skill, capability vs workflow, standalone/orchestrator/subordinate - Final activation cues and anti-triggers used - Chosen folder structure and rationale - At least three representative requests used as acceptance criteria - Which helper agents were used, if any - Validation commands run, pass/fail status, and interpretation - Repository-specific overlays applied after portable draft - Follow-up actions, unresolved questions, or recommended issue links See `references/skill-template-baseline.md` for default folder structure and baseline template. ## Validation See `references/validation-signals.md` for success signals, failure signals, and recovery steps. ## Skill Readiness Checklist Use `assets/skill-readiness-checklist.md` as final-quality checklist. Repository-specific PR requirements belong in repository instructions, not in the installable skill asset. ## Safety & constraints Never: - Request or expose secrets or credentials - Run destructive commands without explicit user confirmation - Invent validation results or evaluation evidence - Modify unrelated files outside the requested scope - Add hidden network access, remote-code execution, or unsafe script guidance - Edit an APM-installed copy in place without first surfacing its source repo and getting explicit confirmation Always: - Keep `SKILL.md` concise; move overflow to direct references - Make the discovery contract explicit in the description - Prefer deterministic validation loops over hand-wavy advice - Keep helper agents tightly scoped; core workflow still works when runtime doesn't invoke them - Respect target catalog's naming, ownership, lifecycle, and release policy

相关技能

文档办公

Ontology

为结构化的代理内存和可堆肥技能所打入的知识图. 在创建/征服实体(Person, project, Task, Evention, Document)时使用,链接相关对象,强制约束,规划多步动作作为图变,或技能需要共享状态时使用. 触发到"记住","我知道什么","链接X到Y",…

文档办公

Nano Pdf

使用纳米-pdf CLI编辑带有自然语言指令的PDF.

文档办公

Word / DOCX

创建,检查,并编辑有可靠样式的Microsoft Word文档和DOCX文件,编号,跟踪更改,表格,章节,并进行相容性检查. 当 (1) 任务涉及 Word 或 ".docx " 时使用; (2) 文件包括跟踪的更改,评论,字段,表格,模板,或页面布局限制; (3) 文档必须在不…

文档办公

Api Gateway

通过 Maton 网关调用第三方 API, 它为用户已经连接的应用程序注入证书 。 当用户命名一个连接的应用程序和其中的具体行动时使用此技能——读取一个邮箱,查询一个CMM,归档一个问题,更新一个电子表格,通过一个连接的搜索或刮取提供者运行一个查询. 每一次通话都到用户连接的应用…