skill staleness check

Other Community

Skill notes

Inputs

Webhook payload from an upstream package repo merge to main:

Step 1 — Match changed files to skills

Read all SKILL.md files under packages/intent/skills/. For each skill, extract sources from the frontmatter. Match changed_files from the webhook against sources entries across all skills. Source references use the format Owner/repo:relative-path and support glob patterns.

Using sync-skills.mjs

The repo includes scripts/sync-skills.mjs for programmatic staleness detection. For a given library: This checks: Source file SHA drift (compares stored SHAs in sync-state.json against current remote SHAs via GitHub API)

Step 2 — Evaluate each candidate

For each matched skill: Read the current SKILL.md content Fetch the file diff from the triggering commit in the source repo Classify the change: Classification · Criteria · Action

Two-pass classification

Pass 1 — Quick scan: Read the diff summary (files changed, insertions, deletions). Identify which skill sections could be affected. Pass 2 — Detail evaluation: For each potentially affected section, read the full diff hunks and compare against the skill content. Determine if the change actually affects what the skill documents.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@TanStack · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Match changed files to skills

Read all SKILL.md files under `packages/intent/skills/`. For each skill, extract `sources` from the frontmatter. Match `changed_files` from the webhook against `sources` entries across all skills. Source references use the format `Owner/repo:relative-path` and support glob patterns.

02
Step 2 — Evaluate each candidate

For each matched skill: Read the current SKILL.md content Fetch the file diff from the triggering commit in the source repo Classify the change: Classification · Criteria · Action

03
Step 3 — Update stale skills

For skills classified as needing content updates: Load the skill-generate meta skill Provide it with: The existing SKILL.md content The source diff

04
Step 4 — Check cross-skill references

After updating skills in Step 3, check for cross-skill staleness: For each skill that was updated, read its `name` Scan all other skills for `requires` entries or `sources` that reference the updated skill For each skill that references an updated skill, evaluate whether the

05
Step 5 — Mark skills as synced

After updating, mark the affected skills as synced so future staleness checks have a clean baseline: This updates `sync-state.json` with current source file SHAs, the tree-generator SHA, and the sync timestamp.

06
Step 6 — Open PRs

For each skill (or group of skills) that was updated: Create branch: `skill-update/<skill-name>-<short-sha>` Commit updated SKILL.md file(s) Open PR with structured body

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.