agentleFS
Sign inStart free
andrew-shwetzerandrew-shwetzer/career-ops-plugin/skills/triage/SKILL.md

triage

Skill501 starsChanged 7 months agoMITView on GitHub

Quick-score your pipeline of scan results. Ranks every role in your pipeline by fit and recommends which ones deserve a full evaluation. Use when someone says 'triage my pipeline', 'which scanned jobs should I apply to', 'rank my pipeline', or 'process my scan results'.

189 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 66 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 167 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 42 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 68 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 63 projects that use this

  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 4

    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:

    Read data/pipeline.md - the queue from scan results

    line 20
  2. Very specific:

    Read data/applications.md - exclude already-tracked roles

    line 21
  3. Distinctive:

    If pipeline is empty:

    line 23
  4. Distinctive:

    If WebFetch unavailable, score based on title + location only (partial)

    line 38
  5. Distinctive:

    Add quick score to each entry

    line 79
  6. Distinctive:

    If user says "evaluate all recommended," process each sequentially using the evaluate skill, pausing between each for user confirmation.

    line 91

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

Quick-score scan results to find the best candidates for full evaluation.

Step 0: Load Context

  1. Read data/profile.yml
  2. Read data/pipeline.md - the queue from scan results
  3. Read data/applications.md - exclude already-tracked roles

If pipeline is empty:

"Your pipeline is empty. Scan some companies first: say 'scan {company name}' or 'scan all' for your watchlist."

Step 1: Determine Scope

  • No argument / "all": Process every "New" entry in pipeline
  • Company name: Process only that company's entries
  • Number limit: "triage top 10" -> process first 10 by relevance

Step 2: Quick-Score Each Role

For each pipeline entry with status "New":

  1. Fetch the full JD if only a URL is stored (use WebFetch)
  2. If WebFetch unavailable, score based on title + location only (partial)
  3. Quick-score on 3 dimensions:
    • Title fit (0-5): How well does the title match target roles?
    • Requirements fit (0-5): If JD available, how many requirements match?
    • Logistics fit (0-5): Location, seniority, compensation range match?
  4. Average = quick score out of 5.0

This is FAST scoring. No blocks A-F. No STAR stories. Just a fit check.

Step 3: Rank & Recommend

Sort by quick score, descending.

## Pipeline Triage: {date}

Scored **{n}** roles from your pipeline.

### Recommended for Full Evaluation (score >= 3.5)

| # | Company | Role | Quick Score | Why |
|---|---|---|---|---|
| 1 | {company} | {title} | {score}/5 | {one-line reason} |
| 2 | ... | ... | ... | ... |

### Maybe (score 2.5-3.4)

| # | Company | Role | Quick Score | Why |
|---|---|---|---|---|
| ... | | | | |

### Skip (score < 2.5)

| # | Company | Role | Quick Score | Why |
|---|---|---|---|---|
| ... | | | | {why it doesn't fit} |

Step 4: Update Pipeline

Update data/pipeline.md:

  • Add quick score to each entry
  • Change status from "New" to "Triaged"

Step 5: Next Steps

"Top {n} roles are worth a full evaluation.

Want me to:

  • Evaluate the top pick? Say 'evaluate {company} {role}'
  • Evaluate all recommended? I'll work through them one by one
  • Scan more companies? Say 'scan {company}'"

If user says "evaluate all recommended," process each sequentially using the evaluate skill, pausing between each for user confirmation.

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