菜单
Create or improve agent skills from concrete behavior and evidence. Use when building or revising SKILL.md, or testing whether a skill earns its context. Do not use for ordinary documentation or one-off prompts.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Astro-Han/skills --skill craft-skill命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Create simple, beautiful visual explainers for people new to a topic. Use for ELI5 and picture-first requests.
Review a pull request or queue from problem value through code correctness. Use for new review, rereview, batch review, or deciding findings and next steps. Do not use to implement feedback, report status, draft, merge, or monitor checks.
Use this skill whenever existing code-review feedback may lead to a code decision or edit, including PR comments and findings from external models, review tools, or delegated reviewers—even when the user simply says to fix, address, apply, or resolve them. Do not use to perform a new review, diagnose an unrelated bug, implement a new requirement, or merely summarize feedback without deciding what to do.
基于 SOC 职业分类
正在显示 SKILL.md
| name | craft-skill |
| description | Create or improve agent skills from concrete behavior and evidence. Use when building or revising SKILL.md, or testing whether a skill earns its context. Do not use for ordinary documentation or one-off prompts. |
A skill should be called for the right task, steer the agent to genuine completion, and make every token earn its place.
Read the request, conversation, existing skill, repository conventions, and target platform's authoritative skill specification.
Define the useful behavior with realistic examples: what should call the skill, what should not, what the agent should do differently, and what observable evidence means it finished. Ask only about user-owned choices that materially change those answers. When revising a skill, preserve its name and inspect observed failures before editing.
SKILL.md. Put branch-specific knowledge behind a direct pointer that states when to load it.Call is complete when every intended branch and close non-trigger has one clear owner, and the metadata passes the platform's validator when one exists.
Use the lightest reliable medium:
Match freedom to fragility. Use principles where several approaches work; tighten procedure or code only where variance causes failure.
Define completion from the requested outcome, not the procedure. Exhaustive means every decision-relevant item is accounted for, not every discoverable source or intermediate step is performed. End each step with a completion criterion the agent can check, with honest terminal states for missing evidence, unavailable input, and blocked actions. End with an overall postcondition that inspects the resulting artifact or state; completed steps are not final evidence.
When evidence could change the decision, read references/evaluation.md before evaluating. When an existing skill misbehaves and the cause is unclear, read references/diagnosis.md.
Run the platform validator and relevant script tests. Confirm every resource has a condition-bearing pointer. Report the evidence and what remains unverified.
Stop when the concrete examples work and another deletion would damage Call, Steer, or the evidence needed to judge them.