vitya
0eb7dd1d7c
setup-interns (v0.1.0) — 8-phase install of the local `interns` MCP server:
detect `.common/lib/interns-mcp/` source, `pip install -e`, write
`.common/secrets/interns.env` with endpoint API keys (gitignored), register
`mcpServers.interns` in `~/.claude.json` with absolute Python interpreter
path + `cwd` so the runtime resolves config relative to project root.
Mirrors setup-projects-meta / setup-context7 confirmation-gate shape.
Description 899 chars (under the 900 budget per
feedback_skill_description_length_limit).
using-interns (v0.1.0) — runtime policy for `mcp__interns__*`. Per-session
permission grant mirrors project-discipline Rule 4: ask-mode default,
conversational grant ("разреши интернов" / "allow interns"), conversational
revoke, always-ask paths for `**/.env`, `**/secrets/**`, `**/*.key`,
`**/.ssh/**`, `**/.aws/credentials` etc with transitive rule (Claude can't
bypass by reading the file with the local Read tool and forwarding content),
cost-cap >$0.10 always asks, session-end automatic reset. Routing hints for
`bulk_text_read` (3+ files or one file >400 lines) and `transcript_distill`
(before .wiki/log.md updates / session summaries). Description 814 chars.
project-bootstrap (1.5.0 -> 1.6.0, MINOR — capability added):
* assets/CLAUDE.md.template: insert `delegate to interns when allowed`
between `follow project discipline` and `we're on Windows`.
* SKILL.md Step 5: same insertion in inline template + new commentary
paragraph explaining the trigger, no-op semantics, install pointer.
* SKILL.md Step 5.5: bootstrap-manifest table extended with
`setup-interns`, `using-interns`, `project-discipline` rows.
* README.md: Workflow Step 5.5 description + See also section both pick up
the new skills.
Root CLAUDE.md dogfood: `delegate to interns when allowed` line added.
.wiki/log.md decision entry. .tasks/STATUS.md task moved to 🟢 done.
.tasks/interns-skills-mvp.md per-task file with goal / key-files /
decisions log / open questions.
Build + install verified: `dist/{setup-interns,using-interns,
project-bootstrap}.skill` rebuilt; `bash scripts/install.sh ...` succeeded;
harness skill listing shows full descriptions for all three (no H1
fallback) — confirms the description budget held.
Versioning per project-discipline Rule 3:
* setup-interns: 0.1.0 (first edit of unversioned artifact, MAJOR=0).
* using-interns: 0.1.0 (first edit of unversioned artifact, MAJOR=0).
* project-bootstrap: 1.5.0 -> 1.6.0 (MINOR — adds capability without
breaking existing CLAUDE.md merge or manifest consumers).
Server runtime itself (`.common/lib/interns-mcp/`) is out of scope for this
task — the skills land lifecycle, policy, and bootstrap integration so any
machine where the MCP server is later installed already has Claude's
policy in place.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
claude-skills
Russian version: README.ru.md.
Joint workshop and storage for Claude skills.
About
A shared workspace where Claude and I author, debug, and ship skills together:
skills/— editable sources (markdown + assets), the source of truthdist/— built.skillarchives, committed to the reposcripts/— utilities:build.sh(source →.skill),install.sh(source →~/.claude/skills/).wiki/,.tasks/— working notes and the task board
Quick start
Install skills on a fresh machine
Windows (PowerShell):
git clone <repo> claude-skills
cd claude-skills
bash scripts/install.sh # copies every skills/* into ~/.claude/skills/
# or only specific ones:
bash scripts/install.sh caveman wiki-maintainer
Linux / macOS (bash):
git clone <repo> claude-skills
cd claude-skills
bash scripts/install.sh # copies every skills/* into ~/.claude/skills/
# or only specific ones:
bash scripts/install.sh caveman wiki-maintainer
The install target can be overridden with CLAUDE_SKILLS_DIR=/path bash scripts/install.sh.
install.shworks on Windows under git-bash. A nativeinstall.ps1is on the task board but not yet implemented.
Using skills in projects
Once the skills are installed, the easiest way to wire them into a new
(or existing) project is the project-bootstrap
skill. Tell the agent "bootstrap" or "set everything up" from the
project's folder and it will, in one pass:
- initialize
git(if missing) and write a sane.gitignore - create a starter
README.md - lay out
.wiki/per the Karpathy LLM Wiki pattern (delegated tosetup-wiki) - lay out
.tasks/with the canonical task board (delegated tosetup-tasks) - write
CLAUDE.mdwith skill triggers (use superpowers,use project wiki,use task management system,check across all projects,we're on Windows) - record the skill versions used in
.wiki/concepts/bootstrap-manifest.mdso cross-project layout drift stays debuggable - check whether the official
superpowers@claude-plugins-officialplugin is installed and, if not, print the install command — theuse superpowerstrigger is a no-op without it
Two modes, picked automatically: init for an empty folder, upgrade
for an existing project (the skill only fills the gaps and never overwrites
without explicit confirmation). On upgrade, CLAUDE.md is merged
idempotently — only canonical trigger lines that aren't already present are
appended after explicit confirm, so re-running project-bootstrap after a
template change picks up the new triggers without duplicating the old ones.
Edit a skill
# 1. Edit skills/<name>/SKILL.md (or its assets).
# 2. Push the changes into the live skill folder:
bash scripts/install.sh <name>
# 3. Rebuild the archive (optional, but handy before a commit):
bash scripts/build.sh <name>
Build .skill archives
bash scripts/build.sh # all skills
bash scripts/build.sh caveman # one skill
build.sh uses zip when it's available (Linux/macOS) or delegates to
scripts/build.ps1 via PowerShell (Windows without zip). On Windows you
can also run powershell scripts/build.ps1 directly.
Layout
claude-skills/
├── skills/ ← sources (one folder per skill)
├── dist/ ← .skill archives (committed)
├── scripts/
│ ├── build.sh / build.ps1
│ └── install.sh
├── .wiki/ ← design docs, notes
├── .tasks/ ← STATUS.md
├── CLAUDE.md
└── README.md (this file — see README.ru.md for Russian)
For the principles and decisions behind this layout see
.wiki/concepts/repo-layout.md.