fix(plugins): sync all 171 plugin SKILL.md files with fixed skills/ versions

Propagates Anti-Patterns sections, description rewrites, Required Inputs additions, and Quality Checks format fixes from skills/ to matching plugin SKILL.md copies. https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
2026-06-08 13:06:21 +00:00
parent fb85a1cb55
commit affae033fe
171 changed files with 1428 additions and 56 deletions
@@ -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]"
@@ -70,6 +70,22 @@ Produces a structured financial due diligence framework — document request lis
 - Balance sheet risk: [Assessment]
 - Overall: Green Strong / Amber Acceptable / Red Material concerns

+## Quality Checks
+
+- [ ] Document request list is tailored to the transaction type and stage — not a generic template
+- [ ] Red flags checklist covers revenue quality, margins, cash conversion, and balance sheet risk
+- [ ] Every analytical question connects to a specific risk the transaction presents
+- [ ] Summary output template is completed with an overall RAG assessment
+- [ ] Disclaimer that this is a framework and does not substitute for qualified financial or legal advice
+
+## Anti-Patterns
+
+- [ ] Do not present the checklist without tailoring it to the specific transaction type and stage of diligence
+- [ ] Do not overlook revenue concentration risk — customer concentration above 20–30% is a material risk that must be flagged
+- [ ] Do not confuse EBITDA with cash — always check cash conversion and identify non-cash items
+- [ ] Do not skip the related-party transaction review — undisclosed related-party dealings are a common due diligence failure point
+- [ ] Do not produce output without noting this is a framework and qualified financial and legal advice is required
+
 ## Example Trigger Phrases
 - "Give me a financial due diligence checklist for [company type]"
 - "What documents should I request for financial DD?"
@@ -63,6 +63,14 @@ For each significant variance:
 - [ ] Audience-appropriate language (board vs investor vs management)
 - [ ] One-off items clearly distinguished from recurring items

+## Anti-Patterns
+
+- [ ] Do not list numbers without explaining what is driving them — narrative must go beyond restating the figures
+- [ ] Do not mix one-off items with recurring performance without clearly distinguishing them
+- [ ] Do not write the same level of detail for all line items — focus depth on the items that matter most
+- [ ] Do not omit forward-looking commentary — a narrative without outlook is incomplete for board or investor audiences
+- [ ] Do not use technical accounting language without translation — the audience is executives, not accountants
+
 ## Example Trigger Phrases
 - "Write a financial narrative for these results: [paste numbers]"
 - "Turn this P&L into a board narrative"
@@ -51,6 +51,14 @@ For each slide:
 - [ ] Ask slide specifies use of funds and 18-month milestones
 - [ ] TAM is bottoms-up where possible

+## Anti-Patterns
+
+- [ ] Do not include a "no real competitors" slide — every company has competition and investors will discount founders who claim otherwise
+- [ ] Do not use a top-down TAM calculation without a bottoms-up validation — investors distrust pure top-down market sizing
+- [ ] Do not leave the ask vague — specify the amount, use of funds, and 18-month milestones the funding enables
+- [ ] Do not let traction slides show vanity metrics — focus on revenue, retention, and growth rate over downloads and signups
+- [ ] Do not bury the problem slide — investors must understand and feel the pain before they care about the solution
+
 ## Example Trigger Phrases
 - "Build a pitch deck structure for [company]"
 - "Help me structure my Series A deck"
@@ -120,6 +120,14 @@ Based on the above, prioritise these before year-end:
 - [ ] Disclaimer is prominent — this is a framework, not tax advice
 - [ ] Threshold figures are flagged as requiring verification for current tax year

+## Anti-Patterns
+
+- [ ] Do not provide specific tax advice — always recommend qualified tax advice and note this prominently
+- [ ] Do not present threshold figures as definitive without noting they require verification for the current tax year
+- [ ] Do not produce a generic checklist without tailoring it to the entity type (individual, sole trader, limited company)
+- [ ] Do not omit timing-critical items — some reliefs require action before year-end and deadlines must be called out
+- [ ] Do not conflate UK and non-UK tax rules — clarify jurisdiction before generating any checklist
+
 ## Example Trigger Phrases

 - "Give me a tax planning checklist for [year-end / my situation]"