agentleFS
cyb3rcricketcyb3rcricket/cricket-mode/.agents/skills/drift/SKILL.md

drift

Skill0 starsChanged 50 days agoMITView on GitHub

Use when the project may disagree with itself — code vs tests, docs or comments vs behavior, config vs runtime, examples vs interfaces, or setup vs real requirements — and you need the concrete mismatch, not a stale-file list.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look for contradictions between:

    line 10
  2. Distinctive:

    Do not just list stale files.

    line 20
  3. Distinctive:

    Use the actual project files as evidence.

    line 31
  4. Distinctive:

    Do not change anything unless I ask.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

Drift

Find where this project has drifted out of sync with itself.

Look for contradictions between:

  • code and tests,
  • implementation and documentation,
  • comments and actual behavior,
  • configuration and runtime behavior,
  • examples and current interfaces,
  • schemas and handlers,
  • setup instructions and real requirements.

Do not just list stale files.

Find concrete disagreements that could confuse a developer, break a workflow, or make the project behave differently than its documentation suggests.

For each finding, show:

  • what says one thing,
  • what says something different,
  • which behavior appears current based on the available evidence, or say when it is unclear,
  • and what likely needs attention.

Use the actual project files as evidence.

Do not change anything unless I ask.

Core Rule

Find where the project disagrees with itself.

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.