archivist-stinger — Claude Code skill: what it does, how to install
archivist-stinger prepares an acquired repository for long-term archival by scrubbing seller attribution, merging documentation into library/, and building a knowledge base.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install documentation-tools@wasp-nestWhat archivist-stinger does
This skill converts an acquired codebase into an archival research artifact across six distinct phases. It checks project provenance, purges seller attribution and personal identifiers while keeping third-party notices untouched, relocates scattered documentation into Library Schema v2, generates reference documents with subagents, and audits the changes.
The tool relies on markdown templates alongside helper Python scripts that run searches, prepare replacement tables, and verify file integrity. Every helper script works exclusively with the Python 3.10+ standard library. The utilities remain read-only unless you deliberately pass the --apply flag.
Without documented proof of repository ownership, the intake gate terminates execution immediately. The skill refuses to touch any repository file until an operator signs the intake manifest.
What it helps with
- sanitize vendor attribution and personal data from an acquired codebase
- consolidate scattered project documentation into the
library/tree - preserve third-party notices while stripping seller license claims
- generate a final archival report highlighting open decisions
Example prompts for the agent
- Prepare this acquired codebase for archival as a research object
- Scrub former owner attribution, personal identifiers, and licenses
- Consolidate legacy documents into
library/and build the knowledge base
How to install archivist-stinger
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install documentation-tools@wasp-nestThis installs the whole documentation-tools plugin with all its skills
2Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill archivist-stinger -a claude-code3Manually: put the files in place
~/.claude/skills/archivist-stinger/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/archivist-stinger/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill archivist-stinger -a codex2Manually: put the files in place
.agents/skills/archivist-stinger/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill archivist-stinger -a cursor2Manually: put the files in place
.cursor/skills/archivist-stinger/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/documentation-tools/skills/archivist-stinger2Manually: put the files in place
.github/skills/archivist-stinger/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill archivist-stinger -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/documentation-tools/skills/archivist-stingerManually: put the files in place
.devin/skills/archivist-stinger/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about archivist-stinger
How do I install archivist-stinger in Claude Code?
Register the marketplace with /plugin marketplace add legioncodeinc/vibe-coding-tools, then run /plugin install documentation-tools@wasp-nest. Alternatively, add it directly using npx skills add legioncodeinc/vibe-coding-tools --skill archivist-stinger -a claude-code.
What dependencies does archivist-stinger require?
You need Python 3.10 or newer to run the internal verification and replacement tools. The scripts use only the Python standard library, so external packages are not needed.
Does archivist-stinger wipe third-party licenses?
No, third-party dependency notices and license files remain untouched. The scrub isolates and removes only first-party seller credits, identities, and proprietary grants.