CtrlK
BlogDocsLog inGet started
Tessl Logo

percy

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

56

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/percy/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is a well-structured, executable guide to driving Percy through the Membrane CLI, with concrete commands, a clear connect-and-act workflow, and explicit state checkpoints. It is held back from top marks by mild introductory verbosity and a Popular actions section that discovers rather than demonstrates.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete CLI commands and a flags table, but the opening "Percy is a visual testing platform..." paragraph and some restated guidance add mild over-explanation that could be trimmed, fitting the efficient-with-minor-trimmables anchor.

4 / 5

Actionability

Concrete, copy-paste-ready membrane commands are provided for install, login, connection ensure, polling, action list/run, and proxy requests; it falls short of 5 only because the Popular actions section stays at discovery level without a worked example of running a common action.

4 / 5

Workflow Clarity

The connect -> wait-for-READY -> search -> run flow is clearly sequenced with explicit state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling guidance, missing a 5 only because error-recovery feedback loops are described rather than enforced as explicit validate-then-retry steps.

4 / 5

Progressive Disclosure

As a single self-contained file with no bundle directories, it is well organized under clear headers (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with one-level structure and no nested references, meeting the good-structure anchor; it is not a 5 only because no detailed material is split out, which is acceptable but not exemplary.

4 / 5

Total

16

/

20

Passed

Description

53%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 correctly identifies the Percy niche and includes a Use-when clause, but its capabilities are stated generically (manage data, automate workflows) rather than as concrete visual-testing actions, and the trigger term coverage is thin.

Suggestions

Replace generic verbs with concrete Percy operations, e.g. "Compare visual snapshots across builds, review visual diffs, and manage Percy projects and builds."

Expand the trigger clause with natural phrases users say: "Use when the user mentions visual testing, visual regression, screenshot comparisons, Percy snapshots, or UI diff reviews."

Keep third person but make the what/when pairing explicit and specific rather than the current one-sentence catch-all.

DimensionReasoningScore

Specificity

Names the domain (Percy) and gestures at actions via "Manage data, records, and automate workflows," but those actions are generic rather than concrete Percy operations (snapshots, comparisons, builds), matching the anchor for domain plus 1-2 vague actions.

3 / 5

Completeness

It states a what ("Manage data, records, and automate workflows") and a when ("Use when the user wants to interact with Percy data"), but the when is generic and the what is vague, falling short of the explicit concrete trigger phrases required for a 4 or 5.

3 / 5

Trigger Term Quality

The only trigger is "Use when the user wants to interact with Percy data"; it misses the natural terms a user would actually say such as visual testing, screenshots, visual regression, or builds, so keyword coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

"Percy integration" carves out a clear niche that is unlikely to trigger for the wrong skill, with only minor overlap risk against a general data-management skill.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.