agentleFS
vale-clivale-cli/agent-tools/skills/triage/SKILL.md

triage

Skill8 starsChanged 3 months agoMITView on GitHub

Turn a large first Vale run into a decision per rule — fix, downgrade, or switch off. Use when the user says "too many alerts", "where do we start", "vale is too noisy", or has just added Vale to an existing corpus.

190 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing-beats, setup-matt-pocock-skills and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 74 projects that use this

  • GoogleSkill

    setup-matt-pocock-skills

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

    Also in 182 projects that use this

  • SethGammonSkill

    ascii-diagram

    Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

    Also in 4 projects that use this

  • simo97Skill

    migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    Also in 74 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 70 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 47 projects that use this

  • +1 more from Lesani
  • Other versions190 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 190

    1. mattpocock/skills★ 325ksame name
    2. withastro/astro★ 64ksame name
    3. vectorize-io/hindsight★ 61ksame name
    4. ogulcancelik/herdr★ 47ksame name
    5. herdrdev/herdr★ 47ksame name
    6. colinhacks/zod★ 44ksame name
    7. The-Vibe-Company/quivr★ 40ksame name
    8. QuivrHQ/quivr★ 40ksame name
    9. vercel-labs/skills★ 39ksame name
    10. vercel-labs/add-skill★ 39ksame name

    180 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 2

    Distinctive

    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:

    4. Say what currently blocks: Only error exits non-zero, so a pipeline can adopt Vale immediately with everything else advisory.

    line 40
  2. Very specific:

    Do not propose raising MinAlertLevel as the fix.

    line 60
  3. Distinctive:

    Do not disable a rule because it is noisy on legacy content that new content would pass.

    line 62
  4. Distinctive:

    Do not recommend a bucket without saying what it costs.

    line 64

“Common” is measured: kept by at least 6 in 10 of the 179 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

Triage a first Vale run

When to use this

Vale runs, the count is in the thousands, and the question is where to start. The output of this skill is a short ordered plan, not a fixed file.

Prerequisites

  1. vale ls-config resolves.
  2. You know which path represents the real corpus, not a subset.

Workflow

1. Count by rule, not by file.

vale --output=JSON <path> > /tmp/vale.json
jq -r 'to_entries | map(.value[]) | group_by(.Check) | map({check: .[0].Check, n: length, severity: .[0].Severity}) | sort_by(-.n) | .[] | "\(.n)\t\(.severity)\t\(.check)"' /tmp/vale.json | head -20

2. Report the shape before proposing anything: total, the split by severity, and the ten rules responsible for the most. A team that hears "18,000 alerts" reaches for MinAlertLevel; a team that hears "four rules are 80% of this" makes a decision.

3. Sort each of the top rules into one bucket, and say which and why:

bucketwhenwhat to write
Fixfew hits, rule is rightdo it now, or hand to fix
Downgraderule is right, backlog is realset it to suggestion so it guides new writing
Disablerule does not match how this project writesname it in the config with a comment saying why

4. Say what currently blocks. Only error exits non-zero, so a pipeline can adopt Vale immediately with everything else advisory. That is usually the right first move and worth stating outright.

5. Report.

Vale triage
===========
Total: 18,412   errors 3 · warnings 1,204 · suggestions 17,205
Blocking today: 3 alerts across 2 rules

Top rules
  9,881  suggestion  Microsoft.Wordiness      → downgrade (real backlog, right rule)
  3,442  suggestion  Microsoft.Contractions   → disable (house style differs)
  1,204  warning     Microsoft.Headings       → fix (mechanical, 40 files)

Do not

  • Do not propose raising MinAlertLevel as the fix. It hides alerts without deciding anything, and the decisions are the point.
  • Do not disable a rule because it is noisy on legacy content that new content would pass. Downgrade it.
  • Do not recommend a bucket without saying what it costs.

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.