meta-observer

Log skill invocations and analyze triggers, outcomes, corrections, and durations.

12|4|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/mshadmanrahman/pm-pilot --skill meta-observer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-observer
Source: https://github.com/mshadmanrahman/pm-pilot/tree/main/skills/productivity/meta-observer
Command: npx skills add https://github.com/mshadmanrahman/pm-pilot --skill meta-observer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track and analyze how skill invocations impact outcomes, enabling continuous improvement of skill usage.

Core Features & Use Cases

  • Track invocation context: trigger, outcome, corrections, and duration for each skill use.
  • Surface insights: identify patterns, frequent corrections, and unused skills for refinement.
  • Weekly review: generate summaries for product teams to inform optimizations.

Quick Start

Enable passive logging of skill invocations and review the generated insights after each session.

Frequently Asked Questions about meta-observer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track skill usage and analyze performance patterns?

To track skill usage and analyze performance patterns, enable passive logging to automatically capture invocation triggers, outcomes, corrections, and durations across sessions for periodic review.

What is skill invocation logging and how does it reveal usage insights?

Skill invocation logging is a non-intrusive tracking mechanism that records the trigger, outcome, corrections, and duration for each skill use, writing to internal logs to surface performance insights and frequent correction patterns.

Can I generate weekly summaries from skill usage logs to inform optimizations?

Yes, you can generate weekly review summaries from skill usage logs to help product teams identify unused skills, frequent corrections, and performance patterns to inform continuous optimization.

Does passive skill tracking disrupt active sessions or require manual input?

Passive skill tracking remains completely non-intrusive during active sessions, automatically logging invocations and writing outputs to internal logs without requiring manual input or disrupting your workflow.

What is the best way to identify unused skills and frequent corrections across sessions?

The best way to identify unused skills and frequent corrections is to apply non-intrusive usage analytics across sessions, automatically logging invocation data to surface refinement opportunities for product teams.