feat: 100 skills milestone — 7 new skills + quality improvements across all 93

New skills added:
- teaching-lesson-plan: structured lesson plans for any subject/audience/setting
- seo-content-brief: complete SEO briefs with intent, competitor gaps, and outline
- media-pitch: story-first journalist pitches with angle development framework
- change-management-plan: stakeholder analysis, comms strategy, adoption metrics
- workshop-facilitation-guide: activity instructions, decision protocols, facilitator moves
- sales-forecasting-model: pipeline model, scenario analysis, assumption log
- tax-planning-checklist: year-end tax planning across income, pension, CGT, reliefs

Quality improvements across all 93 existing skills:
- Standardised description format: "Verb the thing. Use when X. Produces Y."
- Added Required Inputs section to all skills missing it (prompts for missing info)
- Added Quality Checks section to all skills missing it (specific, not generic)
- Fixed broken multiline YAML descriptions
- Removed non-standard frontmatter keys (tool_integration, metadata blocks)

README updated to v6.0.0 with 100-skill count, new skill tables, and article series

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

skills/competitor-signal-tracker/SKILL.md

@@ -1,13 +1,19 @@
 ---
 name: competitor-signal-tracker
-description: Analyse competitor moves and surface strategic implications for your product
-tool_integration: Notion
+description: "Analyse competitor moves and surface strategic implications for your product. Use when asked to track competitor signals, analyse a competitor announcement, understand what a competitor is doing strategically, or produce a competitive intelligence report. Produces a categorised signal analysis with threat ratings, roadmap implications, and recommended responses."
 ---
+
 # Competitor Signal Tracker Skill
 
-## Purpose
 Turn scattered competitor information into structured strategic intelligence — not just "what they did" but "what it means for us."
 
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Competitor name(s)** and the signals/updates to analyse
+- **Your product's current roadmap or strategic priorities** (to assess relevance)
+- **Time period** the signals cover (this week, this month, etc.)
+
 ## Signal Categories to Track
 - **Product signals:** New features, removals, UX changes, beta programmes
 - **Pricing signals:** Changes to tiers, free limits, enterprise terms
@@ -21,8 +27,9 @@ Turn scattered competitor information into structured strategic intelligence —
 3. Rate strategic threat level: High / Medium / Low / Watch
 4. Connect to your roadmap: does this accelerate, validate, or challenge any of your bets?
 5. Recommend a response: Accelerate existing initiative / Deprioritise / Monitor / Investigate further
+6. **Validate** — Confirm every High threat has a specific recommended response with an owner. "Monitor" is not an acceptable response for High-rated threats.
 
-## Output Format
+## Output Structure
 
 ### Competitive Intelligence Report — [Date]
 
@@ -35,4 +42,12 @@ Turn scattered competitor information into structured strategic intelligence —
 **Recommended Response:** [Action + owner + timeline]
 
 #### Strategic Summary
-[2-3 sentences on the overall competitive landscape shift this week/month]
+[2-3 sentences on the overall competitive landscape shift this period]
+
+## Quality Checks
+
+- [ ] Every signal is categorised (not just described)
+- [ ] Threat level is justified — not assigned arbitrarily
+- [ ] High-threat signals have specific recommended responses (not "monitor")
+- [ ] Implications connect to specific roadmap items or strategic bets
+- [ ] Strategic summary gives a landscape-level view, not just a list of individual signals