Releases: intelligentrascal/skill-manager
Release list
Skill Manager v0.8.0 - The Redesign
The Redesign
Skill Manager v0.7.0 - Provenance, Updates, Variants
Skill Manager v0.7.0 - Provenance, Updates, Variants
The control plane arrives. Third-party skills now know where they came from, can be updated from their originals, and adapt to agents they were never written for.
🧬 Three new capabilities
1. Provenance - every skill knows its origin
A committed skillmgr.yaml records what each skill is and where it came from:
| state | meaning |
|---|---|
upstream |
third-party skill, tracks its original repo |
mine |
originated in your repo |
promoted |
third-party skill you adopted as your own |
upstream-edited |
third-party skill with local edits (a conflict to resolve) |
Identity is the canonical upstream URL + subpath + pinned revision - never a name, never HEAD-guessing. Frontmatter extraction is only a suggested import; the manifest is the authority.
2. Upstream updates - track the original, not just your repo
- Preview a full-directory diff at a pinned revision (added / removed / modified files)
- Security gate: typed acknowledgement required when executable behavior appears or changes
- Staged apply with rollback - never a silent overwrite
- Built, tested, and manifest-gated: activates when your
skillmgr.yamldeclares pinned sources
3. Variants - claude-only becomes everywhere
A claude-only skill becomes a linked variant for pi / opencode / codex:
- Invocation fields (
argument-hint,user-invocable, ...) dropped, guidance folded into the description - pi keeps
allowed-tools+disable-model-invocation(it honors both) - opencode gets triggers added
- Full snapshots in a sidecar store, deployed explicitly, verified before they stay (removed fields must be gone)
- Variants are linked, never drift, never duplicates - the status model gained a
VARIANTstate
⚡ Performance - 24x faster cold load
Root cause: the repoClean check spawned a separate git status process per repo copy - 223 sequential spawns on Windows.
Fix: one batch git status --porcelain -uall call, checked in memory.
| before | after | |
|---|---|---|
| cold load | 13.9s | 0.57s |
| refresh cycle | slow | 1.12s |
🤝 Built by three agents, cross-reviewed
- A - provenance manifest: schema, strict validation, scanner integration
- B - update engine: shallow-clone fetch, diff, security gate, staged apply + rollback
- C - variant engine: adaptation rules, sidecar store, deploy, verification loop
Each agent's work was reviewed by another; the review loop caught real errors (pi profile semantics, precedence honesty, trust-gated discovery) before anything shipped. 45 tests green, typecheck clean.
📚 Docs
- README: provenance, upstream updates, variants, the revised status model
- Onboarding guide: new Provenance / Updates / Variants section
- BUILD-SPEC: full A+B+C track documentation
- The multi-agent build, visualized
Next: seed a real skillmgr.yaml from the fleet to activate upstream updates, then the UI/UX redesign (final phase).
Skill Manager v0.6.0 - Explain + Adaptation Suggestions
New in v0.6.0
Skill Manager v0.5.0 - Portability
New in v0.5.0 - the knowledge layer
Skill Manager v0.4.0 - Visibility + Search
New in v0.4.0
Skill Genome v0.3.0
The Skill Genome - a living wall of your entire skill fleet.