agentleFS
evergonlabsevergonlabs/aiframework/.claude/skills/sheal-drift/SKILL.md

sheal-drift

Skill0 starsChanged 7 months agoMITView on GitHub

Detect learning drift — learnings that aren't being applied. Suggests promotions to CLAUDE.md invariants or .claude/rules/.

  • Installs packages

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check if it appears in CLAUDE.md invariants already

    line 38
  2. Very specific:

    Check if a .claude/rules/ file covers it

    line 39
  3. Distinctive:

    Check frequency of drift (how often the same learning is violated)

    line 40
  4. Distinctive:

    Ask: "Found N learnings with persistent drift.

    line 51
  5. Distinctive:

    Add to CLAUDE.md Invariants section via Edit tool

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/sheal-drift — Drift Detection

Prerequisites

command -v sheal >/dev/null 2>&1 && sheal --version 2>/dev/null || echo "sheal not installed — run: npm install -g @liwala/sheal"

Step 0: Telemetry (silent, non-blocking)

aiframework-telemetry skill_invoked skill=sheal-drift 2>/dev/null || true

Step 1: Check Drift

sheal drift --last 10 --format json --project . 2>/dev/null || echo '{"error": "sheal drift failed"}'

Step 2: Analyze Patterns

For each drifted learning:

  1. Check if it appears in CLAUDE.md invariants already
  2. Check if a .claude/rules/ file covers it
  3. Check frequency of drift (how often the same learning is violated)

Step 3: Promotion Recommendations

Apply these rules:

  • Drift on same learning 3+ times → promote to CLAUDE.md invariant
  • Drift in specific file area → create .claude/rules/<domain>.md
  • No drift, healthy learning → keep as-is in sheal

Step 4: Apply Promotions (with approval)

Ask: "Found N learnings with persistent drift. Promote to permanent rules?"

For each approved promotion:

  • Add to CLAUDE.md Invariants section via Edit tool
  • Or create new .claude/rules/ file
  • Mark the sheal learning as promoted

Step 5: Report

LearningDrift CountAction
...NPromoted/Keep/Dismissed

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.