CtrlK
BlogDocsLog inGet started
Tessl Logo

pricefy

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

48

Quality

52%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

58%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 largely actionable with concrete Membrane CLI commands and reasonable section organization, but it over-explains background context, presents the multi-step connection workflow as prose rather than a numbered sequence with validation checkpoints, and has no external reference files.

Suggestions

Cut the introductory paragraph about what Pricefy is and who uses it; Claude does not need this context.

Reframe the install → login → ensure connection → wait/poll → search → run flow as an explicit numbered checklist with a validate checkpoint after polling (e.g. 'Only proceed to action calls once state is READY').

Consolidate the two `membrane action list` invocations (lines 103 and 112) into one canonical example to reduce redundancy.

DimensionReasoningScore

Conciseness

Mostly efficient with executable CLI snippets, but it includes explanations Claude already knows (what Pricefy is, who uses it) and lightly padded prose around the proxy/connection sections that could be trimmed.

3 / 5

Actionability

Concrete, copy-pasteable `membrane` commands are provided for install, login, connection, action search/run, and proxy requests with documented flags; minor gaps such as placeholder CONNECTION_ID handling keep it just below 5.

4 / 5

Workflow Clarity

There is a recognizable sequence (install → authenticate → connect → search actions → run), but it is not presented as an ordered list and lacks an explicit validate-before-proceed checkpoint for the async connection build, so the validation cap applies.

3 / 5

Progressive Disclosure

Content is well-organized into overview, authentication, connecting, searching, running, proxy, and best-practices sections with no nested external references and no bundle files to manage; minor structure gaps (e.g. the loose '1b' substep) keep it from 5.

4 / 5

Total

14

/

20

Passed

Description

46%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 identifies the target service and includes a 'Use when' clause, but the capability language is generic ('Manage data, records, and automate workflows') and lacks concrete PRICEFY.IO-specific actions and richer trigger keywords. It is distinct yet somewhat under-specified.

Suggestions

Replace generic verbs with concrete PRICEFY.IO actions, e.g. 'Import product catalogs, compare competitor prices, sync pricing rules'.

Add natural trigger phrases and synonyms such as 'pricing', 'competitor prices', and 'price monitoring' alongside 'PRICEFY.IO'.

Expand the 'Use when' clause with specific scenarios, e.g. 'Use when the user asks to compare prices, import catalogs, or automate PRICEFY.IO workflows'.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the integration domain but the actions are generic; no concrete PRICEFY.IO-specific operations (e.g. compare prices, import catalogs, sync competitor pricing) are enumerated.

2 / 5

Completeness

There is a clear-enough 'what' (PRICEFY.IO integration for data, records, workflow automation) and an explicit 'when' ("Use when the user wants to interact with PRICEFY.IO data"), but the trigger clause is thin and lacks concrete trigger phrases, capping completeness at 3.

3 / 5

Trigger Term Quality

It surfaces the natural keyword "PRICEFY.IO" but offers no synonyms, file extensions, or common user phrases like "pricing" or "competitor prices" to broaden triggering.

3 / 5

Distinctiveness Conflict Risk

Tying the skill explicitly to "PRICEFY.IO" gives it a clear niche with minimal overlap risk against other skills; only minor generality in 'manage data, records, automate workflows' keeps it from 5.

4 / 5

Total

12

/

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.