Skip to content
Back to skills

Perf Harness

ASecurity

Tooling for the creo-perf skill: deterministic benchmark scripts (scenario captures with EXPLAIN medians and p50/p95 HTTP loops, Lighthouse initial-load audit, platform and schema audits, pg_stat_statements workload discovery, auto-rebuilt before/after dashboard) plus the project scaffolder used by /creo perf init. Not invoked directly; creo-perf routes to it.

  • 4 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 22, 2026
ai-agentsbashsqlbackend

Security analysis

A100/100

Pro scans all 20 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add oyusypenko/creo --skill perf-harness --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Perf Harness?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Perf Harness
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/oyusypenko-perf-harness/badge)](https://www.skillsdirectory.com/skills/oyusypenko-perf-harness)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: creo-perf-harness
description: >
  Tooling for the creo-perf skill: deterministic benchmark scripts (scenario
  captures with EXPLAIN medians and p50/p95 HTTP loops, Lighthouse initial-load
  audit, platform and schema audits, pg_stat_statements workload discovery,
  auto-rebuilt before/after dashboard) plus the project scaffolder used by
  /creo perf init. Not invoked directly; creo-perf routes to it.
allowed-tools:
  - Read
  - Bash
---

# creo-perf-harness

This directory holds the executable half of the `creo-perf` skill. It has no
commands of its own: `/creo perf ...` loads `creo-perf` (the playbook), which
runs these scripts.

| Script | Role |
|---|---|
| `scripts/init-project.sh` | scaffold `.claude/skills/creo-perf/` in a project from `templates/` |
| `scripts/preflight.sh` | tools, targets, scenarios, SQL mode sanity |
| `scripts/audit-all.sh <label>` | every capture in the configured order + workload window |
| `scripts/audit-scenario.sh <id> <label>` | one scenario: EXPLAIN medians, HTTP loops, wire bytes, ETag replay, FE probe |
| `scripts/audit-fe.sh <label>` | served assets, production build, bundle composition, Lighthouse xN |
| `scripts/audit-platform.sh <label>` | backend process facts + PostgreSQL settings (context, not metrics) |
| `scripts/audit-schema.sh <label>` | tables, columns, indexes, hypopg verdicts, PostGIS shape |
| `scripts/observability-setup.sh` | pg_stat_statements + auto_explain (+hypopg); restarts the DB |
| `scripts/workload-{pre,drive,post}.sh` | discovery window: reset, drive scenario traffic, rank hot queries |
| `scripts/common/build-dashboard.py` | pivot all captures into `results/dashboard.md` with deltas |
| `scripts/common/sql-runners.py` | psql runner files from hand-written SQL (compile) or real app code (record) |
| `scripts/common/fe-interactions.mjs` | Playwright interaction probe: requests fired, rows held, long tasks |

Every script reads the project's `.claude/skills/creo-perf/perf.config.sh`.
See `README.md` for requirements and `creo-perf/references/scenario-spec.md`
for the scenario file contract.

Files in this skill

  • README.md6.3 KB
  • SKILL.md2.1 KB
  • install.ps11015 B
  • install.sh1.5 KB
  • scripts/audit-all.sh2.8 KB
  • scripts/audit-fe.sh12.9 KB
  • scripts/audit-platform.sh8.9 KB
  • scripts/audit-scenario.sh6.3 KB
  • scripts/audit-schema.sh8.2 KB
  • scripts/common/build-dashboard.py11.5 KB
  • scripts/common/fe-interactions.mjs6.1 KB
  • scripts/common/lib-harness.sh5.8 KB
  • scripts/common/lib-scenario.sh9.8 KB
  • scripts/common/sql-runners.py6.3 KB
  • scripts/init-project.sh4.5 KB
  • scripts/observability-setup.sh3.7 KB
  • scripts/preflight.sh3.9 KB
  • scripts/workload-drive.sh924 B
  • scripts/workload-post.sh4.9 KB
  • scripts/workload-pre.sh1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.