Triage
Cross-customer dashboard. Scan every customers/<name>/ directory, surface the highest-urgency blockers and unresolved unknowns across the FDE's portfolio. Optional filter to one cohort. No session marker required — this skill is the "where do I look first today?" view. Proactively invoke this skill at the start of a session in an FDE ops repo when no specific customer has been named, OR when the FDE asks "where should I look first", "what's most urgent", "what's on my plate today", or any variant of "what should I be working on?". Usage: /triage [active|blocked|all] Voice triggers: "what's urg
Install
npx skills add Dan-Cleary/fdestack --skill triagegit clone --depth 1 https://github.com/Dan-Cleary/fdestack.git /tmp/fdestack
mkdir -p ~/.claude/skills
cp -r /tmp/fdestack/skills/triage ~/.claude/skills/triagePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# /triage Multi-customer portfolio view. Answer: where should the FDE spend the next hour? ## Step 0: Parse cohort filter Optional first argument: `active | blocked | all`. Default: `active`. - **active** — customers with at least one commit to their dir in the last 14 days - **blocked** — customers with at least one HIGH blocker or HIGH unknown - **all** — every customer dir, regardless of recency Set `COHORT` from the argument or default to `active`. ## Step 1: NO session marker check Unlike `/discovery` / `/scope` / `/poc` / `/integrate` / `/value-frame`, /triage runs without requiring `/customer-context` first. It's the *meta* view — the FDE is deciding which customer to load context for. Requiring a per-customer marker here is backwards. ## Step 2: List customers ```bash CUSTOMERS=$(ls -d customers/*/ 2>/dev/null | xargs -n1 basename 2>/dev/null) COUNT=$(echo "$CUSTOMERS" | grep -c . || echo 0) echo "FOUND_CUSTOMERS=$COUNT" ``` If `FOUND_CUSTOMERS=0`: "No customers/ subdirectories. Run /customer-context <name> for your first customer." Stop. ## Step 3: Context-window guard If `FOUND_CUSTOMERS > 10` AND `COHORT=all`: > You have $COUNT customers. Loading profile.md + blockers.md + unknowns.md > for all of them may exhaust the context window. Filter to a smaller cohort? > Options: active (last 14d) / blocked (HIGH items only) / all (proceed anyway). Wait for FDE response. Default to `active` if they don't pick. ## Step 4: Apply cohort filter For `active`:
Details
- Skill name
triage- Repository
- Dan-Cleary/fdestack
- Path
skills/triage/SKILL.md- License
- MIT
- Repo updated
- 19 May 2026
FAQ
What does the Triage skill do?
Cross-customer dashboard. Scan every customers/<name>/ directory, surface the highest-urgency blockers and unresolved unknowns across the FDE's portfolio. Optional filter to one cohort. No session marker required — this skill is the "where do I look first today?" view. Proactively invoke this skill at the start of a session in an FDE ops repo when no specific customer has been named, OR when the FDE asks "where should I look first", "what's most urgent", "what's on my plate today", or any variant of "what should I be working on?". Usage: /triage [active|blocked|all] Voice triggers: "what's urg
How do I install the Triage skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dan-Cleary/fdestack --skill triage. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Triage popular?
It lives in Dan-Cleary/fdestack, which has 49 GitHub stars and 5 forks.
Related skills
Customer Context
49Dan-Cleary/fdestack
Load a customer's context at the start of every session. Run this before any other FDEstack skill. Reads all 7 context files, surfaces drift since last session, asks what's new, and commits updates. Proactively invoke this skill (do NOT answer customer-specific questions directly) when the user references a customer name in an FDE ops repo without context being loaded this session. Always the first skill in a customer session — every other FDEstack skill requires its session marker. Usage: /customer-context <customer-name> Voice triggers: "load <customer>", "start session with <customer>", "wh
Discovery
49Dan-Cleary/fdestack
Process any inbound source of customer context — meeting transcript, prior FDE's handoff notes, AE/sales briefing, customer-side RFP response, prior Discovery Workshop output, or your own raw notes. Extracts new stack info, stakeholders, stated problem, real problem, open questions, and context conflicts. Updates customer context files and commits. Proactively invoke this skill (do NOT just summarize) when the user pastes call notes, meeting transcripts, AE briefings, RFP responses, handoff docs, or any inbound document about a customer. Triggers on phrases like "I just had a meeting", "here a
Engagement Retro
49Dan-Cleary/fdestack
Weekly retrospective for a single customer engagement. Reads commit history, recent discovery/scope/value-frame/poc/integrate files, and current blockers/unknowns. Produces a structured retro: what shipped, what's stuck, what we learned, what's next. Optional cross-customer learnings write-back for patterns worth remembering. Distinct from gstack's /retro (which is engineering-retro per-codebase). Proactively invoke this skill on Fridays or end-of-week, or when the FDE asks "where did the week go", "weekly retro", "what shipped this week", or seems to be wrapping up an engagement phase. Always
Value Frame
49Dan-Cleary/fdestack
Translate a scoped process inefficiency into a defensible dollar value with stated assumptions and sensitivity. Forces lever taxonomy, explicit unit economics, and a defensibility check. Vague items get pushed to unknowns.md HIGH so they surface in every future Session Brief until resolved. Proactively invoke this skill after /scope when the FDE asks "is this worth doing", mentions ROI, asks about business case, needs to prepare for an executive conversation about value, or wants to put a dollar number on the work. Especially relevant before executive readouts or renewal calls. Usage: /value-f
Scope
49Dan-Cleary/fdestack
Force the wedge question: smallest thing buildable this week that proves the core value. Require binary success criteria. Push vague answers to unknowns.md as HIGH so they surface in every future Session Brief. Proactively invoke this skill after /discovery when the FDE describes a problem they want to solve for the customer, references the wedge or first thing to build, or asks "what should we build first" / "what's the smallest thing". Always run before /poc or /value-frame. Usage: /scope <customer-name> <problem statement> Voice triggers: "scope this out", "what's the wedge", "smallest thin
SEO Optimization
47mujez/claude-skills
SEO and content optimization specialist. Use when optimizing web pages, blog posts, landing pages for search engines, implementing structured data, meta tags, Open Graph, technical SEO, Core Web Vitals, or AI search engine optimization (AEO). Covers both traditional SEO and AI-powered search discoverability.
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.