Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
Set up machine-wide agent memory and open the local project workbench.
Install Docmancer Onboarding
$ npx skills add docmancer/docmancer --skill docmancer-onboarding -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install docmancer/docmancer docmancer-onboarding --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/docmancer/docmancer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docmancer/distribution/skills/onboarding .claude/skills/docmancer-onboarding && 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 "docmancer-onboarding" agent skill from https://github.com/docmancer/docmancer/tree/main/docmancer/distribution/skills/onboarding into .claude/skills/docmancer-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docmancer-onboarding", 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/docmancer/docmancer/tree/main/docmancer/distribution/skills/onboardingType 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 docmancer/docmancer --skill docmancer-onboarding -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install docmancer/docmancer docmancer-onboarding --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docmancer/docmancer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/docmancer/distribution/skills/onboarding .agents/skills/docmancer-onboarding && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docmancer-onboarding" agent skill from https://github.com/docmancer/docmancer/tree/main/docmancer/distribution/skills/onboarding into .agents/skills/docmancer-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docmancer-onboarding", 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 docmancer/docmancer --skill docmancer-onboarding -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install docmancer/docmancer docmancer-onboarding --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docmancer/docmancer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/docmancer/distribution/skills/onboarding .cursor/skills/docmancer-onboarding && 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 "docmancer-onboarding" agent skill from https://github.com/docmancer/docmancer/tree/main/docmancer/distribution/skills/onboarding into .cursor/skills/docmancer-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docmancer-onboarding", 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/docmancer/docmancer.git --path docmancer/distribution/skills/onboarding--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 docmancer/docmancer --skill docmancer-onboarding -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install docmancer/docmancer docmancer-onboarding --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docmancer/docmancer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/docmancer/distribution/skills/onboarding .gemini/skills/docmancer-onboarding && 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 "docmancer-onboarding" agent skill from https://github.com/docmancer/docmancer/tree/main/docmancer/distribution/skills/onboarding into .gemini/skills/docmancer-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docmancer-onboarding", 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 docmancer/docmancer docmancer-onboardingInstalls 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 docmancer/docmancer --skill docmancer-onboarding -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/docmancer/docmancer.git skills-src && mkdir -p .github/skills && cp -r skills-src/docmancer/distribution/skills/onboarding .github/skills/docmancer-onboarding && 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 "docmancer-onboarding" agent skill from https://github.com/docmancer/docmancer/tree/main/docmancer/distribution/skills/onboarding into .github/skills/docmancer-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docmancer-onboarding", 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 docmancer/docmancer --skill docmancer-onboarding -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install docmancer/docmancer docmancer-onboarding --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docmancer/docmancer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/docmancer/distribution/skills/onboarding .opencode/skills/docmancer-onboarding && 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 "docmancer-onboarding" agent skill from https://github.com/docmancer/docmancer/tree/main/docmancer/distribution/skills/onboarding into .opencode/skills/docmancer-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docmancer-onboarding", 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
docmancer-onboarding- GitHub stars
- 129
- Token cost
- ~151 tokens
- SKILL.md length
- 75 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Set up machine-wide agent memory and open the local project workbench.
- Works in 4 steps: Run docmancer setup once on the machine. → Change to the project and run docmancer… → Run docmancer status to inspect local… → …
- Tasks that involve Agent memory
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Docmancer Onboarding is an agent skill from docmancer/docmancer. Set up machine-wide agent memory and open the local project workbench.
Its SKILL.md is about 150 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 Agent Workflows, covering Agent memory. The repository describes itself as: Find out what your coding agents already know. Docmancer indexes the memory, rules, and instructions Claude Code, Codex, Cursor, and Gemini wrote on your machine, then carries… The licence is MIT.
When your agent uses it
- Tasks that involve Agent memory
Example prompts
- “/docmancer-onboarding”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Run docmancer setup once on the machine.
- Change to the project and run docmancer web. The workbench safely creates or adopts the project tree and refreshes changed agent sources.
- Run docmancer status to inspect local health.
- Use docmancer import only when the user asks to copy arbitrary Markdown into the project inbox.
What it can do on your machine
Read from SKILL.md and the folder at commit c5c76c6. 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.
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
Docmancer Onboarding loads about 151 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 75 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 docmancer/docmancer at commit c5c76c6, republished under its MIT licence (© docmancer). 75 words, ~151 tokens.
Download SKILL.mdSave it as
.claude/skills/docmancer-onboarding/SKILL.md (or your agent's skills folder).- name
- docmancer-onboarding
- description
- Set up machine-wide agent memory and open the local project workbench.
Onboard Docmancer
- Run
docmancer setuponce on the machine. - Change to the project and run
docmancer web. The workbench safely creates or adopts the project tree and refreshes changed agent sources. - Run
docmancer statusto inspect local health. - Use
docmancer import <path>only when the user asks to copy arbitrary Markdown into the project inbox.
Onboarding does not enable capture hooks, connect Cloud, publish Team memory, or rewrite existing memory files.
© docmancer, MIT. 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 docmancer/distribution/skills/onboarding of docmancer/docmancer.
Open the folder on GitHubat commit c5c76c6
Compare with similar skills
Docmancer Onboarding 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 |
|---|---|---|---|---|---|---|
| Docmancer Onboarding this skilldocmancer/docmancer | 129 | — | ~151 | Automated safety check: Pass | MIT | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Beads Task Memorygastownhall/beads | 28k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Reflect on Session Learningscursor/plugins | 10k | 5 repos | ~1.2k | Automated safety check: Pass | None | |
| MemPalace Memory SearchMemPalace/mempalace | 59k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Compound Learning WriterEveryInc/compound-engineering-plugin | 25k | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
Beads Task Memory
gastownhall/beads
Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.
- Official
Reflect on Session Learnings
cursor/plugins
Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.
MemPalace Memory Search
MemPalace/mempalace
Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.
Compound Learning Writer
EveryInc/compound-engineering-plugin
Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.
Session History Search
slopus/happy
Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.
More from docmancer/docmancer
Docmancer
docmancer/docmancer
Work from the same local memory as every other coding agent on this machine.
Docmancer Memory
docmancer/docmancer
Recall and write source-attributed local memory. An agent skill from docmancer/docmancer.
Docmancer Memory Writing
docmancer/docmancer
Write deliberate source-attributed local memory. An agent skill from docmancer/docmancer.
Docmancer Search Before Answer
docmancer/docmancer
Recall prior project decisions and supporting agent evidence before answering.
Recall
docmancer/docmancer
Recall source-attributed local memory before work. An agent skill from docmancer/docmancer.
Related
Categories
Questions about Docmancer Onboarding
What does Docmancer Onboarding do?
Set up machine-wide agent memory and open the local project workbench. Docmancer Onboarding is an agent skill from docmancer/docmancer. Set up machine-wide agent memory and open the local project workbench.
When should I use Docmancer Onboarding?
Docmancer Onboarding fits situations like: tasks that involve Agent memory.
How do I install Docmancer Onboarding in Claude Code?
Run `npx skills add docmancer/docmancer --skill docmancer-onboarding -a claude-code`. Or copy the skill folder (docmancer/distribution/skills/onboarding in docmancer/docmancer) into .claude/skills/docmancer-onboarding in your project. Claude Code loads it when a task matches its description.
How do I install Docmancer Onboarding in Codex?
Run `npx skills add docmancer/docmancer --skill docmancer-onboarding -a codex`. Or copy the skill folder (docmancer/distribution/skills/onboarding in docmancer/docmancer) into .agents/skills/docmancer-onboarding in your project. Codex loads it when a task matches its description.
Can I use Docmancer Onboarding 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 docmancer/docmancer --skill docmancer-onboarding -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docmancer-onboarding, .gemini/skills/docmancer-onboarding, .github/skills/docmancer-onboarding and .opencode/skills/docmancer-onboarding in your project.
What does Docmancer Onboarding need to run?
SKILL.md names no scripts, command-line tools or credentials: Docmancer Onboarding is instructions for the agent only.
Does Docmancer Onboarding 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 Docmancer Onboarding 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 Docmancer Onboarding use?
Docmancer Onboarding is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Docmancer Onboarding use?
About 151 tokens (SKILL.md is roughly 604 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 Docmancer Onboarding?
Skills that share tags, products or a category with Docmancer Onboarding: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Beads Task Memory (gastownhall/beads, 28k stars), Reflect on Session Learnings (cursor/plugins, 10k stars) and MemPalace Memory Search (MemPalace/mempalace, 59k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docmancer Onboarding?
docmancer (a GitHub organization) maintains it in docmancer/docmancer, which has 129 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on August 13, 2026.
Source: docmancer/docmancer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.