Agent skill · Testing & QA

langfuse-dashboard

Automates Langfuse Cloud dashboard interactions using Playwright MCP. Captures screenshots for documentation, extracts metrics for monitoring, navigates trace details for investigation, and handles authentication. Use when documenting workflows, creating compliance screenshots, monitoring dashboard metrics, or investigating traces visually. MUST use Playwright MCP tools (mcp__playwright__*) for browser automation.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill langfuse-dashboard --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 8 KB
Bundled scripts: none
Allowed tools: BashReadWritemcp__playwright__browser_navigatemcp__playwright__browser_snapshotmcp__playwright__browser_take_screenshotmcp__playwright__browser_clickmcp__playwright__browser_wait_formcp__playwright__browser_evaluatemcp__playwright__browser_close
Path: skills/ai-llm/langfuse-dashboard/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Langfuse Dashboard Skill **Purpose**: Automate Langfuse Cloud dashboard interactions via Playwright MCP for screenshots, metrics, and trace investigation. **Dashboard URL**: https://cloud.langfuse.com/project/cmhuwhcfe006yad06cqfub107 --- ## When to Use This Skill ✅ **Use when**: - Capturing dashboard screenshots for documentation or compliance reports - Extracting metrics (trace count, costs, latency) for monitoring/alerting - Navigating to specific trace details for visual investigation - Creating walkthrough documentation with annotated screenshots - Automating repetitive dashboard checks ❌ **Do NOT use when**: - Programmatic data extraction (use `langfuse-extraction` skill with API) - Adding instrumentation to code (use `langfuse-integration` skill) --- ## Prerequisites 1. **Playwright MCP server enabled** (`/mcp` command) 2. **Langfuse Cloud account** with project access 3. **Authentication**: Login cookies or credentials ready --- ## Common Workflows ### Workflow 1: Capture Dashboard Overview Screenshot ``` Purpose: Document current dashboard state for reports Steps: 1. Navigate to dashboard 2. Wait for content to load (CRITICAL: networkidle) 3. Take full-page screenshot 4.

What's inside
Steps it walks through
  1. When to Use This Skill
  2. Prerequisites
  3. Common Workflows
  4. Workflow 1: Capture Dashboard Overview Screenshot
  5. Workflow 2: Extract Dashboard Metrics
  6. Workflow 3: Navigate to Specific Trace
  7. Workflow 4: Filter Traces by Tag
  8. Best Practices
  9. Always Wait for Network Idle
  10. Use Snapshots for Data Extraction
  11. Handle Authentication
  12. Common Dashboard URLs
  13. Troubleshooting
  14. Issue: Blank Screenshots
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the langfuse-dashboard skill do?

Automates Langfuse Cloud dashboard interactions using Playwright MCP. Captures screenshots for documentation, extracts metrics for monitoring, navigates trace details for investigation, and handles authentication. Use when documenting workflows, creating compliance screenshots, monitoring dashboard metrics, or investigating traces visually. MUST use Playwright MCP tools (mcp__playwright__*) for browser automation.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill langfuse-dashboard --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going