Upgrade
Apply plugin knowledge base updates to an existing generated system.
Install
npx skills add agenticnotetaking/arscontexta --skill upgrade -g -a claude-code -y- Repository
- agenticnotetaking/arscontexta3.5k
- Category
- Writing
- Updated
- 8mo ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".
Runtime Configuration (Step 0, before any processing)
Read these files to configure domain-specific behavior:
-
ops/derivation-manifest.md, vocabulary mapping, platform hints- Use
vocabulary.notesfor the notes folder name - Use
vocabulary.note/vocabulary.note_pluralfor note type references - Use
vocabulary.reducefor the extraction verb - Use
vocabulary.reflectfor the connection-finding verb - Use
vocabulary.reweavefor the backward-pass verb - Use
vocabulary.verifyfor the verification verb - Use
vocabulary.rethinkfor the meta-cognitive verb - Use
vocabulary.topic_mapfor MOC references
- Use
-
ops/config.yaml, processing depth, domain context -
ops/derivation.md, derivation state and engine version
If these files don't exist, use universal defaults.
EXECUTE NOW
Target: $ARGUMENTS
Parse immediately:
- If target contains a specific skill name (e.g., "upgrade reduce"): check only that skill
- If target contains "--all": check all generated skills
- If target is empty: check all generated skills (same as --all)
START NOW. Reference below defines the upgrade process.
Why Consultation, Not Hashing
Skills do not upgrade through hash comparison against a generation manifest. Hash comparison answers a narrow question: "Has this file changed?" Meta-skill consultation answers the right question: "Is this skill's approach still the best approach given what we know?"
A skill could be unchanged but outdated because the knowledge base has grown. Or a skill could be heavily edited by the user but already incorporate the latest thinking through a different path. Reasoning about methodology is more valuable than diffing bytes.
Two Upgrade Paths
Generated skills and meta-skills follow fundamentally different upgrade mechanisms:
