capture skill
Record what people decided in this session in the wiki pages it affects (team or local wiki). Use when the user asks to capture or record what the session decided, or when a wiki reminder asks you to.
- GitHub stars
- 36
- Files
- 1
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the capture skill do?
capture is an agent skill. Record what people decided in this session in the wiki pages it affects (team or local wiki). Use when the user asks to capture or record what the session decided, or when a wiki reminder asks you to.
How to install the capture skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the capture skill in Plugin
/plugin marketplace add nimbalyst/nimbalyst-wiki /plugin install nimbalyst-wiki@nimbalyst-wiki
Install the capture skill in Claude Code
~/.claude/skills/capture/SKILL.md
$ npx degit nimbalyst/nimbalyst-wiki/skills/capture ~/.claude/skills/captureInstall the capture skill in Claude Code (project)
.claude/skills/capture/SKILL.md
$ npx degit nimbalyst/nimbalyst-wiki/skills/capture .claude/skills/captureInstall the capture skill in Codex
~/.agents/skills/capture/SKILL.md
$ npx degit nimbalyst/nimbalyst-wiki/skills/capture ~/.agents/skills/captureInstall the capture skill in Gemini CLI
~/.gemini/skills/capture/SKILL.md
$ npx degit nimbalyst/nimbalyst-wiki/skills/capture ~/.gemini/skills/captureInstall the capture skill in Claude.ai
npx degit nimbalyst/nimbalyst-wiki/skills/capture capture && zip -r capture.zip capture # claude.ai → Customize → Skills → + → Create skill → Upload a skill → capture.zip
SKILL.md
View on GitHubRecord what this session decided in the project's wiki. Load the update skill and follow it for every write; the connect skill covers choosing the wiki and finding the project.
Focus, if the user gave one: $ARGUMENTS (left as written or empty means the whole session)
- If the desktop app's wiki tools are available (
mcp__nimbalyst-trackers__*), use them and the desktop wiki skills instead of this plugin's tools. - Choose the wiki as the
connectskill describes. For the team wiki, callpages_statuswithrepoandproject; if the state isambiguous, ask which project and pin it; if it isunbound, follow the skill's connecting steps. For a local wiki, use thenimbalyst-localtools; if there is none yet, offer to start one. If there is still no wiki to write to, say so and stop. - Read the guide page ("How we write this wiki":
guideLinkon the team wiki,listPageson a local one) and follow it. - On a local wiki, start from the code: call
pagesForFileswith the files this session changed (no arguments checks the working tree; when the work is already committed, pass the files, orsincewith the commit before it). For each page it returns, read it and either update it with what the change means for a reader, or, when you cannot say that well, set itsstatustooutdated(setPageFields, ortracker_updateon a typed page) and add one line saying what changed and where.stalemeans a covered file was committed after the page last changed, which may include commits from before this session; record what this session changed and say the page may lag further rather than guessing at older changes. Skip a page the change does not affect in meaning. - List the candidates from this session: decisions people made (who, what was not chosen, and why), questions answered or left open, and context a teammate would need to see the whole problem. Drop routine progress and anything the code or
git logalready says. - If nothing is left and no page needed updating, reply "nothing to record" and stop.
- Otherwise, find the page each candidate affects with
listPagesandreadCollabDoc, and write it there as the skill says: a decided or open mark on the sentence, a citation fromlist_session_inputswhen the person's own words support it. Extend existing pages; create a page only when none fits. When the project came from a pin or the user is in several teams, first say which project the writes go to; on a local wiki, say which folder. - End your reply with the pages you updated or marked outdated, one link per line.
Files in this skill
1capture skill questions
How do I install the capture skill in Claude Code?
Run npx degit nimbalyst/nimbalyst-wiki/skills/capture ~/.claude/skills/capture. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the capture skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.