Name: assertible
Rating: 48 (1 reviews)
Author: membranedev

assertible

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

Quality

51%

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/assertible/SKILL.md

Quality

Content

61%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 a solid, executable CLI reference with a well-structured connection workflow including state-based validation checkpoints, but it leads with unnecessary background explanation of what Assertible is and keeps all detail inline rather than using a references bundle for the longer API/state material.

Suggestions

Cut the introductory paragraph explaining what Assertible and QA teams do; Claude already knows this and it competes with context.

Move the clientAction state taxonomy and/or the proxy flag table into a references/ file and point to it from SKILL.md to improve progressive disclosure.

Add a brief verification step after running an action (e.g. check the output field for errors) to give the action-running workflow the same validation rigor as connection setup.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command references, but the opening 'Assertible is a web service for automated API testing and monitoring. Developers and QA teams use it to continuously validate the reliability of their APIs...' explains background Claude already knows, and several prose blocks around connection states repeat what the flags convey.	3 / 5
Actionability	Concrete, copy-pasteable CLI commands are given throughout (install, login, connection ensure, action list/run, request proxy) with the --json flag and parameter syntax, leaving only minor gaps such as how to obtain CONNECTION_ID programmatically.	4 / 5
Workflow Clarity	The connection setup is sequenced with a polling loop (--wait) and explicit state checks (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with recovery guidance, satisfying the validation-checkpoint bar; minor gaps exist in the action-running path, which lacks an equivalent verify step.	4 / 5
Progressive Disclosure	No references/scripts/assets bundle exists and the file is a single ~140-line document with clear section headers, but content that could be split out (the full clientAction state taxonomy and the proxy flag table) is inlined rather than referenced, and there are no one-level-deep pointers to organize the material.	3 / 5
	Total	14 / 20 Passed

Description

41%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 anchors on the distinct proper noun 'Assertible' but pads it with generic capability verbs (manage data, records, automate workflows) that under-describe the skill's API-testing and monitoring purpose. It clears the basic what/when bar but lacks concrete, natural trigger phrases.

Suggestions

Replace generic verbs with Assertible-specific actions, e.g. 'Run API assertions, schedule API tests, and monitor web service reliability.'

Add concrete trigger phrases to the 'Use when' clause, e.g. 'Use when the user wants to test or monitor an API, run assertions, or check web service reliability with Assertible.'

Drop the vague 'Manage data, records' phrasing, which inflates scope and dilutes distinctiveness.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain but uses minimal, generic actions rather than concrete operations on Assertible's API-testing surface (e.g. run assertions, monitor endpoints, manage schedules).	2 / 5
Completeness	A clear 'what' is present ("Assertible integration. Manage data, records, and automate workflows") and a 'Use when' clause exists ("Use when the user wants to interact with Assertible data"), but the 'when' is broad and lacks concrete trigger phrases, so it is not fully explicit.	3 / 5
Trigger Term Quality	Aside from the proper noun "Assertible", the only keywords are generic ("data, records, automate workflows"); natural user phrases like "API testing", "test my API", "monitoring", or "assertions" are absent.	2 / 5
Distinctiveness Conflict Risk	The proper noun "Assertible" plus "integration" carves a clear, narrow niche with minimal overlap risk against other skills; the only weakness is the generic remainder of the sentence.	4 / 5
	Total	11 / 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/assertible/SKILL.md
Commit: f484c82

Reviewed: 3 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.