Govern skill library lifecycle with SKILL.md contracts and lifecycle sidecars.
npx skills add https://github.com/thistleknot/skills --skill skill-wiki
Please help me install this Agent Skill. Skill: skill-wiki Source: https://github.com/thistleknot/skills/tree/main/skill-wiki Command: npx skills add https://github.com/thistleknot/skills --skill skill-wiki
skill-wiki prevents agents from repeatedly re-deriving behavioral contracts by providing a living, evidence-driven editorial pipeline for when to author, update, promote, and supersede skills.
Use skill-wiki to create or update a new skill contract by running its editorial workflow and ensuring the resulting SKILL.md includes evidence-backed applicability and the required lifecycle fields.
High-intent search queries and answers about installing and using this skill.
Skill lifecycle governance manages reusable procedural memory by turning session observations into validated SKILL.md contracts. You need it when agents repeatedly re-derive behavioral contracts, causing maintenance bottlenecks and stale operational guidance.
To author a skill contract, run the editorial workflow from integrate/intake through staged drafts to promotion gates. Ensure the resulting SKILL.md includes YAML frontmatter, contract-focused instructions, an applicability envelope, and lifecycle sidecars for evidence.
Yes, skill-wiki operates without external dependencies, relying entirely on internal editorial workflows. It enforces a contract-first anatomy separating invocable behavior contracts from provenance and maintenance files like HISTORY.md and EVIDENCE.md.
The best way to prevent stale guidance is running periodic library health sweeps. These sweeps update staleness signals, verify superseded skills, and route recurring behavioral patterns through pre-staged vetting before they become active skills.
Maintenance bottlenecks occur when agents lack an evidence-driven editorial pipeline, forcing them to repeatedly re-derive behavioral contracts. Implementing pattern-store centric compounding with promotion gates reduces these bottlenecks by vetting recurring procedures before activation.
You should not use contract-first skill anatomy when your agentic toolchain cannot support YAML frontmatter or lifecycle sidecars. The system requires structured evidence curation and editorial governance to properly supersede and update stale operational practices.
aget-frameworkCapture and categorize research observations into AGET knowledge base session files.
jdforsytheAudit agent, skill, and template libraries for duplicates and stale items.
hjemmesidekongenExtract atomic instincts from JSONL observations and update YAML definitions.
PaulBader-impDocument operational procedures for managing the imp-assistant repository.
