agentleFS
Sign inStart free
PrefectHQPrefectHQ/fastmcp/.agents/skills/triage/SKILL.md

triage

Skill28k starsChanged 27 days agoApache-2.0View on GitHub

Find worthwhile FastMCP issues to work on in a backlog or release window, verify promising candidates, and present concrete picks with existing PR links.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 6

    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:

    Read AGENTS.md and the contribution policy in the development guide.

    line 8
  2. Distinctive:

    Start from an inventory, then link each candidate to the PRs that mention it:

    line 10
  3. Distinctive:

    Read the report, comments, maintainer decisions, and prior bot investigation.

    line 24
  4. Distinctive:

    Search related issues and PRs in all states, including gate-closed contributions.

    line 25
  5. Distinctive:

    Verify the claimed contract and enough evidence to explain the cause.

    line 27
  6. Distinctive:

    When the user chooses implementation, use fix-issue.

    line 31

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

Find worthwhile work

Read AGENTS.md and the contribution policy in the development guide. Honor the requested scope. For "since the last patch," identify the release timestamp, then look for open issues created or substantively updated afterward. Use a bounded inventory internally; report truncation if it affects coverage.

Start from an inventory, then link each candidate to the PRs that mention it:

gh release list --repo PrefectHQ/fastmcp --limit 1
gh issue list --repo PrefectHQ/fastmcp --state open --limit 30 \
  --json number,title,author,createdAt,updatedAt,labels,comments
gh pr list --repo PrefectHQ/fastmcp --state all --search "<issue-number> in:body" \
  --json number,title,state,author

Pick work with concrete user impact, a supported contract being violated, and a tractable causal fix. Do not rank solely by recency, comment count, or how small a proposed patch looks. Automated dashboard churn is not itself useful work.

For promising candidates:

  • Read the report, comments, maintainer decisions, and prior bot investigation.
  • Search related issues and PRs in all states, including gate-closed contributions. Closure alone says nothing about a fix's merit.
  • Trace the relevant code and git history. Distinguish fixed on main, released on the affected line, and merely proposed.
  • Verify the claimed contract and enough evidence to explain the cause. A proposed solution is a lead, not a diagnosis. Consider compatibility before calling a fix straightforward.

Lead with the strongest pick as soon as evidence supports it: link, what breaks, why it matters, where the cause is, and the next action. Include a few alternatives when useful. Do not turn selection into an exhaustive audit or a full review of every linked PR. Save continuation notes only when needed.

When the user chooses implementation, use fix-issue. For an assignment decision on an external contribution, use review-issue. Triage alone does not authorize public mutations or implementation.

Download now (ZIP)

Trending

Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 1 new projectWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Who's talking about PrefectHQ/fastmcp

The biggest 5 of 76 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 76

Talked about on GitHub, YouTube, the web, Hacker News and Bluesky (76 times).

On GitHub · 50

45 more on GitHub

On YouTube · 21

16 more on YouTube

On the web · 3

On Hacker News · 1

On Bluesky · 1

  • Other versions191 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. jlowin/fastmcp★ 28k71% same

    Wrote their own version · 190

    1. mattpocock/skills★ 303ksame name
    2. withastro/astro★ 63ksame name
    3. vectorize-io/hindsight★ 54ksame name
    4. herdrdev/herdr★ 46ksame name
    5. ogulcancelik/herdr★ 44ksame name
    6. colinhacks/zod★ 44ksame name
    7. QuivrHQ/quivr★ 40ksame name
    8. pnpm/pnpm★ 37ksame name
    9. vercel-labs/skills★ 36ksame name
    10. vercel-labs/add-skill★ 35ksame 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.

  • Used alongsideProjects with it also use setup-matt-pocock-skills, writing-beats 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.
    • 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 148 projects that use this

    • 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 58 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 33 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 59 projects that use this

    • FabienDehopreSkill

      decision-mapping

      Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

      Also in 7 projects that use this

  • In this repository12 other files it gives its agents.

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