Menu

Individual skill

capture

0upvotes

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.

plugins/nimbalyst-wiki/skills/capture/SKILL.md

Read pinned source

Source commit 826adb4f93dbe86db35b76ce2502a3a33abe0489

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,049
Repository last updated
Nov 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Record 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)

1. 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.
2. Choose the wiki as the `connect` skill describes. For the team wiki, call `pages_status` with `repo` and `project`; if the state is `ambiguous`, ask which project and pin it; if it is `unbound`, follow the skill's connecting steps. For a local wiki, use the `nimbalyst-local` tools; if there is none yet, offer to start one. If there is still no wiki to write to, say so and stop.
3. Read the guide page ("How we write this wiki": `guideLink` on the team wiki, `listPages` on a local one) and follow it.
4. On a local wiki, start from the code: call `pagesForFiles` with the files this session changed (no arguments checks the working tree; when the work is already committed, pass the files, or `since` with 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 its `status` to `outdated` (`setPageFields`, or `tracker_update` on a typed page) and add one line saying what changed and where. `stale` means 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.
5. 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 log` already says.
6. If nothing is left and no page needed updating, reply "nothing to record" and stop.
7. Otherwise, find the page each candidate affects with `listPages` and `readCollabDoc`, and write it there as the skill says: a decided or open mark on the sentence, a citation from `list_session_inputs` when 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.
8. End your reply with the pages you updated or marked outdated, one link per line.
Back to top