CommunityCoding & Developmentgithub.com

Zhr65/SkillFresh

Skill capability depreciation table. Used when users ask 'Are my installed skills/plugins outdated?', 'Which capabilities degraded after a model swap?', 'What should I delete or add?', 'Is this skill actually useful?' Cross-host (DSH plugin / WorkBuddy, Claude Code, Codex skill), based on capability fingerprinting + golden set regression, not gut feelings.

What is SkillFresh?

This skill, named SkillFresh or skill-auditor, provides a systematic and objective way to measure how skill and plugin capabilities degrade when models are upgraded or swapped. Instead of relying on subjective feelings, it uses a 'capability fingerprint' and golden set regression testing to quantify performance changes. It supports multiple hosts such as DSH plugins, WorkBuddy, Claude Code, and Codex, offering both tool-based and CLI interfaces. The skill answers critical questions like whether capabilities have actually regressed, whether new skills provide net value, and whether a skill aligns with the user's style and needs. It enforces hard constraints such as requiring K≥3 baselines for degradation conclusions, distinguishing synthetic from real user samples, and never silently deleting or installing skills. Actionable outputs include a five-tier recommendation system (strong, watch, unverified, degraded, prune-candidate) with explicit rules for each tier, ensuring developers and AI agent users make data-driven decisions about their tool ecosystem.

Works with✓Claude Code✓Codex CLI~Cursor
npx skills add https://github.com/Zhr65/SkillFresh/tree/HEAD/npm/skill

Installed? Explore more Coding & Development skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Capability Depreciation Table (skill-auditor)

When the model is upgraded, installed skills / plugins won't throw errors, they will only quietly degrade. This skill turns "degradation" into measurable numbers.

Three Judgments, Each with Evidence

User's QuestionHow to DetermineKey Prerequisite
Have capabilities degraded?Re-run the same golden set on the new model; pass rate drop ≥20pp with consistent directionFingerprint unchanged. Fingerprint changed means it was 'modified', not degraded
Is the new skill/plugin useful?Ablation study (with it / without it) + adoption rate, calculate net benefitNo control group means only "feels good"
Does it fit me?Trigger precision (triggers when it should, doesn't trigger when it shouldn't) + environment reconciliation + style baselineUse real historical prompts, not imagined ones

How to Invoke

When the plugin has registered tools, use the tools directly (this is the preferred method):

  • skill_audit_status — Depreciation table: fingerprint / baseline pass rate / risk / judgment
  • skill_audit_recommend — Strong / Watch / Unverified / Degraded / Prune-candidate, five tiers
  • skill_audit_check — Whether the current model has changed relative to the last regression baseline
  • skill_audit_scan — Re-discover assets after installing new items
  • skill_audit_suggest — What to add when the user's need is not covered by any asset

Without a tool surface (e.g., hosts that only have skills installed), use the CLI:

python <data-dir>/scripts/console.py --host deepseek status
python <data-dir>/scripts/console.py --host deepseek recommend
python <data-dir>/scripts/console.py --host workbuddy status --root ~/.workbuddy-ai/skills

<data-dir> defaults to ~/.dsh/skill-auditor (can be overridden with SKILL_AUDITOR_HOME). The engine is pure standard library Python 3.8+, with no third-party dependencies.

When the User Has No Available Skills / Plugins

This is the skill's proactive mechanism, do not wait for the user to ask:

  1. First check the installed registry — if there is coverage, do not suggest a new one (avoid duplicate installations);
  2. Truly none available → skill_audit_suggest --need "<one-sentence need>";
  3. Output "suggested addition + search term", installation is confirmed by the user, no automatic installation.

Hard Constraints (Must State Honestly, Do Not Package as Conclusions)

  • A baseline with K=1 is self-assessment, not a statistical conclusion. To render a 'degradation' verdict, K≥3 is required.
  • The golden set may contain synthetic samples (when the user's history is insufficient). Synthetic samples can test 'is the structure correct', but cannot test 'does it resemble you'. Such samples are marked with "synthetic": true in the file.
  • risk is an indicator of the maintenance surface (lines of code + tool dependencies), it does not represent value. High risk does not mean it should be deleted.
  • Removal and installation must be confirmed; removal prioritizes 'disable / archive', no silent deletion.
  • Degradation attribution has only four categories, do not expand: Tool call error → fix tool description; Output structure correct but content wrong → rewrite instructions; Should have triggered but didn't → modify trigger description; All intermediate steps correct but final state wrong → only then might be a model capability regression.

Post-Judgment Actions

JudgmentAction
strongKeep, can be pinned as recommended
watchKeep, prioritize re-running on next model change
unverifiedFirst build a golden set (3–5 real prompts) then judge, do not deprecate for now
degradedFirst attribute, then decide to rewrite or disable; do not delete directly
prune-candidateNo baseline + very high maintenance surface → suggest evaluation, do not auto-delete

Individual skills in this repo

This repo contains 1 individual skill — each has its own dedicated page.

Related Skills