agentleFS
Sign inStart free
AgiFlowAgiFlow/ai-plugin/skills/triage/SKILL.md

triage

Skill4 starsChanged 33 days agoMITView on GitHub

Diagnose stalled, blocked, overloaded, or unhealthy Agiflow projects and recommend specific corrective actions. Use for project health checks, blocked work, conflicting priorities, obsolete tasks, overloaded assignees, or an unmanageable backlog.

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

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

  • 0

    Common

    Most of the 176 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Call get_current_scope and resolve the target project when one is specified.

    line 12
  2. Very specific:

    Call list_active_tasks_by_org, list_work_units, and list_members.

    line 13
  3. Distinctive:

    Do not change anything during diagnosis.

    line 31
  4. Very specific:

    Document the reason with create_task_comment before cancelling or materially re-scoping a task.

    line 32
  5. Very specific:

    Use update_task only after approval for reassignment, priority, status, or scope changes.

    line 33
  6. Distinctive:

    Create new tasks only when the user approves the proposed corrective work.

    line 34
  7. Distinctive:

    Do not use deletion as a default cleanup action.

    line 35

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

Agiflow Triage

Diagnose before prescribing. Read the workspace first and separate evidence from inference.

Workflow

  1. Call get_current_scope and resolve the target project when one is specified.
  2. Call list_active_tasks_by_org, list_work_units, and list_members.
  3. For relevant items, call get_task, get_work_unit, get_work_unit_progress, and list_task_comments to inspect details and documented blockers.
  4. Identify:
    • Stalled tasks or work units
    • Explicit blockers and unresolved dependencies
    • Missing or vague acceptance criteria
    • High-priority unassigned work
    • Excessive work in progress
    • Obsolete or duplicate tasks
    • Priority inversions
  5. Classify each finding as Blocker, Warning, or Note.
  6. Recommend one specific action for each finding and explain the expected impact.
  7. Present the report and ask which actions the user approves.
  8. Execute only approved actions with the appropriate tools, such as update_task, create_task, batch_create_tasks, or create_task_comment.
  9. Re-read affected records to verify the result.

Mutation Rules

  • Do not change anything during diagnosis.
  • Document the reason with create_task_comment before cancelling or materially re-scoping a task.
  • Use update_task only after approval for reassignment, priority, status, or scope changes.
  • Create new tasks only when the user approves the proposed corrective work.
  • Do not use deletion as a default cleanup action.

Response

Provide a concise health summary, evidence for each finding, severity, recommended action, and the three highest-priority next steps.

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