CtrlK
BlogDocsLog inGet started
Tessl Logo

chipax

Chipax integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chipax 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/chipax/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 largely executable, well-sectioned guide to driving Chipax through the Membrane CLI with decent validation checkpoints around connection state. It would benefit from trimming explanatory prose and resolving the dangling 'Step 2' reference.

Suggestions

Delete the opening paragraph defining what Chipax is and the 'so you can focus on the integration logic rather than auth plumbing' filler; keep only what Claude cannot infer.

Either add an explicit '## Step 2: Search and run actions' header or replace the two 'skip to Step 2' references with the actual section name so the workflow is unambiguous.

Standardize the connection-get command to one form (either `membrane connection get` or `npx @membranehq/cli connection get`) throughout to avoid confusing the executable path.

DimensionReasoningScore

Conciseness

The body is mostly command-driven but opens with prose explaining what Chipax is ('Chilean SaaS platform that simplifies accounting...') and includes padded phrasing like 'so you can focus on the integration logic rather than auth plumbing' that Claude does not need.

3 / 5

Actionability

It provides many concrete, copy-paste-ready CLI commands (install, login, connection ensure, action run, request) covering common cases, with only minor gaps such as the unfilled CONNECTION_ID placeholder and the inconsistent use of `npx` vs `membrane` for the same command.

4 / 5

Workflow Clarity

The install → authenticate → connect → poll-for-ready → search → run sequence is clear with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-retry feedback loop, but the repeated 'skip to Step 2' references a Step 2 header that does not exist, leaving a minor sequencing gap.

4 / 5

Progressive Disclosure

Content is well-organized into clear section headers (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested references, but at ~159 lines all material is inlined in SKILL.md with no split-out reference files, keeping it just below 5.

4 / 5

Total

15

/

20

Passed

Description

61%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 cleanly names the target app and includes an explicit 'Use when' trigger, making it distinctive and reasonably complete. Its main weakness is that the stated capabilities are generic verbs rather than concrete actions.

Suggestions

Replace generic verbs with concrete Chipax actions, e.g. 'Manage data, records, and automate workflows' → 'Create and fetch invoices, bank transactions, contacts, and cash-flow records' to lift specificity.

Add natural trigger synonyms users might say (e.g. 'contabilidad', 'facturas', 'gastos') so the description matches a wider range of phrasings.

DimensionReasoningScore

Specificity

The description names the domain ('Chipax integration') but its actions — 'Manage data, records, and automate workflows' — are generic and minimal rather than concrete, matching the anchor 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

It supplies both a what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Chipax data'), though the what is generic, capping it below 5.

4 / 5

Trigger Term Quality

The only natural keyword is 'Chipax' / 'Chipax data' in the 'Use when the user wants to interact with Chipax data' clause; relevant but missing common variations or synonyms a user might say.

3 / 5

Distinctiveness Conflict Risk

'Chipax' is a specific named SaaS app, giving the skill a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

14

/

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.