meta-observer

Solid

Track skill performance and emerging patterns

AI & Automation 17 stars 4 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
42
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Meta Observer Track which skills are used, how well they work, and what patterns emerge. ## When to Use - Explicitly: "observe skills", "skill performance" - Passively: after any session with 3+ skill invocations - Periodically: weekly review of skill usage ## What to Track For each skill invocation: - **Skill name**: which skill was triggered - **Trigger**: what phrase or condition activated it - **Outcome**: success, partial, failed - **Corrections**: did the user correct the output - **Duration**: rough time spent (fast/medium/slow) ## Procedure 1. **Log Observation** Append to `.claude/logs/skill-observations.md`: ```markdown ## {date} | Skill | Trigger | Outcome | Corrections | Notes | |-------|---------|---------|-------------|-------| | {name} | {trigger} | {outcome} | {yes/no} | {brief note} | ``` 2. **Detect Patterns** After logging, scan for: - Skills never used (candidates for removal) - Skills frequently corrected (need refinement) - Missing skills (user repeatedly does something manually) - Trigger mismatches (wrong skill activates) 3. **Surface Insights** When patterns emerge: ``` Skill Observations: - {skill} triggered {count} times, corrected {count} times - Pattern: {description of recurring issue} - Suggestion: {improvement recommendation} ``` 4. **Update Lessons** Write significant findings to `tasks/lessons.md`: - Skill gaps discover...

Details

Author
mshadmanrahman
Repository
mshadmanrahman/pm-pilot
Created
5 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

task-observer

Monitors task execution for skill improvement opportunities. Use this skill during ANY multi-step task, agentic workflow, or substantive work session where the agent is using tools and producing deliverables. It captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable skills. Also triggers during post-task feedback discussions and when the user explicitly mentions skill observations, improvements, the observation log, skill taxonomy, or asks the agent to watch for skill opportunities. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: this skill should be invoked at the start of every task-oriented session — if you are about to use tools to produce deliverables, invoke this skill first. For reliable activation, pair this description with a CLAUDE.md instruction or harness-level session-start hook (see Recommended Activation Setup) — description-level matching alone is not enforceable.

1,951 Updated 1 weeks ago
rebelytics
DevOps & Infrastructure Listed

task-observer

Monitors task execution for skill improvement opportunities. Use this skill during ANY multi-step task, agentic workflow, or substantive work session where the agent is using tools and producing deliverables. It captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable skills. Also triggers during post-task feedback discussions and when the user explicitly mentions skill observations, improvements, the observation log, skill taxonomy, or asks the agent to watch for skill opportunities. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: this skill should be invoked at the start of every task-oriented session — if you are about to use tools to produce deliverables, invoke this skill first. For reliable activation, pair this description with a CLAUDE.md instruction or harness-level session-start hook (see Recommended Activation Setup) — description-level matching alone is not enforceable.

1 Updated 1 weeks ago
mostwise
Code & Development Featured

skill-monitor

Analyze skill effectiveness across sessions. Computes per-skill metrics (action rate, friction, outcomes), identifies degrading skills, and generates improvement recommendations. Requires session-scan data in metrics.jsonl.

528 Updated yesterday
oliver-kriska