Music To Video
chmonitor/chmonitor
A skill your agent uses when the user has a music track (an audio file, or a video to pull audio from) and wants a beat-synced HyperFrames video, calm to hard-hitting.
Call nodetool.memory, nodetool.shared or nodetool.threads from a code action: save and recall durable notes and resources across conversations, pass results between steps and sub-agents in one run…
Install API Memory
$ npx skills add nodetool-ai/nodetool --skill api-memory -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nodetool-ai/nodetool api-memory --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-memory .claude/skills/api-memory && 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-memory" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-memory into .claude/skills/api-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-memory", 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-memoryType 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-memory -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nodetool-ai/nodetool api-memory --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-memory .agents/skills/api-memory && 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-memory" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-memory into .agents/skills/api-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-memory", 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-memory -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nodetool-ai/nodetool api-memory --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-memory .cursor/skills/api-memory && 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-memory" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-memory into .cursor/skills/api-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-memory", 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-memory--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-memory -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nodetool-ai/nodetool api-memory --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-memory .gemini/skills/api-memory && 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-memory" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-memory into .gemini/skills/api-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-memory", 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-memoryInstalls 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-memory -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-memory .github/skills/api-memory && 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-memory" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-memory into .github/skills/api-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-memory", 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-memory -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-memory --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-memory .opencode/skills/api-memory && 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-memory" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-memory into .opencode/skills/api-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-memory", 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
api-memory- GitHub stars
- 556
- Token cost
- ~894 tokens
- SKILL.md length
- 400 words
- Files
- 1
- Skills in repo
- 127
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Call nodetool.memory, nodetool.shared or nodetool.threads from a code action: save and recall durable notes and resources across conversations, pass results between steps and sub-agents in one run…
- Tasks that involve Subagents
- SKILL.md covers nodetool.memory, nodetool.shared and nodetool.threads
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
API Memory is an agent skill from nodetool-ai/nodetool. Call nodetool.memory, nodetool.shared or nodetool.threads from a code action: save and recall durable notes and resources across conversations, pass results between steps and sub-agents in one run, and read past chat threads. Load before the first call into these namespaces.
Its SKILL.md is about 890 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, covering Subagents. The repository describes itself as: Agent-first Creative Workspace. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve Subagents
Example prompts
- “/api-memory”
What it can do on your machine
Read from SKILL.md and the folder at commit 515bd28. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
API Memory loads about 894 tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 400 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 515bd28, republished under its AGPL-3.0 licence (© nodetool-ai). 400 words, ~894 tokens.
Download SKILL.mdSave it as
.claude/skills/api-memory/SKILL.md (or your agent's skills folder).- name
- api-memory
- description
- Call nodetool.memory, nodetool.shared or nodetool.threads from a code action: save and recall durable notes and resources across conversations, pass results between steps and sub-agents in one run, and read past chat threads. Load before the first call into these namespaces.
nodetool.memory, nodetool.shared, nodetool.threads
Nothing carries over between code actions except what a tool saved. These three namespaces are where state lives, at three lifetimes:
| Namespace | Lifetime | Use it for |
|---|---|---|
nodetool.memory | Every conversation, until deleted | Facts, decisions, preferences, and the assets and documents you made |
nodetool.shared | This run only | Handing results between steps, tasks and sub-agents |
nodetool.threads | Read-only chat history | "What did we decide last time?" |
nodetool.memory
| Call | Does |
|---|---|
save(content, {title, kind, resources}) | Saves a note. |
search(query, {limit, thread, kinds}) | Finds notes by keyword. Every word must appear in the title or the content, so fewer words find more. limit defaults to 25. |
list({limit, thread, kinds}) | Lists notes, newest first. limit defaults to 100, max 200. |
update(memoryId, {content, title, kind, resources}) | Changes the fields you pass. resources replaces the list. |
remove(memoryId) | Deletes one note. |
kindisnote(default),fact,preference,decisionorresource.threadis"all"(default) or"current".resourcesis a list of{type, id, uri?, label?}.typeisasset,workflow,collection,node,job,timeline,script,storyboard,image_document,thread,urlorother. Asset references are checked and come back with a liveasset://uri.- The notes of the current conversation are shown to you at the start of each turn. Search for the rest.
Record what you make in the same action that makes it:
const shot = await nodetool.media.generateImage(prompt, model);
await nodetool.memory.save("Hero still for the launch film", {
title: "Hero still",
kind: "resource",
resources: [{ type: "asset", id: shot.asset_id }]
});Before you generate, search memory for a result that already exists. Never generate again what a note already records.
Show full SKILL.md (166 more words)Show less
nodetool.shared
The scratchpad of this run. It is gone when the run ends.
| Call | Does |
|---|---|
list({kind, key_prefix, sources}) | Metadata only: keys, titles, kinds, sizes. kind filters to task_result, step_result, input or shared. |
read(keys) | Full values for the keys you name. Misses come back in missing. A key with no <namespace>: prefix is also looked up under shared:. |
publish(key, value, {title, description}) | Stores any JSON value under shared:<key>. |
The results of earlier steps and tasks land here. Read them instead of asking for them again. List first, then read only the keys you need.
nodetool.threads
| Call | Does |
|---|---|
list({limit, workflow_id, cursor, preview}) | Past conversations, newest first, each with its last message unless preview: false. limit defaults to 20. |
get(threadId, {limit, newest_first, cursor, max_chars}) | A page of messages, oldest first. Text is cut at max_chars (default 2000, 0 for no cut). |
last(threadId) | The newest message, or undefined |
message(messageId) | One message in full: every tool call with its arguments, files, cost |
Page with the next cursor of the previous answer.
© 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/api-memory of nodetool-ai/nodetool.
Open the folder on GitHubat commit 515bd28
Compare with similar skills
API Memory 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 Memory this skillnodetool-ai/nodetool | 556 | — | ~894 | Automated safety check: Pass | AGPL-3.0 | |
| Music To Videochmonitor/chmonitor | 299 | 1 repos | ~4k | Automated safety check: Notes | GPL-3.0 | |
| Hearyourvoicekillernay/HearYourVOICE | 140 | — | ~10k | Automated safety check: Notes | MIT | |
| Architecture Design Reviewbbartling/open-fdd | 172 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Canvas Ops SkillOpenLoaf/OpenLoaf | 108 | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 | |
| Ultragoaljxnl/personal-monorepo-template | 562 | — | ~1.8k | Automated safety check: Pass | None |
Similar skills
Hearyourvoice
killernay/HearYourVOICE
The repeatable workflow for short Thai documentary/explainer videos — one topic in, one finished MP4 out.
Architecture Design Review
bbartling/open-fdd
A skill your agent uses to evaluate architecture, design proposals, refactors, module boundaries, dependency direction, data flow, concurrency model, and maintainability tradeoffs across any codebase.
Canvas Ops Skill
OpenLoaf/OpenLoaf
Triggered when the user wants lifecycle management of OpenLoaf canvases / whiteboards: create, open, filter, duplicate, delete, rename, or change ownership.
Ultragoal
jxnl/personal-monorepo-template
Design, critique, set, create, activate, or run durable Codex goals for persistent or long-running objectives.
Ads Quick
zubair-trabzada/ai-ads-claude
60-Second Ad Readiness Snapshot — quick assessment without subagents
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 API Memory
What does API Memory do?
Call nodetool.memory, nodetool.shared or nodetool.threads from a code action: save and recall durable notes and resources across conversations, pass results between steps and sub-agents in one run…. API Memory is an agent skill from nodetool-ai/nodetool.threads from a code action: save and recall durable notes and resources across conversations, pass results between steps and sub-agents in one run, and read past chat threads.
When should I use API Memory?
API Memory fits situations like: tasks that involve Subagents.
How do I install API Memory in Claude Code?
Run `npx skills add nodetool-ai/nodetool --skill api-memory -a claude-code`. Or copy the skill folder (packages/system-skills/api-memory in nodetool-ai/nodetool) into .claude/skills/api-memory in your project. Claude Code loads it when a task matches its description.
How do I install API Memory in Codex?
Run `npx skills add nodetool-ai/nodetool --skill api-memory -a codex`. Or copy the skill folder (packages/system-skills/api-memory in nodetool-ai/nodetool) into .agents/skills/api-memory in your project. Codex loads it when a task matches its description.
Can I use API Memory 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 api-memory -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-memory, .gemini/skills/api-memory, .github/skills/api-memory and .opencode/skills/api-memory in your project.
What does API Memory need to run?
SKILL.md names no scripts, command-line tools or credentials: API Memory is instructions for the agent only.
Does API Memory access the network?
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.
Is API Memory 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 API Memory use?
API Memory 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 API Memory use?
About 894 tokens (SKILL.md is roughly 3.6k 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 API Memory?
Skills that share tags, products or a category with API Memory: Music To Video (chmonitor/chmonitor, 299 stars), Hearyourvoice (killernay/HearYourVOICE, 140 stars), Architecture Design Review (bbartling/open-fdd, 172 stars) and Canvas Ops Skill (OpenLoaf/OpenLoaf, 108 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains API Memory?
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.