fix(skills): add Anti-Patterns sections, fix descriptions, quality checks, and required inputs

- Add Anti-Patterns section (3-5 binary checkboxes) to all modified skills
- Fix Quality Checks to use binary checkbox format where needed
- Rewrite descriptions to verb-when-produces format where needed
- Add Required Inputs sections to skills missing them
- Fix email-triage frontmatter YAML quoting

https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
This commit is contained in:
Mohit
2026-06-08 10:20:50 +00:00
parent 44f69a541f
commit 4ff88bdbb1
88 changed files with 740 additions and 33 deletions
+11 -4
View File
@@ -48,10 +48,17 @@ Does the full-year forecast need updating? State revised expectation and key ass
3-4 sentences of management commentary suitable for a board pack.
## Quality Checks
- All variances above threshold explained
- Root causes specific (not vague)
- Favourable/Adverse correctly labelled
- Forecast impact stated for material variances
- [ ] All variances above threshold explained
- [ ] Root causes specific (not vague)
- [ ] Favourable/Adverse correctly labelled
- [ ] Forecast impact stated for material variances
## Anti-Patterns
- [ ] Do not explain a variance as "timing" without specifying which period it will reverse into and what amount is expected
- [ ] Do not label a favourable variance on a cost line without checking whether it is due to underspend, delayed spend, or reduced activity — the cause determines whether it is genuinely good news
- [ ] Do not omit variances below the materiality threshold entirely — note them collectively so the reader knows they exist and were reviewed
- [ ] Do not present a variance analysis without a forecast impact statement for material items — historical variances without forward implications are incomplete
## Example Trigger Phrases
- "Write a variance analysis for these actuals vs budget: [paste]"