nodetool-skill-author
Write or revise a NodeTool skill: a user skill row through create_skill, or a shipped system skill under packages/system-skills. Use when instructions should persist across sessions.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-15
- Stars
- ★ 635
- Forks
- 91
01 前言 Front Matter
- name
- nodetool-skill-author
- featured
- true
- description
- Write or revise a NodeTool skill: a user skill row through create_skill, or a shipped system skill under packages/system-skills. Use when instructions should persist across sessions.
03 SKILL.md 正文
Author a NodeTool skill
A skill is a named set of instructions an agent loads when its description matches the task. Write one when the same direction would otherwise be repeated every session. Do not write one for a single job: do the job.
Which kind
| User skill | System skill | |
|---|---|---|
| Lives in | A row in the user's account | packages/system-skills/<name>/SKILL.md in the build |
| Written by | create_skill, update_skill, delete_skill |
A file in a pull request |
| Scope | That user | Every install, on day one, with no seeding migration |
| Editable at runtime | Yes | No. Immutable, and create_skill, update_skill and renames refuse a shipped name. A user row that already held the name before the skill shipped still shadows it |
A repository skill under .claude/skills/ is a third thing: it directs the
coding agent working on the NodeTool repository, not the agent inside the
product — the engineering loop, not a product surface. Its maintenance rules
are in a checkout's .claude/README.md, § Maintaining skills.
A skill that teaches a product surface is a system skill even when the coding
agent also wants it. packages/system-skills/<name> holds the one copy and
.claude/skills/<name> is a symlink to it, so the product and the repository
read the same document. Write a second copy under .claude/skills/ and the
two drift; npm run check:agents-docs fails on one.
The contract
A system skill is one Markdown document with frontmatter:
---
name: my-skill
description: When to use this
---
The instructions.
A user skill has the same three parts as separate create_skill fields:
{name, description, content}. content is the body only. Do not put
frontmatter in it.
nameis a lowercase slug,a-z0-9-only, at most 64 characters. It cannot containanthropicorclaude. A user's names must be unique per user.descriptionis one bounded line, at most 1024 characters, with no markup. It is the only part always in context, so write it as when to use this, not as what the skill contains. A description that does not name the trigger means the skill never loads.featured: trueis for a shipped skill only. It puts the skill in the catalog that every turn carries. Every other shipped skill is found withlist_skills({query}), so feature a skill only when a turn needs it before its first call: the entry point of a product surface, or a craft skill that work on that surface always reads.- The body must be non-empty. Frontmatter is parsed as scalar
key: valuepairs, not full YAML, and the fence is the first---line after the opening one, so a---rule inside the body survives. ##headings organize the body for the reader.load_skillreturns the whole document in one piece, so a section does not save context.
Confirm the parse by listing it back: list_skills shows name and description,
load_skill {name} returns the full instructions.
Write it so it fires and so it holds
- Lead with the result, then the loop. The reader is mid-task and will act on the first thing that looks like an instruction.
- Name tools exactly. A renamed tool in a skill is a failure a model cannot recover from. Check each call against the live schema or the capability registry before writing it.
- State what a tool refuses, not only what it accepts. Most skill failures are a call made with a field the tool drops.
- Point at the neighbour rather than restating it. A craft skill quotes a call, the contract skill owns it.
- Do not add checkpoints or deliverables the user did not ask for. An example in a skill is an illustration, not a requirement on the next request.
Shipping a system skill
One directory holding a SKILL.md whose frontmatter name matches the
directory. Nothing imports these files, so packages/system-skills is not a
workspace: stageSystemSkills in scripts/bundle-backend.mjs copies every
directory into _skills/ beside the bundled server.mjs, and
scripts/verify-backend-bundle.mjs fails a build that misses one. A new
directory ships with no other change.
Discovery checks NODETOOL_SYSTEM_SKILLS_DIR first, and when it is set nothing
else is searched. Otherwise it uses _skills/ beside the bundle, else
packages/system-skills on the way up. Only SKILL.md is read: a
skill ships as one document, so material that would have been a references/
file belongs in a ## section of the body.
Symlink the new directory into .claude/skills/<name> when the repository's
coding agent should reach it too.
Two follow-ups a new system skill usually needs:
- Check the tool names yourself.
packages/agents/tests/shipped-skill-names.test.tsreads snake_case calls out of every shipped skill and checks them against the registry, but only names with a known verb prefix (add_,create_,get_,list_and so on). Names such asweb_search,request_secretorfind_modelpass unchecked, and so do node types. A skill whose body names timeline calls can also go in that test'sSKILL_NAMES, which matches them exactly against the capability specs andedit_timeline's op list. - A skill that guides one model line goes in
MODEL_PROMPTING_SKILLS(packages/agents/src/model-prompting-skills.ts) sofind_modelattaches it to a matching route.packages/agents/tests/model-prompting-skills.test.tschecks that table against the skills on disk, the model ids the shipped provider manifests name, and the capability registry.
Reference
In a NodeTool checkout, these repository sources go further:
packages/system-skills/README.md— the shipped set, and how one job routes across it.packages/agents/src/system-skills.ts— loader and discovery rules.packages/protocol/src/skill-document.ts— the parser and the validators.
04 同仓库更多 Skills
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language, stock AI words, bold labels, or filler.
nodetool
Use the NodeTool MCP server to build, validate, run, and debug visual AI workflows, and to work with assets, collections, and jobs. Use when the user mentions NodeTool or asks for a workflow graph, a node, or a media generation run on their NodeTool server.
wan-2-6-prompting
Prompt Alibaba's Wan 2.6 video — text-to-video with a global style line plus timing-bracketed shots, and image-to-video that describes only what changes over time. Covers the shot-mode switch per provider, the prompt budget, negative prompts, motion intensity wording, audio input and prompt expansion. Use whenever the model id names a Wan 2.6 video route (alibaba/wan-2.6/text-to-video, alibaba/wan-2.6/image-to-video, wan-video/wan-2.6-t2v, wan-video/wan-2.6-i2v, wan-video/wan2.6-i2v-flash) on generate_video, animate_image or a TextToVideo node. Not for Wan 2.5 or 2.7, or the Wan 2.6 image routes.
video-workflow
Build a reusable NodeTool video workflow for batches or repeated inputs. For a single finished piece, use a storyboard skill.
video-clone
Analyze a reference video and recreate its shot structure with a new product or cast in NodeTool.
video-audio-continuity
Keep sound continuous across a multi-scene piece cut from generated video — why one clip per scene hard-cuts the audio at every boundary, when to write all the scenes into a single generation instead, the sound-design vocabulary that survives a provider's copyright filter, and how to check the length, the aspect ratio and the mix of what came back. Use when a piece has more than one scene and the video model writes its own audio (Seedance 2, Veo 3, MiniMax H3, Kling 2.6 and later), or when a cut's sound drops out at the shot changes.