backend-tests

Run backend tests and code quality checks for OPRE OPS. Covers ops_api pytest, data_tools pytest, and nox linting/formatting sessions. Use this skill when the user wants to run backend tests, check code quality, lint Python code, run pytest, or verify their backend changes pass CI checks — even if they just say "run the tests" or "does this pass".

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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.

A highly actionable, well-structured operational skill: every command is executable and the argument dispatch is unambiguous. Weakest points are mild cross-section redundancy and a missing Docker pre-flight step inside the full CI workflow.

Suggestions

Add the Docker pre-flight check (docker info) to step 4 of the `all`/CI workflow before running data_tools tests, since the skill itself documents that these tests hang without Docker.

Deduplicate the repeated cd/pipenv/pytest invocations across the api, data-tools, and test-path sections, e.g., by stating the common command shape once and varying only the directory and test target.

Consider moving the default help text and Common Issues section into a reference file to slim the always-loaded SKILL.md body.

Dimension	Reasoning	Score
Conciseness	Efficient and assumes competence — no concept explanations, just commands and project-specific facts. Minor trimming opportunities: the "pipenv run pytest" / "-v --tb=short" pair and "cd backend/..." repeat across sections, and the default help block restates all commands. Not 5 because not every token earns its place; well above the unnecessary-explanation anchor at 3.	4 / 5
Actionability	Every branch (api, data-tools, lint, format, test-path, all, default) has copy-paste-ready executable commands, plus concrete routing rules ("If it contains `data_tools` or `load_` -> run in `backend/data_tools/`"). Fully executable and covers the common cases.	5 / 5
Workflow Clarity	Clear 7-branch dispatch on $ARGUMENTS with a Docker pre-flight check, a reporting spec, a final CI summary checklist, and a troubleshooting section. Not 5: the `all`/CI workflow omits the Docker pre-flight before data_tools tests even though the hanging-on-no-Docker failure is documented in Common Issues, and workflows lack an explicit validate→fix→retry loop.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-sectioned with a clear command-dispatch structure. Minor gap rather than a 5: at ~205 lines, content like the default help text and Common Issues could move to a reference file to keep the overview lean.	4 / 5
	Total	17 / 20 Passed

Description

92%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.

A strong description: it states concrete capabilities, gives an explicit and detailed trigger clause including colloquial variants, and is tightly scoped to this project's backend. Only minor gains available from adding a few more natural synonyms.

Dimension	Reasoning	Score
Specificity	"Run backend tests and code quality checks", "ops_api pytest, data_tools pytest, and nox linting/formatting sessions" lists multiple specific concrete actions with comprehensive coverage of the skill's domain. Score 4 allows minor coverage gaps, but none are material here.	5 / 5
Completeness	Explicitly answers both: what ("Run backend tests and code quality checks for OPRE OPS. Covers ops_api pytest, data_tools pytest, and nox linting/formatting sessions.") and when ("Use this skill when the user wants to run backend tests... — even if they just say 'run the tests' or 'does this pass'") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-phrase coverage: "run backend tests", "lint Python code", "run pytest", "pass CI checks", plus colloquial "run the tests" and "does this pass". A few common variations (e.g., "unit tests", "test suite") are missing, so it falls short of the comprehensive-synonym anchor at 5 but is clearly above the missing-variations anchor at 3.	4 / 5
Distinctiveness Conflict Risk	Scoped to the OPRE OPS backend with distinct pytest/nox/CI triggers and an explicit claim to generic phrases like "run the tests" — a clear niche with minimal conflict risk with frontend or general skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: HHS/OPRE-OPS
Path: .claude/skills/backend-tests/SKILL.md
Commit: b61c72b

Reviewed: 19 hours ago

Table of Contents

Discovery Implementation Validation

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.