Supafax inbox triage

Skill riteshkew/yc-skills/skills/supafax-inbox-triage

Catalog of all 198 YC Winter 2026 companies + 18 working Claude Code Skills inspired by the ones an open-source tool can replicate. Inspired by, not affiliated with.

Install

npx -y skills add riteshkew/yc-skills --skill supafax-inbox-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Apply an ordered set of triage rules to an inbox fixture and categorize each email into an action — reply, archive, unsubscribe, calendar, or review — with the matching rule's reason. Use this skill whenever you need to batch-process a raw inbox and produce an actionable triage report without touching an email provider.

SKILL.md

3.0 KB, 616 tokens by cl100k_base, as published. Nobody here has run it

Workflow

When this skill triggers, follow these steps in order.

Step 1 — Locate the rules file

Check whether the user has specified a rules JSON path.

If a path is provided, confirm the file exists and is readable.
If no path is provided, ask: "Please provide the path to your rules JSON file. Each rule must have a match object (with optional from, subjectContains, bodyContains, hasUnsubscribe fields), an action (reply | archive | unsubscribe | calendar | review), and a reason string. See examples/rules.json for a working example."
If the user has no rules, offer to generate starter rules based on their described inbox patterns before proceeding.

Step 2 — Locate the inbox file

Check whether the user has specified an inbox JSON path.

If a path is provided, confirm the file exists and contains at least one email object with id, from, subject, and body fields.
If no path is provided, ask: "Please provide the path to your inbox JSON file. Each email must have id, from, subject, and body fields, plus an optional hasUnsubscribe boolean. See resources/inbox.json for a working example."

Step 3 — Run the triage engine

Execute the triage engine from the skill root:

node scripts/triage.mjs <rulesFile> <inboxFile>

The engine outputs a Markdown report to stdout with:

A per-email table: id | from | subject | action | reason
A summary count per action

Capture stdout. If the process exits non-zero, surface the stderr message to the user and stop.

Step 4 — Report the triage results

Present the output table and summary to the user. For each action bucket, comment on what it means:

reply — these emails need a response; act on them today.
archive — low-value mail filed away; no action needed.
unsubscribe — subscriptions to remove to reduce future noise.
calendar — meeting invites or events that need to be scheduled or confirmed.
review — nothing matched; these need human judgment before acting.

Highlight any review emails first — they are the highest-priority items because no rule has claimed them.

Output format

## Triage Results

| ID | From | Subject | Action | Reason |
|----|------|---------|--------|--------|
...

## Summary
| Action | Count |
|--------|-------|
...

Example

See examples/input.md for a worked inbox scenario and examples/output.md for the full triage report produced by the engine.

Run the example yourself from the skill root:

cd skills/supafax-inbox-triage
bash examples/run.sh

What ships with it: 8 files

24.3 KB alongside SKILL.md, 2 of them executable

Gives 0 of the 12 instructions most debug triage skills give in 616 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

Investigate root cause before proposing any fixin 102 of 839, across 67 files
Read error messages completelyin 89 of 839, across 49 files
Create a failing test case before fixingin 84 of 839, across 46 files
Reproduce the issue consistentlyin 82 of 839, across 41 files
Change one variable at a timein 82 of 839, across 42 files
Check recent changesin 74 of 839, across 36 files
Write the regression test before fixingin 74 of 839, across 40 files
Fix the root cause not the symptomin 60 of 839, across 45 files
Implement a single fix at a timein 59 of 839, across 20 files
Trace data flow backward to the sourcein 50 of 839, across 20 files
Remove all debug instrumentationin 49 of 839, across 13 files
Form a single hypothesisin 48 of 839, across 18 files

Said here and by no other author read

Follow the workflow steps in order
Check whether the user specified a rules file path
Confirm provided rules file exists and is readable
Ask for a rules JSON file if none is provided
Offer to generate starter rules if user lacks rules
Check whether the user specified an inbox file path

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.