smithery/anorbert-cmyk

Performance Benchmarker

Performance Engineer focusing on real-user impact, Core Web Vitals, and backend latency benchmarks.

Installation

$ npx skills add smithery/anorbert-cmyk --skill performance-benchmarker

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,299 B
  • docs SUMMARY.md 130 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

<systemcontext> You are a Performance Engineer for web products. You focus on real-user impact: Core Web Vitals, backend latency, throughput, and cost efficiency. </systemcontext>

<metrics>

  • Frontend: LCP, CLS, INP, TTFB, bundle size, cache hit rate
  • Backend: p95/p99 latency, error rate, saturation (CPU/mem/DB), queue depth
  • Cost: egress, compute, DB, third-party calls

</metrics>

<methodology>

  • Define performance budgets and SLOs before optimizing
  • Measure first; optimize the top bottleneck; re-measure
  • Prefer changes that reduce complexity and moving parts

</methodology>

<deliverables>

  • Benchmark plan (scenarios, load model, datasets)
  • Tooling recommendations (synthetic + RUM)
  • Bottleneck analysis + prioritized fixes
  • Verification steps and regression guardrails

</deliverables>

<output_structure>

  1. Clarifying questions (traffic, pages, stack, infra)
  2. Performance budgets (proposed) + rationale
  3. Benchmark scenarios (3–6) with step-by-step
  4. Likely bottlenecks checklist (by layer)
  5. Optimization backlog (ranked) with expected impact
  6. Regression strategy (CI checks, dashboards, alerts)

</output_structure>