Topic: observability
71 skills in this topic.
-
ask-questions-if-underspecified
Ask clarifying questions when requirements are underspecified
alfredolopez80/multi-agent-ralph-loop 115
-
adversarial
Multi-Agent Adversarial Analysis System for code security
alfredolopez80/multi-agent-ralph-loop 115
-
writing-helper
A versatile writing assistant that helps compose, improve, and transform text for various purposes including emails, letters, reports, social media, and more
AIGNE-io/aigne-framework 363
-
octopoda-memory
Persistent memory across sessions — recall, store, share, audit decisions, snapshots, and version history
RyjoxTechnologies/Octopoda-OS 109
-
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
langfuse/langfuse 24,320
-
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
langfuse/langfuse 24,320
-
turborepo
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines,
dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment
variables, internal packages, monorepo structure/best practices, and boundaries.
Use when user: configures tasks/workflows/pipelines, creates packages, sets up
monorepo, shares code between apps, runs changed/affected packages, debugs cache,
or has apps/packages directories.
langfuse/langfuse 24,320
-
frontend-browser-review
Shared workflow for browser-based review of user-visible frontend changes in Langfuse.
Use when a change affects UI behavior, layout, styling, navigation, or browser-visible
regressions and should be checked with the Playwright MCP server before signoff.
langfuse/langfuse 24,320
-
code-review
Shared code review workflow for Langfuse. Use when reviewing a PR, branch, diff,
or local changes for correctness, regressions, risk, and missing tests.
Start with references/review-checklist.md for repo-specific review rules and
use package AGENTS.md files plus any matching shared skills when the change
touches those areas.
langfuse/langfuse 24,320
-
clickhouse-best-practices
MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 28 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.
langfuse/langfuse 24,320
-
changelog-writing
Shared workflow for writing Langfuse changelog entries after a feature is complete.
Use when a branch is ready for merge and a changelog entry or changelog draft is needed.
langfuse/langfuse 24,320
-
backend-dev-guidelines
Shared backend guide for Langfuse's Next.js 14, tRPC, BullMQ, and TypeScript monorepo. Use when creating or reviewing tRPC routers, public REST endpoints, BullMQ queue processors, backend services, middleware, Prisma or ClickHouse data access, OpenTelemetry instrumentation, Zod validation, env configuration, or backend tests across web, worker, or packages/shared.
langfuse/langfuse 24,320
-
agent-setup-maintenance
Shared workflow for editing Langfuse's repo-owned agent setup under `.agents/`.
Use when changing AGENTS files, shared skills, `.agents/config.json`,
generated shim behavior, provider discovery paths, or install-time agent sync.
langfuse/langfuse 24,320
-
add-model-price
Use when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/types.ts, pricing tiers, tokenizer IDs, or matchPattern regexes for OpenAI, Anthropic, Bedrock, Vertex, Azure, or Gemini model pricing.
langfuse/langfuse 24,320
-
context-recovery
Recover lost context after session compaction or when information from previous sessions is needed. Use when: user mentions "what were we working on", "I lost context", "before the compact", "previous session", or asks about decisions/implementations/discussions that aren't in current context. Also use proactively when you notice references to prior work you lack context for.
omgpointless/aspy 1
-
instrumentation-planning
Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
nexus-labs-automation/mobile-observability 108
-
interaction-latency
Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.
nexus-labs-automation/mobile-observability 108
-
navigation-latency
Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.
nexus-labs-automation/mobile-observability 108
-
network-tracing
Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.
nexus-labs-automation/mobile-observability 108
-
session-replay
Set up session replay for visual debugging. Use when implementing screen recording, replay features, or visual debugging tools.
nexus-labs-automation/mobile-observability 108
-
symbolication-setup
Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
nexus-labs-automation/mobile-observability 108
-
user-journey-tracking
Track user journeys with intent context and friction signals. Use when instrumenting onboarding, checkout, or any multi-step flow where you need to understand WHY users fail.
nexus-labs-automation/mobile-observability 108
-
crash-instrumentation
Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
nexus-labs-automation/mobile-observability 108