CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stand-api-test

Write, fix, or review HTTP contract tests in tests/stand/api/ — the deployed-stand suite against a real gateway, real Keycloak sessions and real backend images. Covers the operation catalogue, which persona session to take, requires_seed markers, the scratch-resource policy, the hand-written vs generated response models, status-code discipline (identity 404 vs analytics 403 outside a scope, 400 vs 415 vs 422) and the endpoint coverage gate. Use when adding or changing anything under tests/stand/api/, closing a coverage-gate gap, or turning a stand-scenarios claim into an API case. For browser journeys use stand-ui-test. Seeded-bronze → served-metric specs are the data-path suite in tests/datapath/ (metric-test).

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally dense, actionable body that reads as repo house law rather than tutorial prose: concrete fixtures, exact commands, explicit validation steps, and failure-mode guidance throughout. The only deductions are a few over-explained rationales and the absence of any reference-file split for tabular detail that would trim the inline token load.

Suggestions

Move the status-code discipline table, the caller-fixture table, and the Models section into a references/ file (e.g. references/status-codes.md, references/models.md) and keep one-line pointers in the body to reduce inline tokens and aid navigation.

Tighten the 401 rationale and the xfail-strict mechanics to the operative rules (e.g. 'never re-sweep 401 per operation — the gateway rejects before routing; one premise-check per module'), cutting the explanatory justification.

Add an explicit recovery step to the Procedure for the case where the coverage gate still reports gaps after reconcile (e.g. what to check in the observed ledger vs the catalogue template grouping).

DimensionReasoningScore

Conciseness

Nearly every section carries non-derivable house knowledge ("One module per path group, split by service", scratch policy, gate rules) and assumes Claude's competence, but passages like "A 401 alone proves nothing — the gateway rejects at the edge before routing, so a path that does not exist answers 401 too" and the xfail-strict mechanics run longer than the operative rule needs. This is noticeably above anchor 3 (only some unnecessary explanation) but not anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Fully executable throughout: exact fixture names (`admin_operator_session`, `session_for("dev_lead")`), a copy-paste assert line, and ready commands such as `./dev-compose.sh test-stand test --instance=worktree --tree=tests/stand/api/identity -k subchart` and `uv run --project tests --frozen python tests/generate_schemas.py --check`. Matches the 5 anchor's copy-paste-ready coverage of common cases.

5 / 5

Workflow Clarity

The 9-step Procedure is clearly sequenced with explicit validation checkpoints (run tests, ruff, schema drift `--check`, reconcile the coverage gate) plus error-recovery feedback loops: seed markers "Validated at collection time … aborts once naming every missing name", strict xfail that "retires itself", and leak diagnosis ("gets diagnosed as flakiness"). Not 4 — no meaningful checkpoint is missing.

5 / 5

Progressive Disclosure

Sections are well-organized and every cross-reference (insight-stand, stand-scenarios, metric-test, quality-vector-tests, repo paths) is one level deep and clearly signaled, but there is no bundle split at all — reference-grade material like the status-code table, the caller-fixture table, and the Models detail is inlined in a ~290-line body. Good structure with minor organization gaps fits anchor 4; anchor 5 would require that detail content actually live in separate referenced files.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a model of the form: concrete third-person actions, code-level specifics on status-code discipline and policy coverage, an explicit 'Use when…' clause with natural trigger phrases, and explicit redirects that fence it off from sibling skills. No vague or padded language; every clause either states a capability or a trigger.

DimensionReasoningScore

Specificity

"Write, fix, or review HTTP contract tests in tests/stand/api/" names multiple concrete actions and then comprehensively enumerates coverage: "the operation catalogue", "requires_seed markers", "the scratch-resource policy", "status-code discipline (identity 404 vs analytics 403 outside a scope, 400 vs 415 vs 422)", "the endpoint coverage gate". Comprehensive with code-level specifics matches the 5 anchor; 4 would require minor coverage gaps, which are absent.

5 / 5

Completeness

Both halves are explicit: the what ("Write, fix, or review HTTP contract tests … Covers the operation catalogue, which persona session to take, …") and the when ("Use when adding or changing anything under tests/stand/api/, closing a coverage-gate gap, or turning a stand-scenarios claim into an API case"). This mirrors the 5 anchor's concrete-trigger example exactly; 4 would mean a less explicit when-clause.

5 / 5

Trigger Term Quality

"Use when adding or changing anything under tests/stand/api/, closing a coverage-gate gap, or turning a stand-scenarios claim into an API case" gives natural trigger phrases a user of this repo would actually say, with domain synonyms (contract tests, stand, coverage gate, API case) covering the 5 anchor's comprehensiveness including variations.

5 / 5

Distinctiveness Conflict Risk

The skill is pinned to a single directory (tests/stand/api/) and actively disambiguates neighboring skills: "For browser journeys use stand-ui-test" and "Seeded-bronze → served-metric specs are the data-path suite in tests/datapath/ (metric-test)". A clear niche with explicit redirects gives minimal conflict risk, matching the 5 anchor.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

constructorfabric/insight

Path

.claude/skills/stand-api-test/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.