api-performance-validation
/api-performance-validation
Build AgentWorks API performance validation with authorized bounded load, customer-defined budgets, comparable samples, and durable diagnostics. Use for latency, throughput, error-rate, or capacity regression checks.
- Author
- manishiitg ↗
- Repository
- agentworks ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Build AgentWorks API performance validation with authorized bounded load, customer-defined budgets, comparable samples, and durable diagnostics. Use for latency, throughput, error-rate, or capacity regression checks.
Original author description
Build AgentWorks API performance validation with authorized bounded load, customer-defined budgets, comparable samples, and durable diagnostics. Use for latency, throughput, error-rate, or capacity regression checks.
How it works
- Outcome
- When to use
- Discovery and user direction
- Required inputs
- Plan and AgentWorks tools
- Knowledge and persistence
- Validation and reporting
- Guardrails
- Read details when needed
- Completion contract
SKILL.md preview
--- name: api-performance-validation description: Build AgentWorks API performance validation with authorized bounded load, customer-defined budgets, comparable samples, and durable diagnostics. Use for latency, throughput, error-rate, or capacity regression checks. --- # API Performance Validation ## Outcome Create a repeatable API performance workflow that exercises approved scenarios under bounded load, evaluates customer budgets, preserves comparable samples, and reports supported latency, throughput, reliability, and capacity findings. ## When to use Use for service-level performance baselines, regressions, release checks, or controlled capacity experiments. Require explicit authorization before meaningful load; production is never assumed to be an acceptable target. ## Discovery and user direction Inspect the current workflow, goals, metrics, configuration, capabilities, stores, reports, and triggers before proposing changes. Summarize reusable design and gaps, then ask focused questions for unresolved customer choices such as scope, success, approvals, thresholds, ownership, and budgets. Record the answers as customer direction. Installation alone does not approve workflow changes or execution. Default to one small-team workflow; split only for incompatible access or lifecycle boundaries. ## Required inputs Resolve endpoints and protocol, environment/build, authentication and secret references, scenarios/payload classes, test-data cleanup, load shape, worker location, connection behavior, sample duration, budgets/baseline, stop limits, observability access, evidence retention, and owner. ## Plan and AgentWorks tools Use scripted steps for preflight, the saved load runner, deterministic parsing, aggregation, persistence, and policy decisions. Use a message sequence to correlate supported regressions with metrics/traces. Persist high-load or state-changing proposals for durable review, end preparation, and let a separate execution route validate the saved approval and exact target before sending traffic. ## Knowledge and persistence Store policies, profiles, scenarios, runs, samples, aggregates, errors, and findings in durable tables. Store sanitized runner output, request summaries, traces, and profiles in durable assets. Keep secret values and unrestricted bodies out of artifacts; add only verified non-sensitive service facts to KB notes. ## Validation and reporting Require exact target/build/profile identity, planned sample completeness, functional response checks, error accounting, and valid measurements. The dashboard shows latency distribution, throughput, error rate, concurrency/rate, saturation, and budget status, with filters for route/profile/build/environment and drill-down to samples, errors, traces, history, and limitations. Partial or incomparable runs cannot pass. ## Guardrails Do not load-test production by assumption, exceed approved rate/concurrency/duration, create uncontrolled data, ignore rate-limit signals, hide errors through averages, change budgets after observing results, or claim server capacity from client latency alone. ## Read details when needed - [Workflow design and outcomes](../../references/workflow-design-and-outcomes.md): goals, metrics, and current-versus-separate workflow decisions. - [Performance measurement](../references/performance-measurement.md): shared provenance, sampling, budgets, and reporting. - [API performance workflow](references/api-performance-workflow.md): scenarios, plan, safety, storage, and acceptance cases. - [Example policy](examples/api-performance-policy.json): fictional measurement and load shape. - [Catalog metadata](playbook.json): presentation and optional recommendations. ## Completion contract Return installed playbook and policy/profile revisions, exact target/build, authorized load shape, customer overrides, planned/completed samples, functional and budget decisions, findings, evidence/report locations, capability resolution, and limitations.
Files in this package (4)
- SKILL.md 4 KB
- playbook.json 4 KB
- examples/api-performance-policy.json 1 KB
- references/api-performance-workflow.md 4 KB
Versions
The database has no other skills named api-performance-validation.
Database snapshot: 13.11.2026 · package version f54f8c02377d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100browser-performance-validation
Build repeatable AgentWorks browser performance validation with customer-defined budgets and comparable samples. Use for page, journey, Web Vital, resource, or timing regressions. - 100review-performance
Review code changes for performance, resource use, scale assumptions, benchmarks, and latency or throughput regressions. Use for /review-performance. - 100performance-capacity
Plan, diagnose, and verify performance budgets, latency targets, load tests, capacity estimates, bottleneck analysis, caching strategy, query efficiency, queue throughput, and regression gates. Use when a feature may be slow, a system must scale, a performance regression is… - 100authentication-session-validation
Build repeatable AgentWorks browser validation for authentication and session behavior. Use for login, logout, MFA, recovery, expiry, refresh, and invalid-session coverage after browser setup. - 100performance-engineer
Guides performance engineering—profiling (CPU, memory, I/O), distributed tracing, latency and throughput analysis, load/soak/stress testing, capacity models, performance budgets, database query tuning, and regression detection in CI. Use when investigating slow endpoints, p99… - 100performance-investigation
Diagnose a measured latency, memory, throughput, or resource regression and propose the smallest supported optimization. Use for performance questions; measure before tuning.