Add rule-review skill stub

2026-06-07 10:45:18 -05:00
parent 393e0ca635
commit 6d94136e26
1 changed files with 34 additions and 0 deletions
@@ -0,0 +1,34 @@
 # rule-review
 ## Trigger
 Use this skill when the user wants to review the `! Rule Needed` label, says "let's go
 through the rule needed folder", "what rules should we build", or periodically when that
 label has accumulated enough candidates to be worth a review session.
 ## Purpose
 Interactive interview over the contents of the `! Rule Needed` Gmail label. For each
 flagged email type, Claude designs the right long-term rule using the full toolbox —
 in cost order: Gmail filter first, then Apps Script, then Studio flow (last resort only).
 ## Toolbox Decision Tree
 1. **Gmail filter** — Can this be expressed as a from:/to:/subject:/has: query? Use this.
   Free, instant, zero ongoing cost.
 2. **Apps Script** — Does it require attachment filename inspection, body keyword + sender
   combinations, or other logic filters can't express? Use Apps Script.
 3. **Studio flow** — Only if (1) and (2) genuinely cannot do the job AND the action
   required goes beyond labeling (creating Tasks, filing to Drive, forwarding with context,
   triggering workflows). Studio is limited and expensive — flag this clearly to the user.
 ## Interview Pattern
 For each `! Rule Needed` email:
 - What made you flag this? What did you want to happen automatically?
 - Who sends it? Is the domain consistent?
 - Is there a subject pattern? An attachment type?
 - How often does this type arrive?
 - What's the right action: label only, archive, star, create task, file attachment?
 ## Outputs
 Proposed rules formatted for `import` → `deploy` flow, added to Tracker with status = proposed.
 ## Skill Stub — Implementation Pending
 Full SKILL.md to be written in build session. Load CW-020_Concept.md for scope and design intent.