Name: testrail
Rating: 64 (1 reviews)
Author: membranedev

testrail

TestRail integration. Manage data, records, and automate workflows. Use when the user wants to interact with TestRail data.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/testrail/SKILL.md

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.

The body is highly actionable, packed with executable Membrane CLI commands and a clear connection workflow with state checkpoints and a feedback loop. It is well-organized and mostly concise, with only minor padding and a loosely-numbered overall flow.

Dimension	Reasoning	Score
Conciseness	The body is dominated by concrete, copy-pasteable commands with flag tables, and is mostly efficient; only minor marketing/padding lines ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens') could be trimmed, matching 'efficient; minor instances of over-explanation'. Not 5 due to those few padded sentences.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands across install, login, connection, action search/run, and proxy requests, with a complete flag table, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'. Parameter placeholders like CONNECTION_ID are legitimate, not pseudocode.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, matching 'clear sequence with most checkpoints present; minor validation gaps'. Not 5 because the 'skip to Step 2' reference points to no explicit Step 2 header, leaving the overall connect→search→run flow slightly loosely stitched.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Working with TestRail, Install, Auth, Connecting, Searching, Running, Proxy, Best practices) in a single file with no nested references, matching 'good structure; most content is appropriately placed; minor organization gaps'. Not 5 because, at ~150 lines, some reference-style content (entity list, proxy flags) is inlined rather than split into one-level-deep reference files.	4 / 5
	Total	17 / 20 Passed

Description

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

The description clearly names TestRail and provides both a 'what' and a 'when' clause, with the product name serving as a strong natural trigger. Its main weakness is generic action verbs ('manage data, records, automate workflows') that lack concrete, TestRail-specific operations.

Suggestions

Replace generic verbs with concrete TestRail actions, e.g., 'create and manage test cases, runs, milestones, and plans; log test results and generate reports'.

Expand the 'when' clause with concrete trigger phrases and synonyms users say, e.g., 'Use when the user mentions TestRail, test runs, test cases, QA reporting, or test management.'

Mention key TestRail entities (cases, runs, suites, milestones) in the description to sharpen distinctiveness from generic integration skills.

Dimension	Reasoning	Score
Specificity	Names the domain (TestRail) and several action categories ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete operations, fitting 'names domain and 1-2 concrete actions but not comprehensive'. It does not reach 4 because no specific concrete actions (e.g., 'create test runs', 'log results') are listed.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with TestRail data') are present, matching 'has both what and when; when could be more explicit or specific'. Not 5 because the trigger phrasing lacks concrete synonyms.	4 / 5
Trigger Term Quality	The product name 'TestRail' plus 'interact with TestRail data' gives good natural keyword coverage a user would actually say, but common variations or file extensions are absent, matching 'good keyword coverage; a few natural terms missing'. Not 5 because synonyms/extensions are missing.	4 / 5
Distinctiveness Conflict Risk	The 'TestRail' product name gives a clear niche with minimal conflict risk, but the generic action language ('manage data, records, automate workflows') could overlap with other integration skills, matching 'mostly distinct; minor overlap risk'. Not 5 because the verbs are not uniquely TestRail-specific.	4 / 5
	Total	15 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/testrail/SKILL.md
Commit: f484c82

Reviewed: ~23 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.