CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/tcm-case-management

Use for any question or task about managing test cases in TestRail, Xray, Zephyr Scale, Allure TestOps or Qase, including organizing suites, importing cases from CSV or JSON, linking them to requirements and migrating between tools without losing steps: writing cases from a spec, steps with expected results and mass edits. Pushing run results is test-management-sync.

Quality

91%

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

Overview
Quality
Evals
Security
Files

Quality

Content

81%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 strong, workflow-driven body: fully executable TestRail code with genuine idempotency and verification loops, and a clean routing table that delegates vendor deltas to real, shallow reference files. The main deductions are repeated framing material (the Cloudflare note and result-sync disambiguation each stated multiple times) and the CI-sync step pointing at scripts that are not part of the bundle.

Suggestions

State the Cloudflare/docs limitation once (Limitations is the natural home) and drop the repetitions in the workflow intro and References section; likewise deduplicate the result-sync boundary note and fix the 'test-management-sync / test-management-sync / test-management-sync' triple repetition to name the actual sibling skills once.

Either add the referenced sync scripts (scripts/sync-testrail.py, sync-qase.py, sync-zephyr-scale.py) to the bundle or reframe Step 6 as an illustrative pattern with inline sync-script skeleton code so nothing implies a file that does not exist.

Give sibling references (test-case-anatomy-reference, tcm-migration-agent, test-case-quality-critic, traceability-matrix-builder) resolvable paths or a short 'where to find them' note instead of bare names.

DimensionReasoningScore

Conciseness

The body is dominated by dense, executable code with minimal framing prose and assumes competence (no explaining what HTTP Basic or REST is), matching 'efficient; minor instances of over-explanation'. Not 5 because of genuine repetition: the Cloudflare caveat appears three times (workflow intro, Limitations, References) and the result-sync disambiguation is duplicated — including a literal triple repetition, 'test-management-sync / test-management-sync / test-management-sync' — that could be trimmed. Not 3 because the core Steps 1–6 contain essentially no wasted tokens.

4 / 5

Actionability

Steps 1–5 are copy-paste ready: complete auth helper, create_case with documented enum semantics, runtime enum discovery, dual-shape pagination, and an idempotent CSV import loop. Not 5 because Step 6's CI example runs 'python scripts/sync-testrail.py', which is not in the bundle (no scripts/ directory exists), leaving the sync step as direction rather than executable guidance — a minor gap matching anchor 4 rather than anchor 5's 'specific examples cover the common cases'.

4 / 5

Workflow Clarity

The 7-step sequence is numbered, ordered, and each step carries code; the batch import has an explicit validate-fix-retry loop ('assert len(created) + len(skipped) equals the row count... inspect it, fix the source row, and re-run') and 429 back-off guidance, and CI sync has its own count verification ('a mismatch means a silent partial sync'). This matches anchor 5's 'explicit validation steps; feedback loops for error recovery' and satisfies the batch-operation validation requirement, so no cap applies.

5 / 5

Progressive Disclosure

Good structure: an overview plus a vendor routing table cleanly pushes per-vendor deltas to five reference files that all exist and are one level deep (no further nesting found), and a References section lists them explicitly. Not 5 because of minor organization gaps: the body and two references invoke scripts/sync-*.py files that are not bundled, and sibling skills are named without paths, leaving a few dangling implied references — anchor 4's 'minor organization gaps'.

4 / 5

Total

17

/

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.

An exemplary description: concrete action list, explicit trigger clause, all five vendor names as natural keywords, and an explicit disambiguation boundary against the sibling result-sync skill. Every dimension sits squarely on its anchor-5 example.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'organizing suites, importing cases from CSV or JSON, linking them to requirements and migrating between tools without losing steps: writing cases from a spec, steps with expected results and mass edits' — giving comprehensive coverage of the case-management domain. This matches the anchor-5 example ('Extract text and tables... fill forms, merge documents') in both breadth and concreteness, and exceeds anchor 4, which allows coverage gaps.

5 / 5

Completeness

It explicitly answers both questions: 'Use for any question or task about managing test cases in...' is a clear when-clause, and the enumerated actions answer what, mirroring the anchor-5 example structure ('...Use when working with PDF files or when the user mentions PDFs...'). A 4 would require the when-clause to be less explicit, but 'Use for any question or task about' is as explicit as the good examples.

5 / 5

Trigger Term Quality

Natural trigger terms are comprehensive: all five product names users would actually say ('TestRail, Xray, Zephyr Scale, Allure TestOps or Qase') plus 'managing test cases', 'importing cases from CSV or JSON', 'migrating between tools', 'mass edits', and 'writing cases from a spec'. Not below 5 because no commonly used phrasing for this domain is missing; not above because 5 is the scale maximum.

5 / 5

Distinctiveness Conflict Risk

A clear niche (the pre-execution case repository in five named TCM tools) with an explicit boundary — 'Pushing run results is test-management-sync' — that actively routes the adjacent result-sync use case elsewhere. Conflict risk with unrelated skills is minimal, matching the anchor-5 'clear niche with distinct triggers'.

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page