Contract
When a RepositoryAuditArtifact identifies a performance risk, distinguish a
measured bottleneck from a structural risk or speculative optimization. Require
a measurable target and representative workload before recommending changes.
- Input: performance goal, workload, architecture, measurements, environment, and suspected bottlenecks.
- Output: performance hypothesis, profiling plan, bottleneck analysis, remediation options, and validation criteria.
- Scope: do not optimize without a measurable target and representative workload.
- Rule: do not optimize without a measurable target and representative workload.
- Rule: documented standards override defaults; explicit project rules take precedence.
- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.
Provenance
| Question |
Answer |
| What is the source of truth? |
The user's request, originating spec/issue, and the skill's declared outputs |
| What is in scope? |
Work covered by the skill's acceptance criteria and completion rules |
| What is explicitly out of scope? |
Files, behaviors, and decisions outside the skill's declared boundary |
| Who or what consumes this artifact afterward? |
The next skill in the workflow or the user |
| What evidence proves it is done? |
Completion criteria met, artifact saved, validation passed |
| What risk remains? |
Subjective judgment calls, missing context, or external dependency failures |
Artifact
Emit PerformanceArtifact as both:
- JSON:
.agents/skills/platform/artifacts/performance/{identifier}.json
- Markdown view: same filename with
.md extension
Performance
Use this skill when diagnosing or improving latency, throughput, resource usage, scalability, capacity, or performance regressions in a system.
Rules
- Rule: define the target metric, workload, and measurement environment before interpreting results.
- Rule: separate latency percentiles, throughput, saturation, utilization, and error rate.
- Rule: compare baseline and changed behavior with the same workload.
- Rule: identify the limiting resource before prescribing changes.
- Rule: include regression checks so improvements do not silently degrade later.
Steps
- Define user-visible target, SLO or benchmark, workload, and environment.
- Gather baseline measurements and instrumentation gaps.
- Build hypotheses about bottlenecks across CPU, memory, I/O, network, locks, and external services.
- Profile at the narrowest seam that can confirm or reject the hypothesis.
- Recommend remediation with trade-offs and expected impact.
- Define validation, regression checks, and rollout monitoring.
Completion
- the skill's completion criteria are explicitly checked
- the artifact is saved and validated
- any blockers or skipped validations are documented
- the next consumer is identified or the work is handed off
@include .agents/skills/platform/contract-base.xml
1---2name: "performance"3category: "platform"4maturity: "stable"5version: "1"6description: "Measure and improve system performance — latency, throughput, resource usage, bottlenecks, and capacity planning — with reproducible profiling."7license: "MIT"8capabilities:9 - trace latency and resource paths across the system10 - consume code-review audit findings11 - trace performance decisions across inputs, constraints, and failure paths12 - validate platform outcomes with evidence, assumptions, and explicit next steps13outputs: "performance hypothesis, profiling plan, bottleneck analysis, remediation options, and validation criteria."14sideEffects: []15dependencies: []16stopCondition: "Performance target, measurements, bottleneck, and validation plan are explicit."17risk: "low"18trustTier: "1"19maxIterations: "6"20promptVersion: "2.0"21artifactType: "platform/performance"22modelTier: "reasoning"23evaluators: ["behavioral", "regression"]24fixturesPath: ".agents/skills/platform/fixtures/behavioral/performance.json"25diataxis: "how-to"26tags: ["platform/performance"]27compatibility: [code-review, backend-architecture, performance-testing]28approvalRequired: "false"29approvalFor: []30metadata:31 source: https://skillmd.com/skills/quantumquirkxyz/performance32---3334## Contract3536When a `RepositoryAuditArtifact` identifies a performance risk, distinguish a37measured bottleneck from a structural risk or speculative optimization. Require38a measurable target and representative workload before recommending changes.3940- Input: performance goal, workload, architecture, measurements, environment, and suspected bottlenecks.41- Output: performance hypothesis, profiling plan, bottleneck analysis, remediation options, and validation criteria.42- Scope: do not optimize without a measurable target and representative workload.43- Rule: do not optimize without a measurable target and representative workload.44- Rule: documented standards override defaults; explicit project rules take precedence.45- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.4647## Provenance4849| Question | Answer |50|---|---|51| What is the source of truth? | The user's request, originating spec/issue, and the skill's declared outputs |52| What is in scope? | Work covered by the skill's acceptance criteria and completion rules |53| What is explicitly out of scope? | Files, behaviors, and decisions outside the skill's declared boundary |54| Who or what consumes this artifact afterward? | The next skill in the workflow or the user |55| What evidence proves it is done? | Completion criteria met, artifact saved, validation passed |56| What risk remains? | Subjective judgment calls, missing context, or external dependency failures575859## Artifact6061Emit `PerformanceArtifact` as both:62- JSON: `.agents/skills/platform/artifacts/performance/{identifier}.json`63- Markdown view: same filename with `.md` extension646566# 67# 68# Performance6970Use this skill when diagnosing or improving latency, throughput, resource usage, scalability, capacity, or performance regressions in a system.717273## Rules7475- Rule: define the target metric, workload, and measurement environment before interpreting results.76- Rule: separate latency percentiles, throughput, saturation, utilization, and error rate.77- Rule: compare baseline and changed behavior with the same workload.78- Rule: identify the limiting resource before prescribing changes.79- Rule: include regression checks so improvements do not silently degrade later.8081## Steps82831. Define user-visible target, SLO or benchmark, workload, and environment.842. Gather baseline measurements and instrumentation gaps.853. Build hypotheses about bottlenecks across CPU, memory, I/O, network, locks, and external services.864. Profile at the narrowest seam that can confirm or reject the hypothesis.875. Recommend remediation with trade-offs and expected impact.886. Define validation, regression checks, and rollout monitoring.8990## Completion9192- the skill's completion criteria are explicitly checked93- the artifact is saved and validated94- any blockers or skipped validations are documented95- the next consumer is identified or the work is handed off96---97@include .agents/skills/platform/contract-base.xml