skill-tree 0.1.7 → 0.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +27 -2
- package/dist/cli/index.js +304 -210
- package/dist/cli/index.mjs +460 -360
- package/dist/index.d.mts +74 -49
- package/dist/index.d.ts +74 -49
- package/dist/index.js +232 -159
- package/dist/index.mjs +369 -288
- package/package.json +1 -1
- package/dist/cli/index.js.map +0 -1
- package/dist/cli/index.mjs.map +0 -1
- package/dist/index.js.map +0 -1
- package/dist/index.mjs.map +0 -1
package/README.md
CHANGED
|
@@ -2,6 +2,33 @@
|
|
|
2
2
|
|
|
3
3
|
A TypeScript library for managing agent skill versions and evolution. Store, version, serve, sync, and federate reusable skills for AI agents.
|
|
4
4
|
|
|
5
|
+
## Metrics ownership (as of 0.2.0)
|
|
6
|
+
|
|
7
|
+
skill-tree does **not** track per-skill usage metrics. The `Skill` shape no
|
|
8
|
+
longer carries `metrics` — historical fields like `usageCount`, `successRate`,
|
|
9
|
+
`lastUsed`, `feedbackScores` lived on it but were never updated by any code
|
|
10
|
+
path in skill-tree, and the snapshots that consumers wrote at publish time
|
|
11
|
+
drifted from the live data.
|
|
12
|
+
|
|
13
|
+
Live usage tracking belongs to systems that observe agents running:
|
|
14
|
+
- **cognitive-core** (`playbook.evolution.successCount` / `failureCount`,
|
|
15
|
+
`playbook.confidence`) is the canonical home. `recordSuccess` and
|
|
16
|
+
`recordFailure` mutate it on every trajectory.
|
|
17
|
+
|
|
18
|
+
If you need ranked loadouts driven by live metrics, query that system
|
|
19
|
+
first, then pass the resulting skill IDs to skill-tree's loadout compile
|
|
20
|
+
via `include: [...]`. As of 0.2, `include` is a **presence guarantee** —
|
|
21
|
+
every ID listed is in the result regardless of other filters, in the
|
|
22
|
+
order specified. Combine with `maxSkills: include.length` for "exactly
|
|
23
|
+
these N skills" semantics.
|
|
24
|
+
|
|
25
|
+
skill-tree's `LoadoutCriteria` no longer supports `minSuccessRate` or
|
|
26
|
+
`priorityOrder: 'usage' | 'successRate' | 'recent'` — the only
|
|
27
|
+
recognized `priorityOrder` value is `'relevance'`, currently a no-op
|
|
28
|
+
pending semantic ranking.
|
|
29
|
+
|
|
30
|
+
See `CHANGELOG.md` for the full migration guide.
|
|
31
|
+
|
|
5
32
|
## Overview
|
|
6
33
|
|
|
7
34
|
skill-tree helps you build and maintain a library of reusable skills for AI agents by:
|
|
@@ -45,7 +72,6 @@ await bank.saveSkill({
|
|
|
45
72
|
createdAt: new Date(),
|
|
46
73
|
updatedAt: new Date(),
|
|
47
74
|
status: 'active',
|
|
48
|
-
metrics: { usageCount: 0, successRate: 0, feedbackScores: [] },
|
|
49
75
|
} as Skill);
|
|
50
76
|
|
|
51
77
|
// Search for skills
|
|
@@ -74,7 +100,6 @@ interface Skill {
|
|
|
74
100
|
instructions: string; // Free-form markdown body (the SKILL.md content)
|
|
75
101
|
tags: string[]; // Categorization
|
|
76
102
|
status: SkillStatus; // 'draft' | 'active' | 'deprecated' | 'experimental'
|
|
77
|
-
metrics: SkillMetrics; // Usage tracking
|
|
78
103
|
// ... namespace, taxonomy, lineage, serving metadata
|
|
79
104
|
}
|
|
80
105
|
```
|