kvb-skills-dream, -tune, -auto, -essence and -transcend become kvb-skill-*, and tests/test_naming.py now requires the category skill. enable-plugins.js registers the reminder hooks under the new names and repoints hook commands of the previous kvb-skills-* paths as well as the older autotune/dream paths; test_dream covers both generations. References in kvb-check-confidence, kvb-org-perform, kvb-org-rasci, kvb-transcend, the tests and the README organigram and skill map follow. The header comments of both reminder hooks and enable-plugins.js are dropped. BREAKING CHANGE: /kvb-skills-dream, /kvb-skills-tune, /kvb-skills-auto, /kvb-skills-essence and /kvb-skills-transcend are now /kvb-skill-*. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.7 KiB
1.7 KiB
name, description
| name | description |
|---|---|
| kvb-transcend | Run both transcend skills in one pass. Trigger on /kvb-transcend. |
Collector for the kvb-skill-transcend and kvb-code-transcend skills, so
one harvest needs one round of questions. Its script finds the candidates and
remembers every decision, so a rescan offers only what is new or changed:
transcend.py scan --state <skills repo>/.state/transcend.json \
--skills-repo <skills repo> --session-dir <own scratchpad> \
--peers-root /tmp/claude-<uid> --home ~ [--json]
transcend.py mark --state <same> <path> carried|dropped|later
${CLAUDE_SKILL_DIR}/scripts/transcend.py scans three sources: the own
scratchpad, every peer session's scratchpad, and the agent homes
(~/.claude, ~/.agents, ~/.codex) for skills, commands, agents, hooks
and rules the skills repository does not ship. It keeps scripts, tests and
skills, and skips files named like secrets and files over 1 MB. Carried or
dropped candidates return only when their content changes; later returns
every time.
- Scan, then classify each candidate by both skills' classify steps.
- Consent: a peer's candidates go to that peer, one message listing them, and only what it releases stays; home candidates need the operator's yes.
- One
kvb-think-listenround and one confirmation for all candidates, grouped by target: the skills repository or the current repository. In the skills repository itself, scripts and skills go tokvb-skill-transcend, tests tokvb-code-transcend. - Hand each confirmed candidate to its skill's write step, then
markevery offered candidate with its verdict. - One table:
| Candidate | Source | Target | Verdict |.