CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/tcm-case-management

Test case management (TCM) across the five major platforms - TestRail, Xray, Zephyr Scale, Allure TestOps, and Qase - one tool-agnostic workflow for pre-execution case authoring and repository management: create and update cases, organise suites / sections / folders, attach structured steps, link cases to requirements, bulk import from CSV / JSON with idempotent re-runs, and sync from CI. The body works the workflow end to end against TestRail's API v2; references/ carries the per-vendor API specifics for all five tools. Use for test case management in any of the five TCMs. Not for posting test-run results - result sync is the qa-test-reporting plugin's surface.

76

Quality

96%

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

92%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 action-oriented, well-structured body with executable code, explicit batch-validation checkpoints, and clean one-level-deep reference routing. Its only weakness is mild verbosity and a duplicated 'test-management-sync' phrase that adds tokens without information.

Suggestions

Fix the repeated 'test-management-sync / test-management-sync / test-management-sync' string in the differentiation paragraph and References — name the actual surface once to save tokens and remove the apparent typo.

Tighten the Overview so it does not re-list the same seven workflow steps that the numbered list immediately below already enumerates.

Consider moving the TestRail enum/pagination response-shape detail (e.g. the 'Newer TestRail versions return {offset,limit,size,_links,cases}; older return a bare array' note) into references/testrail.md to keep the body a pure worked example.

DimensionReasoningScore

Conciseness

Mostly lean with executable code and tight rationale, but a few spots over-explain (e.g. the Overview restates the numbered workflow, and the differentiation paragraph repeats 'test-management-sync' three times) that could be trimmed. It is efficient but not fully stripped of padding, so it sits above the midpoint rather than at the top anchor.

4 / 5

Actionability

Copy-paste-ready, complete executable code throughout — auth setup, create_case with structured steps, runtime enum discovery, update/list pagination, a CSV bulk-import loop, and a CI sync YAML step — covering the common cases concretely.

5 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced and the batch operations carry explicit validation checkpoints with feedback loops: 'assert len(created) + len(skipped) equals the row count' and 'verify the repository case count matches the source count', so the batch-skill cap is satisfied.

5 / 5

Progressive Disclosure

A clear overview with a vendor routing table pointing to one-level-deep references (testrail.md, xray.md, zephyr-scale.md, allure-testops.md, qase-io.md — all present as real files), keeping per-vendor API deltas out of the body while the worked TestRail example stays inline.

5 / 5

Total

19

/

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.

A highly specific, third-person description that names concrete capabilities, natural trigger phrases, and a clear what/when boundary including a negative trigger. It is comprehensive without being padded and distinguishes itself cleanly from the sibling result-sync skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create and update cases, organise suites / sections / folders, attach structured steps with per-step expected results, link cases to requirements, bulk import from CSV / JSON with idempotent re-runs, and sync from CI' — giving comprehensive coverage rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both what (the enumerated authoring/repository actions) and when ('Use for test case management in any of the five TCMs - authoring cases from a spec, bulk-importing legacy cases, migrating between tools, or mass-editing a case repository'), plus a negative trigger ('Do NOT use for posting test-run results').

5 / 5

Trigger Term Quality

Covers natural terms users would say — 'test case management', 'authoring cases from a spec', 'bulk-importing legacy cases', 'migrating between tools', 'mass-editing a case repository' — plus all five named tool/platform strings as synonyms.

5 / 5

Distinctiveness Conflict Risk

A clear niche (pre-execution case repository management across five named TCMs) with an explicit boundary against the qa-test-reporting result-sync surface, leaving minimal overlap risk with sibling skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents