Gh Stack
remotion-dev/remotion
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack.
Call nodetool.settings or nodetool.secrets from a code action: read or change a NodeTool setting, find out which credentials are configured, ask the user to enter a missing API key, or read a secret…
$ npx skills add nodetool-ai/nodetool --skill api-settings -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nodetool-ai/nodetool api-settings --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/api-settings .claude/skills/api-settings && 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 "api-settings" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-settings into .claude/skills/api-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-settings", 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/api-settingsType 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 api-settings -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nodetool-ai/nodetool api-settings --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/api-settings .agents/skills/api-settings && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "api-settings" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-settings into .agents/skills/api-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-settings", 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 api-settings -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nodetool-ai/nodetool api-settings --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/api-settings .cursor/skills/api-settings && 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 "api-settings" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-settings into .cursor/skills/api-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-settings", 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/api-settings--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 api-settings -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nodetool-ai/nodetool api-settings --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/api-settings .gemini/skills/api-settings && 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 "api-settings" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-settings into .gemini/skills/api-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-settings", 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 api-settingsInstalls 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 api-settings -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/api-settings .github/skills/api-settings && 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 "api-settings" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-settings into .github/skills/api-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-settings", 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 api-settings -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 api-settings --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/api-settings .opencode/skills/api-settings && 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 "api-settings" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-settings into .opencode/skills/api-settings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-settings", 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.
api-settingsCall nodetool.settings or nodetool.secrets from a code action: read or change a NodeTool setting, find out which credentials are configured, ask the user to enter a missing API key, or read a secret…
API Settings is an agent skill from nodetool-ai/nodetool. Call nodetool.settings or nodetool.secrets from a code action: read or change a NodeTool setting, find out which credentials are configured, ask the user to enter a missing API key, or read a secret in a script. Load before the first call into these namespaces.
Its SKILL.md is about 660 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.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit f99c652. 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 these keys or tokens, usually read from environment variables:
STRIPE_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
API Settings loads about 663 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 352 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 f99c652, republished under its AGPL-3.0 licence (© nodetool-ai). 352 words, ~663 tokens.
.claude/skills/api-settings/SKILL.md (or your agent's skills folder).nodetool.settings is the configuration of this install. nodetool.secrets
reads credentials inside a run. A secret value never passes through the agent:
the user types it in a dialog.
| Call | Does | Answers |
|---|---|---|
list({group}) | Lists every setting, or one group ("Folders", for example), with its description, allowed values and current value. Secrets are not in this list. | {settings, groups} |
get(key) | Reads one setting, from the user's saved settings and then the environment. Refuses a secret. | The setting with its value and source (user, env or unset) |
set(key, value) | Changes one setting for this user. Only a declared setting can be set, and a setting with allowed values takes only those. value is a string. | — |
secrets() | Lists the known credentials and whether each one is configured. | Names and a configured flag. Never values. |
requestSecret(key, {reason, help_url}) | Opens a dialog in the user's client where they type the value. | Only whether they saved one |
key is the environment-variable name: "AUTOSAVE_INTERVAL_MINUTES",
"STRIPE_API_KEY".
secrets() to see what is missing, and use the name the service is
registered under.requestSecret(key, {reason, help_url}). Write reason for the user,
in one sentence. help_url is where they get the key.A run with no interactive client refuses the request. Then tell the user which credential is missing and where to add it (Settings > Secrets). Do not ask again in a loop, and never ask the user to paste a key into the chat.
For code that needs a credential value, such as a Code node or a script:
| Call | Does |
|---|---|
get(name) | The value. It throws and names the secret when it is not set. |
tryGet(name) | The value, or undefined for a credential that is optional |
list() | The names this node declared in its secret scope, or null when it declared none |
A read works only for a name inside the secret scope of the run. A chat
action has no secret store, so nodetool.secrets.get throws there. Use the
tools that hold the credential on the host instead of reading it.
© 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/api-settings of nodetool-ai/nodetool.
Open the folder on GitHubat commit f99c652
API Settings 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 |
|---|---|---|---|---|---|---|
| API Settings this skillnodetool-ai/nodetool | 554 | — | ~663 | Automated safety check: Pass | AGPL-3.0 | |
| Gh Stackremotion-dev/remotion | 62k | 6 repos | ~2.4k | Automated safety check: Pass | Custom licence | |
| HyperFrames Media Useheygen-com/hyperframes | 58k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.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 | 58k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Anthropic Brand Stylinganthropics/skills | 180k | 29 repos | ~559 | Automated safety check: Pass | Apache-2.0 |
remotion-dev/remotion
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack.
heygen-com/hyperframes
Finds, generates and edits media for HyperFrames video projects: music, sound effects, images, icons, logos, voiceovers, captions and color grades.
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.
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.
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
Call nodetool.settings or nodetool.secrets from a code action: read or change a NodeTool setting, find out which credentials are configured, ask the user to enter a missing API key, or read a secret…. API Settings is an agent skill from nodetool-ai/nodetool.secrets from a code action: read or change a NodeTool setting, find out which credentials are configured, ask the user to enter a missing API key, or read a secret in a script.
API Settings fits situations like: media & Creative work in your project.
Run `npx skills add nodetool-ai/nodetool --skill api-settings -a claude-code`. Or copy the skill folder (packages/system-skills/api-settings in nodetool-ai/nodetool) into .claude/skills/api-settings in your project. Claude Code loads it when a task matches its description.
Run `npx skills add nodetool-ai/nodetool --skill api-settings -a codex`. Or copy the skill folder (packages/system-skills/api-settings in nodetool-ai/nodetool) into .agents/skills/api-settings 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 api-settings -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-settings, .gemini/skills/api-settings, .github/skills/api-settings and .opencode/skills/api-settings in your project.
Going by SKILL.md and its folder, API Settings needs credentials named STRIPE_API_KEY. Our summary lists: A credential in STRIPE_API_KEY.
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.
API Settings 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 663 tokens (SKILL.md is roughly 2.7k 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 API Settings: Gh Stack (remotion-dev/remotion, 62k stars), HyperFrames Media Use (heygen-com/hyperframes, 58k stars), Guizang Social Cards (op7418/guizang-social-card-skill, 7.4k stars) and Weekly Changelog Video (heygen-com/hyperframes, 58k 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 554 GitHub stars. The repository holds 130 skills in this directory. The repository was last updated on October 7, 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.