Menu
Track skill performance and emerging patterns
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Pre-meeting context gathering across all connected systems. Pulls recent interactions, open items, and suggested talking points for any person or topic. Triggers on: "meeting prep", "prep for my meeting", "meeting with X", "prep for 1:1".
Pulls a Granola meeting transcript and updates people files with per-person intelligence: what they said, what they pushed back on, what they committed to. Compounds over time — each meeting adds a layer. Triggers on: "sync people", "update people from meeting", "update stakeholders", "/people-sync".
Competitive analysis and market research with source attribution. Parallel fan-out across web, review sites, and news. Triggers on: "market research", "competitive analysis", "competitor comparison".
Voice profile configuration and application for consistent writing. Configure once with 2-3 samples, apply everywhere. Triggers on: "writing style", "voice profile", "apply my voice", writing long-form content.
Platform-optimized Substack Notes creation. 500-char limit, hook-driven, engagement-focused. Triggers on: "write a Substack Note", "Substack content", "Note ideas".
Test-driven development enforcement with RED-GREEN-IMPROVE cycle
| name | meta-observer |
| description | Track skill performance and emerging patterns |
| origin | pm-pilot |
| version | 1.0.0 |
| triggers | ["observe skills","skill performance","passive (runs in background)"] |
Track which skills are used, how well they work, and what patterns emerge.
For each skill invocation:
Log Observation
Append to .claude/logs/skill-observations.md:
## {date}
| Skill | Trigger | Outcome | Corrections | Notes |
|-------|---------|---------|-------------|-------|
| {name} | {trigger} | {outcome} | {yes/no} | {brief note} |
Detect Patterns After logging, scan for:
Surface Insights When patterns emerge:
Skill Observations:
- {skill} triggered {count} times, corrected {count} times
- Pattern: {description of recurring issue}
- Suggestion: {improvement recommendation}
Update Lessons
Write significant findings to tasks/lessons.md:
Skill Observations (last 7 days):
Most used: orchestrator (8x), tdd-workflow (5x)
Corrected: handoff-doc (2x) - missing file paths
Unused: meta-observer, strategic-compact
Pattern: Users trigger "verify" but mean "tdd-workflow"
Suggestion: Add "verify" as tdd-workflow trigger
.claude/logs/ directory if it does not exist