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>
This commit is contained in:
mohitagw15856
2026-04-20 20:52:31 +01:00
parent 34b0f780e6
commit f3b9d008fe
70 changed files with 2173 additions and 599 deletions
@@ -1,21 +1,19 @@
---
name: competitive-intelligence-monitor
description: Continuously monitors competitor signals and surfaces strategic
implications for your roadmap. Use when user asks to "monitor competitors",
"track competitive landscape", "what are competitors doing this week",
"competitive briefing", or "what has changed in the market".
metadata:
author: Mohit Aggarwal
version: 1.0.0
category: strategy
tags: [strategy, competitive-intel, roadmapping]
documentation: https://github.com/mohitagw15856/pm-claude-skills
description: "Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/medium/low priority signals, roadmap implications, and a strategic landscape summary."
---
# Competitive Intelligence Monitor Skill
## Purpose
Turn scattered competitor updates into structured weekly intelligence — not just
"what they did" but "what changed since last week and what it means for us."
Turn scattered competitor updates into structured weekly intelligence — not just "what they did" but "what changed since last week and what it means for us."
## Required Inputs
Ask the user for these if not provided:
- **Competitors to monitor** (list of company names)
- **Your current roadmap or strategic priorities** (to assess relevance of signals)
- **Previous brief or last run summary** (for diff mode — what's new vs. last time)
- **Time period** (this week, this month)
## Signal Categories to Monitor
- **Product signals:** New features, removals, UX changes, beta programmes
@@ -33,6 +31,7 @@ Turn scattered competitor updates into structured weekly intelligence — not ju
4. Rate threat level: High / Medium / Low / Watch
5. Connect each signal to a specific item on the provided roadmap
6. Recommend response: Accelerate / Deprioritise / Monitor / Investigate
7. **Validate** — Every High signal must have a specific recommended action and owner. "Monitor" is only acceptable for Low and Watch ratings.
### Subsequent Runs (Diff Only)
1. Compare current signals against previous run summary
@@ -40,7 +39,7 @@ Turn scattered competitor updates into structured weekly intelligence — not ju
3. Flag if a previously Low signal has escalated to High
4. Keep output under 300 words — brevity is the point
## Output Format
## Output Structure
### Competitive Intelligence Brief — [Date]
**New Since Last Run:** [n signals]
@@ -57,7 +56,10 @@ Turn scattered competitor updates into structured weekly intelligence — not ju
**This Week's Strategic Summary:**
[2 sentences max — what is the overall competitive landscape doing?]
## OpenClaw Configuration
Add to YAML frontmatter for scheduled runs:
`schedule: weekly-monday-0800`
Persistent memory stores last run summary for diff comparison.
## Quality Checks
- [ ] Every High-priority signal has a specific response action and owner
- [ ] Signals are categorised (not just listed as "they did X")
- [ ] Roadmap connections are specific (not "generally relevant")
- [ ] Diff mode output is under 300 words
- [ ] Strategic summary describes the landscape trend, not just repeats individual signals