CtrlK
BlogDocsLog inGet started
Tessl Logo

crezco

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

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

67%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 well-structured, actionable CLI integration guide with strong workflow sequencing and validation feedback loops, held back slightly by redundancy and minor over-explanation.

Suggestions

Remove the redundant "Popular actions" section that repeats the action-list command already shown in "Searching for actions", or replace it with concrete Crezco-specific action examples.

Fix the duplicated "Crezco Overview" bullet list (Counterparty appears twice) or replace it with the actual Crezco action categories.

Trim mild over-explanation such as "so you can focus on the integration logic rather than auth plumbing" to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient command documentation, but it repeats the `membrane action list` command in both "Searching for actions" and "Popular actions", and the duplicated "Crezco Overview" bullet list adds little value, so it could be tightened.

3 / 5

Actionability

It provides concrete, copy-paste-ready commands (login, connection ensure, action run, request proxy) with a full flag table, with only minor gaps such as generic action discovery rather than Crezco-specific action examples.

4 / 5

Workflow Clarity

A clear sequence runs install → authenticate → connect → poll for READY → search → run, with an explicit connection-state feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and re-polling after user action, missing only final post-run validation.

4 / 5

Progressive Disclosure

The single-file guide is well-organized into clear sections with no nested or buried references; given there are no bundle files, the content is appropriately placed with only minor organization gaps like the redundant Popular actions section.

4 / 5

Total

15

/

20

Passed

Description

57%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 Crezco niche and includes an explicit use-when clause, but its stated capabilities are vague and the trigger phrasing is generic rather than rich with natural keywords.

Suggestions

Replace vague actions ("Manage data, records, and automate workflows") with concrete Crezco capabilities such as initiating invoice payments, managing counterparties, and reconciling transactions.

Enrich the trigger clause with natural user phrases and synonyms, e.g. "Use when the user wants to pay invoices, set up counterparties, or reconcile payments via Crezco."

Mention the primary users or context (accounting/finance teams) only if it sharpens distinctiveness without adding fluff.

DimensionReasoningScore

Specificity

Quotes "Manage data, records, and automate workflows" name the Crezco domain but the actions are minimal and generic ("manage data", "automate workflows") rather than concrete capabilities like invoice payments or reconciliation.

2 / 5

Completeness

It states both a "what" ("Crezco integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Crezco data"), but the trigger could be more concrete, so it stops short of a 5.

4 / 5

Trigger Term Quality

The phrase "Use when the user wants to interact with Crezco data" surfaces a few relevant keywords (Crezco, data, records, workflows) but misses natural synonyms or variations a user would actually say.

3 / 5

Distinctiveness Conflict Risk

Naming the specific platform "Crezco" carves out a clear niche with low conflict risk, but the generic trigger phrasing ("interact with Crezco data") keeps it just below the distinct-trigger bar of a 5.

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.