| name | performance-indicators |
| user-invocable | false |
| description | Use when defining, revising, or reviewing the rebuild quality bar and KPI model in docs/quality-and-growth/performance-indicators.md; when deciding launch criteria, evaluation metrics, review cadence, traffic or trust KPIs, conversion KPIs, or how the project should be assessed over time. |
Performance Indicators
What this skill is for
Use this skill when a task affects how the rebuild and the site are evaluated.
It covers:
- launch quality bar,
- KPI definitions,
- review cadence,
- traffic and engagement metrics,
- trust and distribution metrics,
- conversion metrics,
- and content-system health metrics.
KPI-first framing
This skill is not only about deciding when work can stop.
It should also catch:
- what should be measured after launch,
- which signals matter most,
- how those signals relate to trust and revenue potential,
- and how to judge whether the rebuilt system is actually working over time.
Default file targets
docs/quality-and-growth/performance-indicators.mddocs/README.md
What belongs here
Use this skill for questions such as:
- what must be true before launch,
- which KPIs should be tracked,
- how UX, technical quality, and content health connect,
- and how often the site should be reviewed after release.
Decision rules
If the change affects evaluation, measurement, launch readiness, or review cadence, it belongs here.
If the change is about project sequencing rather than evaluation, coordinate with project-workspace-management.
If the change affects ad behavior or conversion flows, check whether content-and-sidebar-strategy also needs an update.
How to work
- Start with
docs/quality-and-growth/performance-indicators.md as the evaluation source of truth.
- Distinguish clearly between launch gate and ongoing KPI tracking.
- Prefer measurable signals over vague success language.
- Keep launch gate requirements narrow and defensible.
- Make sure KPIs map back to user trust, engagement, or conversion value.
Output expectation
When using this skill, explain:
- which quality bar or KPI changed,
- whether it affects launch criteria or post-launch measurement,
- which project files must stay aligned,
- and what future agents should evaluate going forward.
