testerarmy-cli

Use TesterArmy CLI to create, organize, and run dashboard-managed QA tests. Prefer saved tests, groups, project context, credentials, and remote runs over one-off local prompts. Trigger when defining regression coverage, adding QA flows, or wiring CI checks.

Quality

93%

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

87%

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

The content is concise, highly actionable, and well-structured with appropriate progressive disclosure. Its main weakness is workflow clarity, where validation checkpoints exist but are not framed as explicit error-recovery feedback loops for batch and destructive operations.

Suggestions

Add an explicit validate-then-fix feedback loop for test/group runs (e.g., after `ta tests run --remote --wait`, on FAILED: read the failure, update steps via `ta tests update`, and re-run) so batch and destructive operations recover rather than just report.

Number the core authoring workflow as an ordered sequence (check auth -> create/inspect project -> create credentials -> create test -> group it -> remote-validate) so the intended end-to-end path is unambiguous rather than implied by section order.

Frame the existing checkpoints explicitly as verification gates (e.g., a short checklist: run `ta status --json` before anything; `ta tests get <testId>` before update; claim durable coverage only after `ta tests create/update` succeeds).

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with brief rules, assumes Claude's competence, and avoids explaining concepts Claude already knows.	3 / 3
Actionability	It provides fully executable, copy-paste-ready `ta` commands with complete JSON payloads and explicit flag semantics.	3 / 3
Workflow Clarity	The body is organized as a topical reference with some checkpoints ("Inspect before changing", `--wait`, `ta status`), but it lacks explicit error-recovery feedback loops (validate -> fix -> retry) for batch and destructive operations like group runs and test updates.	2 / 3
Progressive Disclosure	Well-organized sections keep the overview inline while the reporting detail is split into a single real one-level reference (references/reporting-template.md) signaled via a References table.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 concise, specific, and clearly answers both what the skill does and when to trigger it using natural user terms. It occupies a distinct niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	"create, organize, and run dashboard-managed QA tests" plus "saved tests, groups, project context, credentials, and remote runs" list multiple specific concrete actions rather than vague language.	3 / 3
Completeness	It states both what the skill does ("create, organize, and run dashboard-managed QA tests") and when to use it ("Trigger when defining regression coverage, adding QA flows, or wiring CI checks").	3 / 3
Trigger Term Quality	"defining regression coverage", "adding QA flows", and "wiring CI checks" are natural terms a QA-focused user would actually say when they need this skill.	3 / 3
Distinctiveness Conflict Risk	The TesterArmy CLI niche with distinct QA/CI/regression triggers is unlikely to overlap with or fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: novuhq/novu
Path: .agents/skills/testerarmy-cli/SKILL.md
Commit: 67de0fa

Reviewed: about 14 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.