Skip to content
Agentmart
Submit a tool

performance-report

Capture browser performance traces and turn Core Web Vitals, network, console, and rendering evidence into actionable reports.

Skill by Anders-planck

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/anders-planck-performance-report

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Capture browser performance traces and turn Core Web Vitals, network, console, and rendering evidence into actionable reports. Use when profiling web performance, diagnosing regressions, comparing builds, or producing a visual performance audit.

Use cases: documents, security

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/performance-report

What's inside

Skill name
performance-report
Description
Capture browser performance traces and turn Core Web Vitals, network, console, and rendering evidence into actionable reports. Use when profiling web performance, diagnosing regressions, comparing builds, or producing a visual performance audit.
License
MIT
Instructions
18 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Performance Report

## Workflow

1. Define the page, scenario, device, network, cache, and comparison baseline.
2. Use Chrome DevTools tooling for traces, network requests, console messages, and source-mapped stacks.
3. Record LCP, INP, CLS, FCP, TBT, resource weight, and critical request chains when available.
4. Tie each recommendation to trace evidence and estimated user impact.
5. Render structured findings as Markdown or self-contained HTML.

## Guardrails

- Do not open a remote-debugging port on a sensitive browser profile.
- Do not compare runs with different cache or throttling conditions without disclosure.
- Separate lab measurements from real-user monitoring.
- Avoid claiming causation from a single trace when evidence is only correlational.

From Anders-planck/orditra, MIT.

More from Anders-planck/orditra

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 12, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Anders-planck

Cite this page

performance-report skill. Agent Mart. https://agentmart.dev/skills/anders-planck-performance-report (last updated 2026-10-24)