Name: testmo
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

testmo

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

Quality

70%

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

Fix and improve this skill with Tessl

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

Quality

Content

75%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 with executable CLI commands and a sensible workflow that includes a polling feedback loop, but it carries an unnecessary intro paragraph and a vague overview section that dilute conciseness. Structure is good but monolithic.

Suggestions

Remove or trim the opening "Testmo is a test management tool..." paragraph and the bare entity-list overview, which explain concepts Claude can infer or that add no actionable detail.

Label the workflow steps explicitly (Step 1 connect, Step 2 search, Step 3 run) so the "skip to Step 2" reference resolves, and add a verification step after running actions.

Replace the vague "Use action names and parameters as needed" line with a concrete pointer to the action search command.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-focused content, but it opens with an unnecessary paragraph explaining what Testmo is ("Testmo is a test management tool used by software development teams...") and a vague entity-list overview ("Use action names and parameters as needed"), matching anchor 3.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands across install, auth, connection, action search/run, and proxy use, plus a concrete flag table, covering the common cases and matching anchor 5.	5 / 5
Workflow Clarity	A clear sequence runs install → authenticate → connect → poll for readiness → search → run actions, with an explicit polling feedback loop over connection states (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR); minor gaps are the unlabeled "Step 2" reference and no validation checkpoint after running actions, matching anchor 4.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no unnecessary external file references, but as a single ~157-line file it does not split content into one-level-deep references, fitting anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

66%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 is well-targeted to a distinct niche (Testmo) and answers both what and when, but its action list and trigger phrasing are generic rather than concrete test-management terms. Tightening the actions and adding natural synonyms would raise the score.

Suggestions

Replace generic verbs with concrete Testmo actions, e.g. "create test runs, log test results, manage test cases and projects".

Expand the trigger clause to include natural user phrasings: "Use when the user wants to manage tests in Testmo, log test results, or work with test runs and cases."

Add file/term synonyms users say, such as "test management", "test runs", or "test results", to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Testmo integration") and enumerates action categories ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete test-management verbs like creating test runs or logging results, fitting anchor 3 over anchor 2 because multiple categories are listed.	3 / 5
Completeness	Answers both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Testmo data"), but the "when" trigger is somewhat generic and could be more explicit, matching anchor 4 rather than 5.	4 / 5
Trigger Term Quality	Includes the core keyword "Testmo" and the phrase "interact with Testmo data", but misses common natural variations a user would say such as "test management", "test runs", "test cases", or "test results", matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	Targets a clearly named niche tool (Testmo) with a distinct trigger ("interact with Testmo data"), giving it minimal overlap risk with other skills, matching anchor 5.	5 / 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/testmo/SKILL.md
Commit: f484c82

Reviewed: 4 days 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.