maintaining-skillgraph-freshness
lifecycle111 linesSource
Use when validating authored skills, checking stale state, and keeping compiled metadata aligned with changing knowledge in an agentpack skillgraph.
Agentpack - Maintaining Skillgraph Freshness
Setup
sh
cd knowledge-base
agentpack publish validate domains/value/skills/copywriting
agentpack author stale
git add .agentpack/compiled.json
Core Patterns
Use stale before and after source changes
sh
agentpack author stale
edit domains/value/knowledge/tone-of-voice.md
agentpack author stale
Revalidate to refresh the baseline
sh
agentpack publish validate domains/value/skills/copywriting
Commit authored metadata
sh
git add .agentpack/compiled.json
git commit -m "chore: refresh skill metadata"
Common Mistakes
CRITICAL Treating stale detection as automatic without validate
Wrong:
sh
edit domains/value/knowledge/tone-of-voice.md
agentpack author stale
Correct:
sh
edit domains/value/knowledge/tone-of-voice.md
agentpack author stale
agentpack publish validate domains/value/skills/copywriting
The stale baseline only updates on successful validation.
Source: docs/cli-skills.mdx
HIGH Not committing compiled state in authoring repos
Wrong:
sh
git add domains/value/skills/copywriting
git commit -m "feat: update copywriting"
Correct:
sh
git add domains/value/skills/copywriting .agentpack/compiled.json
git commit -m "feat: update copywriting"
Uncommitted compiled metadata breaks stale visibility across clones, CI, and teammates.
Source: README.md
MEDIUM Using install-state as authored provenance
Wrong:
text
.agentpack/install.json is treated as the authored source of truth
Correct:
text
.agentpack/compiled.json is the authored metadata file
Install-state describes runtime materialization, not authored source freshness.
Source: docs/staleness.mdx