Guizang Social Cards
op7418/guizang-social-card-skill
Produces social card sets for Xiaohongshu and WeChat: carousels, Live Photo motion cards and puzzle layouts, and WeChat cover pairs, rendered from single-file HTML.
Write or revise a NodeTool skill: a user skill row through createskill, or a shipped system skill under packages/system-skills.
Install Nodetool Skill Author
$ npx skills add nodetool-ai/nodetool --skill nodetool-skill-author -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nodetool-ai/nodetool nodetool-skill-author --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/system-skills/nodetool-skill-author .claude/skills/nodetool-skill-author && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nodetool-skill-author" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-skill-author into .claude/skills/nodetool-skill-author/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-skill-author", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-skill-authorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nodetool-ai/nodetool --skill nodetool-skill-author -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nodetool-ai/nodetool nodetool-skill-author --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/system-skills/nodetool-skill-author .agents/skills/nodetool-skill-author && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nodetool-skill-author" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-skill-author into .agents/skills/nodetool-skill-author/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-skill-author", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nodetool-ai/nodetool --skill nodetool-skill-author -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nodetool-ai/nodetool nodetool-skill-author --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/system-skills/nodetool-skill-author .cursor/skills/nodetool-skill-author && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nodetool-skill-author" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-skill-author into .cursor/skills/nodetool-skill-author/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-skill-author", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nodetool-ai/nodetool.git --path packages/system-skills/nodetool-skill-author--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nodetool-ai/nodetool --skill nodetool-skill-author -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nodetool-ai/nodetool nodetool-skill-author --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/system-skills/nodetool-skill-author .gemini/skills/nodetool-skill-author && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nodetool-skill-author" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-skill-author into .gemini/skills/nodetool-skill-author/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-skill-author", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nodetool-ai/nodetool nodetool-skill-authorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nodetool-ai/nodetool --skill nodetool-skill-author -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/system-skills/nodetool-skill-author .github/skills/nodetool-skill-author && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nodetool-skill-author" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-skill-author into .github/skills/nodetool-skill-author/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-skill-author", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nodetool-ai/nodetool --skill nodetool-skill-author -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nodetool-ai/nodetool nodetool-skill-author --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/system-skills/nodetool-skill-author .opencode/skills/nodetool-skill-author && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nodetool-skill-author" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-skill-author into .opencode/skills/nodetool-skill-author/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-skill-author", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
nodetool-skill-author- GitHub stars
- 560
- Token cost
- ~1.4k tokens
- SKILL.md length
- 797 words
- Files
- 1
- Skills in repo
- 127
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Write or revise a NodeTool skill: a user skill row through createskill, or a shipped system skill under packages/system-skills.
- Instructions should persist across sessions
- SKILL.md covers Which kind, The contract, Write it so it fires and so it… and Shipping a system skill, plus 1 more section
- Calls npm
What it does
Nodetool Skill Author is an agent skill from nodetool-ai/nodetool. Write or revise a NodeTool skill: a user skill row through createskill, or a shipped system skill under packages/system-skills. Use when instructions should persist across sessions.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Media & Creative. The repository describes itself as: Agent-first Creative Workspace. The licence is AGPL-3.0.
When your agent uses it
- Instructions should persist across sessions
Example prompts
- “/nodetool-skill-author”
What it can do on your machine
Read from SKILL.md and the folder at commit 339f069. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Nodetool Skill Author loads about 1.4k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 797 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nodetool-ai/nodetool at commit 339f069, republished under its AGPL-3.0 licence (© nodetool-ai). 797 words, ~1,416 tokens.
Download SKILL.mdSave it as
.claude/skills/nodetool-skill-author/SKILL.md (or your agent's skills folder).- name
- nodetool-skill-author
- 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.
- featured
- true
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 the names are reserved so a user row cannot shadow one |
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
Both kinds are the same document.
---
name: my-skill
description: When to use this
---
The instructions.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 split the body into sections a loader can fetch one at a time. Use them for material an agent needs only at one step.
Confirm the parse by listing it back: list_skills shows name and description,
load_skill {name} returns the full instructions.
Show full SKILL.md (379 more words)Show less
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 order is _skills/ beside the bundle, else packages/system-skills
on the way up, else NODETOOL_SYSTEM_SKILLS_DIR. 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:
- Nothing, for the tool names:
packages/agents/tests/shipped-skill-names.test.tsreads every snake_case call out of every shipped skill and checks it against the registry, so a new directory is covered as soon as it exists. 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.
© nodetool-ai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in packages/system-skills/nodetool-skill-author of nodetool-ai/nodetool.
Open the folder on GitHubat commit 339f069
Compare with similar skills
Nodetool Skill Author next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Nodetool Skill Author this skillnodetool-ai/nodetool | 560 | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 | |
| Guizang Social Cardsop7418/guizang-social-card-skill | 7.4k | 1 repos | ~7.8k | Automated safety check: Pass | AGPL-3.0 | |
| Weekly Changelog Videoheygen-com/hyperframes | 60k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Anthropic Brand Stylinganthropics/skills | 180k | 30 repos | ~559 | Automated safety check: Pass | Apache-2.0 | |
| MoneyPrinterTurbo Video Generatorharry0703/MoneyPrinterTurbo | 129k | — | ~2.1k | Automated safety check: Warn | MIT | |
| HyperFrames Media Useheygen-com/hyperframes | 60k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Weekly Changelog Video
heygen-com/hyperframes
Turns a weekly changelog markdown file into a branded HyperFrames video with voiceover, animated mock-UI scenes and captions, using fonts, background and scripts bundled in the skill.
- Official
Anthropic Brand Styling
anthropics/skills
Applies Anthropic's brand colors and fonts to artifacts such as PowerPoint slides, using fixed hex values for text and accents, Poppins headings and Lora body text.
MoneyPrinterTurbo Video Generator
harry0703/MoneyPrinterTurbo
Installs and runs MoneyPrinterTurbo to turn a topic or script into a finished short video with voice-over, subtitles, stock footage and music.
HyperFrames Media Use
heygen-com/hyperframes
Finds, generates and edits media for HyperFrames video projects: music, sound effects, images, icons, logos, voiceovers, captions and color grades.
Holo Card Studio
EverettFish/holo-card-studio
Create collectible holographic foil cards and two-image lenticular flip cards with AI-generated full-color ukiyo-e and colored sumi-e anime artwork, layered Blender scenes, renders, GLB export, and…
More from nodetool-ai/nodetool
All 127 skills in this repoBeat Sync Editing
nodetool-ai/nodetool
Cut a NodeTool timeline to music and shape its pacing — detect the beat grid, place cuts on phrases, pick a cut type, build speed ramps with time remap, and give the piece an arc.
Caption Titles
nodetool-ai/nodetool
Add and animate a consistent text layer on an existing NodeTool timeline.
Color Motion
nodetool-ai/nodetool
Choose and animate colour on a NodeTool timeline, including shape and text gradients, colour grades, 3D LUTs, and dither.
Commercial Beat Sheet
nodetool-ai/nodetool
Write a shootable, precisely timed commercial beat sheet and store it as a NodeTool storyboard, with a consistent entity roster behind every shot.
Elevenlabs Audio Prompting
nodetool-ai/nodetool
Direct ElevenLabs speech, dialogue, sound effects and music — the bracketed audio tags v3 acts on and why the voice decides whether a tag lands, stability as the delivery dial, punctuation instead…
Frame Composition
nodetool-ai/nodetool
Stage the frame on a NodeTool timeline — grids, focal placement, safe areas per aspect ratio, depth layers and parallax, camera moves, and where elements enter and leave.
Related
Categories
Questions about Nodetool Skill Author
What does Nodetool Skill Author do?
Write or revise a NodeTool skill: a user skill row through createskill, or a shipped system skill under packages/system-skills. Nodetool Skill Author is an agent skill from nodetool-ai/nodetool. Write or revise a NodeTool skill: a user skill row through createskill, or a shipped system skill under packages/system-skills.
When should I use Nodetool Skill Author?
Nodetool Skill Author fits situations like: instructions should persist across sessions.
How do I install Nodetool Skill Author in Claude Code?
Run `npx skills add nodetool-ai/nodetool --skill nodetool-skill-author -a claude-code`. Or copy the skill folder (packages/system-skills/nodetool-skill-author in nodetool-ai/nodetool) into .claude/skills/nodetool-skill-author in your project. Claude Code loads it when a task matches its description.
How do I install Nodetool Skill Author in Codex?
Run `npx skills add nodetool-ai/nodetool --skill nodetool-skill-author -a codex`. Or copy the skill folder (packages/system-skills/nodetool-skill-author in nodetool-ai/nodetool) into .agents/skills/nodetool-skill-author in your project. Codex loads it when a task matches its description.
Can I use Nodetool Skill Author in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nodetool-ai/nodetool --skill nodetool-skill-author -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nodetool-skill-author, .gemini/skills/nodetool-skill-author, .github/skills/nodetool-skill-author and .opencode/skills/nodetool-skill-author in your project.
What does Nodetool Skill Author need to run?
Going by SKILL.md and its folder, Nodetool Skill Author needs the command-line tools its instructions call (npm).
Does Nodetool Skill Author access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Nodetool Skill Author safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Nodetool Skill Author use?
Nodetool Skill Author is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nodetool Skill Author use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Nodetool Skill Author?
Skills that share tags, products or a category with Nodetool Skill Author: Guizang Social Cards (op7418/guizang-social-card-skill, 7.4k stars), Weekly Changelog Video (heygen-com/hyperframes, 60k stars), Anthropic Brand Styling (anthropics/skills, 180k stars) and MoneyPrinterTurbo Video Generator (harry0703/MoneyPrinterTurbo, 129k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nodetool Skill Author?
nodetool-ai (a GitHub organization) maintains it in nodetool-ai/nodetool, which has 560 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on October 10, 2026.
Source: nodetool-ai/nodetool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.