CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

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

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 CLI skill body with executable examples and sensible validation cues. Tightening a few prose lines and externalizing more reference material into bundle files would lift conciseness and progressive disclosure toward 5.

DimensionReasoningScore

Conciseness

Mostly lean and command-driven with little concept over-explanation, but a few prose lines (e.g. 'Default to saved dashboard tests...' and the Local Prompt caveat) could be trimmed further.

4 / 5

Actionability

Fully executable, copy-paste ready bash commands with concrete JSON payloads across creation, update, grouping, runs, and CI cover the common cases comprehensively.

5 / 5

Workflow Clarity

Clear sectioned sequence from Setup through Runs with an 'Inspect before changing' checkpoint and coverage-claim guardrail; minor gap is the absence of an explicit failed-run retry/feedback loop.

4 / 5

Progressive Disclosure

Well-organized sections with one clearly-signaled one-level-deep reference (reporting-template.md in the References table), though most reference-style material stays inline rather than being split into separate files.

4 / 5

Total

17

/

20

Passed

Description

87%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, third-person description that clearly states capabilities and explicit trigger conditions with low conflict risk. It could nudge specificity toward 5 by replacing the abstract 'organize' with more concrete actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('create, organize, and run dashboard-managed QA tests', 'saved tests, groups, project context, credentials, and remote runs'), but 'organize' is somewhat abstract, leaving minor coverage gaps versus a comprehensive 5.

4 / 5

Completeness

Explicitly answers both what ('Use TesterArmy CLI to create, organize, and run dashboard-managed QA tests') and when ('Trigger when defining regression coverage, adding QA flows, or wiring CI checks') with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Trigger when defining regression coverage, adding QA flows, or wiring CI checks' gives good natural-term coverage a user would say, though a few synonyms or CLI-name variants are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped to the TesterArmy CLI with distinct QA/regression/CI triggers, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
novuhq/novu
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.