agentleFS
Sign inStart free
YosoyepaYosoyepa/write-check-trust/skills/wct-gate/SKILL.md

wct-gate

Skill0 starsChanged 3 months agoMITView on GitHub

Run and interpret WCT quality tiers. Use for pre-handoff checks, failing CI, selecting fast versus commit versus full verification, or fixing a named G-* gate without weakening policy.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run uv run wct gate --tier fast while editing, --tier commit before handoff, and --tier full before release.

    line 8
  2. Very specific:

    Treat FAIL and ERROR as blocking.

    line 9

≈ “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

Run WCT gates

  1. Run uv run wct gate --tier fast while editing, --tier commit before handoff, and --tier full before release.
  2. Treat FAIL and ERROR as blocking. Treat SKIP as visible missing coverage, never as proof.
  3. Fix production code or tests. Do not edit thresholds, baselines, generated rules, or integrity locks to obtain green.
  4. Rerun the smallest failing command, then rerun the original tier.
  5. Report every skipped gate and the reason.

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.

Check your setup, free