triage-board
SolidGenerates a structured triage artifact from the current conversation's findings — a self-contained Desktop folder with a JSON Schema, schema-conformant report.json, prose markdown, and a single-file HTML viewer. Viewer ships with MD / CSV / JSON download buttons in the header and a per-finding "Copy as Markdown" action that produces a GitHub/Linear/Notion-ready ticket block. Stateless — triage state lives in the user's ticket system, not in the viewer. Use after a beginner-mind audit, QA exploration, code review, or any session where the user accumulated discrete findings worth handing off. Triggers: "generate test report", "create triage doc", "extract findings", "export this audit", "make a viewer", "save findings for review".
Install
Quality Score: 83/100
Skill Content
Details
- Author
- mostafa-drz
- Repository
- mostafa-drz/claude-skills
- Created
- 7 months ago
- Last Updated
- yesterday
- Language
- HTML
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
triage-findings
This skill should be used when the user explicitly asks to "triage findings" through an interactive browser-based workflow. Only invoke when explicitly requested.
board-triage
This skill should be used when the user asks to "run board triage", "triage the backlog", "prioritize the issues", "rank the unranked issues", "fill in Impact/Effort/Priority", "do the weekly triage", or wants the untriaged items on a task board classified so the prioritization/now/roadmap views become useful. It runs the export -> analyze -> apply loop: pull a snapshot, find the un-ranked/blank/stale items, rank them by the Impact x Effort rubric, and apply only the diffs. The judgment is backend-agnostic; a thin adapter does the board's I/O (kata and GitHub Projects v2 adapters ship; any board with items and fields can have one).
triage-tickets
Sweep a GitHub repo's unlabeled, needs-triage, and stale needs-info issues through the mattpocock /triage state machine on an independent daily schedule, applying only mechanically safe outcomes and recommending the rest. Never launches implementation and never grills; that stays orchestrate-tickets's and a human's job respectively.