monitoring-observability

yonatangross/orchestkit · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/yonatangross/orchestkit --skill monitoring-observability
0 commentsdiscussion
summary

Comprehensive patterns for infrastructure monitoring, LLM observability, and quality drift detection. Each category has individual rule files in rules/ loaded on-demand.

skill.md

Monitoring & Observability

Comprehensive patterns for infrastructure monitoring, LLM observability, and quality drift detection. Each category has individual rule files in rules/ loaded on-demand.

Quick Reference

Category Rules Impact When to Use
Infrastructure Monitoring 3 CRITICAL Prometheus metrics, Grafana dashboards, alerting rules
LLM Observability 3 HIGH Langfuse tracing, cost tracking, evaluation scoring
Drift Detection 3 HIGH Statistical drift, quality regression, drift alerting
Silent Failures 3 HIGH Tool skipping, quality degradation, loop/token spike alerting

Total: 12 rules across 4 categories

Quick Start

# Prometheus metrics with RED method
from prometheus_client import Counter, Histogram

http_requests = Counter('http_requests_total', 'Total requests', ['method', 'endpoint', 'status'])
http_duration = Histogram('http_request_duration_seconds', 'Request latency',
    buckets=[0.01, 0.05, 0.1, 0.5, 1, 2, 5])
# Langfuse v4 LLM tracing — semantic as_type + inline scoring
from langfuse import observe, get_client

@observe(as_type="generation", name="analyze_content")
async def analyze_content(content: str):
    get_client().update_current_trace(
        user_id="user_123", session_id="session_abc",
        tags=["production", "orchestkit"],
    )
    result = await llm.generate(content)
    get_client().score_current_span(name="response_quality", value=0.85)
    return result
# PSI drift detection
import numpy as np

psi_score = calculate_psi(baseline_scores, current_scores)
if psi_score >= 0.25:
    alert("Significant quality drift detected!")

Infrastructure Monitoring

Prometheus metrics, Grafana dashboards, and alerting for application health.

Rule File Key Pattern
Prometheus Metrics rules/monitoring-prometheus.md RED method, counters, histograms, cardinality
Grafana Dashboards rules/monitoring-grafana.md Golden Signals, SLO/SLI, health checks
Alerting Rules rules/monitoring-alerting.md Severity levels, grouping, escalation, fatigue prevention

LLM Observability

Langfuse-based tracing, cost tracking, and evaluation for LLM applications.

Rule File Key Pattern
Langfuse Traces rules/llm-langfuse-traces.md @observe decorator, OTEL spans, agent graphs
Cost Tracking rules/llm-cost-tracking.md Token usage, spend alerts, Metrics API v2
Eval Scoring rules/llm-eval-scoring.md Custom scores, evaluator tracing, quality monitoring

Drift Detection

Statistical and quality drift detection for production LLM systems.

Rule File Key Pattern
Statistical Drift rules/drift-statistical.md PSI, KS test, KL divergence, EWMA
Quality Drift rules/drift-quality.md Score regression, baseline comparison, canary prompts
Drift Alerting rules/drift-alerting.md Dynamic thresholds, correlation, anti-patterns

Silent Failures

Detection and alerting for silent failures in LLM agents.

Rule File Key Pattern
Tool Skipping rules/silent-tool-skipping.md Expected vs actual tool calls, Langfuse traces
Quality Degradation rules/silent-degraded-quality.md Heuristics + LLM-as-judge, z-score baselines
Silent Alerting rules/silent-alerting.md Loop detection, token spikes, escalation workflow

Key Decisions

Decision Recommendation Rationale
Metric methodology RED method (Rate, Errors, Duration) Industry standard, covers essential service health
Log format Structured JSON Machine-parseable, supports log aggregation
Tracing OpenTelemetry Vendor-neutral, auto-instrumentation, broad ecosystem
LLM observability Langfuse (not LangSmith) Open-source, self-hosted, built-in prompt management
LLM tracing API @observe(as_type=...) + score_current_span() v4: semantic types, inline scoring, span filtering
Langfuse APIs Observations API v2 + Metrics API v2 v4 (Mar 2026): faster querying, aggregations at scale
Drift method PSI for production, KS for small samples PSI is stable for large datasets, KS more sensitive
Threshold strategy Dynamic (95th percentile) over static Reduces alert fatigue, context-aware
Alert severity 4 levels (Critical, High, Medium, Low) Clear escalation paths, appropriate response times

Detailed Documentation

Resource Description
${CLAUDE_SKILL_DIR}/references/ Logging, metrics, tracing, Langfuse, drift analysis guides
${CLAUDE_SKILL_DIR}/checklists/ Implementation checklists for monitoring and Langfuse setup
${CLAUDE_SKILL_DIR}/examples/ Real-world monitoring dashboard and trace examples
${CLAUDE_SKILL_DIR}/scripts/ Templates: Prometheus, OpenTelemetry, health checks, Langfuse

Related Skills

  • defense-in-depth - Layer 8 observability as part of security architecture
  • devops-deployment - Observability integration with CI/CD and Kubernetes
  • resilience-patterns - Monitoring circuit breakers and failure scenarios
  • llm-evaluation - Evaluation patterns that integrate with Langfuse scoring
  • caching - Caching strategies that reduce costs tracked by Langfuse
how to use monitoring-observability

How to use monitoring-observability on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add monitoring-observability
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/yonatangross/orchestkit --skill monitoring-observability

The skills CLI fetches monitoring-observability from GitHub repository yonatangross/orchestkit and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/monitoring-observability

Reload or restart Cursor to activate monitoring-observability. Access the skill through slash commands (e.g., /monitoring-observability) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.757 reviews
  • Dhruvi Jain· Dec 28, 2024

    Registry listing for monitoring-observability matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Ama Abbas· Dec 24, 2024

    Useful defaults in monitoring-observability — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Lucas Ndlovu· Dec 20, 2024

    monitoring-observability is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Anaya Ghosh· Dec 8, 2024

    Registry listing for monitoring-observability matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Zara Mehta· Dec 4, 2024

    Solid pick for teams standardizing on skills: monitoring-observability is focused, and the summary matches what you get after install.

  • Benjamin Zhang· Nov 27, 2024

    Solid pick for teams standardizing on skills: monitoring-observability is focused, and the summary matches what you get after install.

  • Soo Bhatia· Nov 23, 2024

    Registry listing for monitoring-observability matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Oshnikdeep· Nov 19, 2024

    Solid pick for teams standardizing on skills: monitoring-observability is focused, and the summary matches what you get after install.

  • Aanya Chen· Nov 15, 2024

    I recommend monitoring-observability for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mia Brown· Nov 11, 2024

    Keeps context tight: monitoring-observability is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 57

1 / 6