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.
Produce a NodeTool campaign with shared product and cast entities, stills, and multiple video cuts.
$ npx skills add nodetool-ai/nodetool --skill launch-kit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nodetool-ai/nodetool launch-kit --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/launch-kit .claude/skills/launch-kit && 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 "launch-kit" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/launch-kit into .claude/skills/launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-kit", 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/launch-kitType 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 launch-kit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nodetool-ai/nodetool launch-kit --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/launch-kit .agents/skills/launch-kit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "launch-kit" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/launch-kit into .agents/skills/launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-kit", 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 launch-kit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nodetool-ai/nodetool launch-kit --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/launch-kit .cursor/skills/launch-kit && 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 "launch-kit" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/launch-kit into .cursor/skills/launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-kit", 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/launch-kit--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 launch-kit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nodetool-ai/nodetool launch-kit --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/launch-kit .gemini/skills/launch-kit && 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 "launch-kit" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/launch-kit into .gemini/skills/launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-kit", 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 launch-kitInstalls 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 launch-kit -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/launch-kit .github/skills/launch-kit && 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 "launch-kit" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/launch-kit into .github/skills/launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-kit", 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 launch-kit -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 launch-kit --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/launch-kit .opencode/skills/launch-kit && 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 "launch-kit" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/launch-kit into .opencode/skills/launch-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-kit", 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.
launch-kitProduce a NodeTool campaign with shared product and cast entities, stills, and multiple video cuts.
Launch Kit is an agent skill from nodetool-ai/nodetool. Produce a NodeTool campaign with shared product and cast entities, stills, and multiple video cuts. Use for a coordinated asset set.
Its SKILL.md is about 1.3k 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.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 515bd28. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Launch Kit loads about 1.3k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 640 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.
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.
The full file from nodetool-ai/nodetool at commit 515bd28, republished under its AGPL-3.0 licence (© nodetool-ai). 640 words, ~1,332 tokens.
.claude/skills/launch-kit/SKILL.md (or your agent's skills folder).Load /storyboard-core first. It carries the loop, the tool contract and
the gating this skill assumes. Everything below is what changes when the deliverable is
a set rather than a cut.
Keep the grade and cast consistent across the requested campaign deliverables. Use the passes below as an organizing pattern, scaled to the brief.
So: one entity set, one board style string, one image model, one video model, fixed
at phase A and reused verbatim through phase D. Changing the image model mid-kit is how
a kit ends up looking like two kits.
Use phases as progress checkpoints. Continue within the authorized deliverables and budget. Pause for a user-requested review or a missing decision that changes the output or spending scope. Do not reconfirm authorization already given.
create_entity {kind: "prop"} with a
descriptor of geometry and finish. Keep the other angles (three-quarter, back, top,
on-figure) as plain assets — only the first reference image rides into a prompt.create_entity {kind: "style", palette}. A style entity
applies to every shot on every board, which is exactly what a kit wants.find_model once each for text_to_image and image_to_video. Write them and the
entities onto the board with set_board.memory_save the grade, the model ids, the board id and the entity ids, with the
ids in resources. This is what makes the kit resumable next week — share_result
would be discarded with the run.Report entity ids, the grade, and model ids. Continue with the requested assets.
Produce the requested number and mix of stills. Use take selection when the user reserved that choice. A stills-only request ends here. Otherwise continue to the authorized video deliverables with the selected frames.
Vary the crop in camera.framing and repeat it in action, since only framing reaches
the still prompt. Give product-only frames an explicit entity_ids naming the product
alone, so the model's descriptor does not season a frame she is not in.
Report the selected asset ids and continue within the requested scope.
Use the brief's clip count, durations, and ratios, animated from the selected phase-B stills. Honor any requested approval of those stills. Reuse them to keep the look consistent.
A separate board per aspect ratio — aspect_ratio is a board field, not a shot field,
so one board cannot serve 9:16 and 16:9. Same entities, same style, same models on each.
Report clip asset ids. Continue if the requested kit includes a longer film.
Build the longer piece at the requested duration and aspect ratio, with stable slugs and timing. Assemble it, then finish the sound:
edit_timeline → get_state, then set_clip_params {muted: true} on the "Shot Audio"
clips under any voiceover, and add music with generate_music + add_track +
add_media_clip at a low volumeDb.
validate_timeline before calling it done.
Report shot and frame counts per phase before each render — never a dollar figure, as
nothing prices a render. Afterwards, get_cost_summary gives what the kit actually
cost.
A twelve-frame still pass is cheap; three clip passes plus a 30-second film is not. If the user is deciding, that is the ratio to tell them.
list_storyboards shows shot counts and how many shots have a still and a clip.
memory_search finds the phase-A note with the grade and the entity ids. Together
those are enough to resume without re-deriving the look.
Adapt these examples to the user's brief. Example deliverables, style choices, and approval checkpoints apply only when the user adopts them.
Launch kit for [BRAND] [SKU] from the attached flat and on-body photos.
Stop after each phase and wait for me.
A. Cast and lock. Product entity from the flat (descriptor = geometry and
finish). Character entity from the on-body photo (descriptor = face, hair and
build, no wardrobe). Pick one image model and one video model with find_model
and write both onto the board. Grade: [cold film / warm daylight / black
studio]. memory_save the grade, both model ids and every entity id.
B. Twelve still campaign frames, mixed crops, on-figure and product-only. Stills
only — stop before clips. Product-only frames get entity_ids naming the
product alone.
C. Three 9:16 clips, 6-8s, animated from stills I approved in B. Do not
re-render those stills. A separate board for the vertical ratio.
D. One 30s 16:9 film, slugged and timed. Assemble, mute the Shot Audio clips
under the voiceover, add a music bed low, then validate_timeline.
Same grade and the same two models from A through D. Report counts before each
render, not dollars.© 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
Just SKILL.md in packages/system-skills/launch-kit of nodetool-ai/nodetool.
Open the folder on GitHubat commit 515bd28
Launch Kit 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 |
|---|---|---|---|---|---|---|
| Launch Kit this skillnodetool-ai/nodetool | 556 | — | ~1.3k | 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 | 59k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Anthropic Brand Stylinganthropics/skills | 180k | 30 repos | ~559 | Automated safety check: Pass | Apache-2.0 | |
| Native Subtitle Quote Imagechengyi-ai/native-subtitle-quote-image | 2.2k | 2 repos | ~1.8k | Automated safety check: Pass | MIT | |
| MoneyPrinterTurbo Video Generatorharry0703/MoneyPrinterTurbo | 129k | — | ~2.1k | Automated safety check: Warn | MIT |
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.
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.
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.
chengyi-ai/native-subtitle-quote-image
将本地视频或用户有权处理的在线视频,经过来源获取、文字稿定位、选题选句、精确取帧、紧凑裁切、拼图和逐张质检,制作成 3:4 或保留画面原比例的视频字幕长图。支持两种明确分开的输出:保留画面内已烧录字幕的原生字幕模式,以及把已审核的时间点与台词绘制到真实视频帧上的脚本字幕模式。用户要求原生字幕截图、字幕帧拼图、YouTube…
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.
latent-spaces/brag
Builds a short, shareable launch video with music and motion from a project directory or a website URL, using only tools already on the machine.
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.
nodetool-ai/nodetool
Add and animate a consistent text layer on an existing NodeTool timeline.
nodetool-ai/nodetool
Choose and animate colour on a NodeTool timeline, including shape and text gradients, colour grades, 3D LUTs, and dither.
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.
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…
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.
Categories
Produce a NodeTool campaign with shared product and cast entities, stills, and multiple video cuts. Launch Kit is an agent skill from nodetool-ai/nodetool. Produce a NodeTool campaign with shared product and cast entities, stills, and multiple video cuts.
Launch Kit fits situations like: A coordinated asset set.
Run `npx skills add nodetool-ai/nodetool --skill launch-kit -a claude-code`. Or copy the skill folder (packages/system-skills/launch-kit in nodetool-ai/nodetool) into .claude/skills/launch-kit in your project. Claude Code loads it when a task matches its description.
Run `npx skills add nodetool-ai/nodetool --skill launch-kit -a codex`. Or copy the skill folder (packages/system-skills/launch-kit in nodetool-ai/nodetool) into .agents/skills/launch-kit in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nodetool-ai/nodetool --skill launch-kit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/launch-kit, .gemini/skills/launch-kit, .github/skills/launch-kit and .opencode/skills/launch-kit in your project.
SKILL.md names no scripts, command-line tools or credentials: Launch Kit is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Launch Kit 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.
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Launch Kit: Guizang Social Cards (op7418/guizang-social-card-skill, 7.4k stars), Weekly Changelog Video (heygen-com/hyperframes, 59k stars), Anthropic Brand Styling (anthropics/skills, 180k stars) and Native Subtitle Quote Image (chengyi-ai/native-subtitle-quote-image, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
nodetool-ai (a GitHub organization) maintains it in nodetool-ai/nodetool, which has 556 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on October 8, 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.