CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cafe-24

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

Quality

66%

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/cafe-24/SKILL.md
SKILL.md
Quality
Evals
Security

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 delivers genuinely executable Membrane CLI guidance with good connection-lifecycle handling, and is appropriately scoped as a single-file skill. Its weaknesses are moderate: a broken 'Step 2' cross-reference, no verification guidance around potentially destructive proxy requests, duplicated discovery commands, and placeholder sections (Popular actions, entity overview) that carry no content.

Suggestions

Fix the dangling reference: 'If the returned connection has state: READY, skip to Step 2' points to a step that doesn't exist — either number the workflow steps explicitly (1. Install, 2. Authenticate, 3. Connect, ...) or replace the reference with the actual next action ('skip to Searching for actions').

Add validation guidance for destructive proxy requests: before running POST/PUT/DELETE via membrane request, verify with a GET first, confirm IDs with the user, and check the response body for errors — the current proxy section sends arbitrary mutations with no checkpoints.

Either populate 'Popular actions' with the actual common Cafe 24 intents (e.g., list products, get orders by date) or remove it and the duplicated npx-form discovery command, keeping a single canonical form; also give the bare 'Cafe 24 Overview' entity list a purpose (e.g., which entities map to which action intents) or cut it.

DimensionReasoningScore

Conciseness

The body is mostly efficient commands, but contains trimmable material: the introductory paragraph ("Think of it as a localized Shopify"), a near-duplicate action-discovery command (membrane vs npx @membranehq/cli@latest forms), an empty "Popular actions" section that adds no content, and padded prose like "This will burn less tokens". This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than anchor 4's minor-instances bar.

3 / 5

Actionability

Concrete, executable commands appear throughout (npm install -g @membranehq/cli@latest, membrane connection ensure "https://www.cafe24.com/" --json, membrane action run <actionId> --connectionId=... --input '{...}') plus a proxy flags table — 'mostly executable guidance; concrete code or commands with minor gaps'. It falls short of 5 because there are no Cafe 24-specific worked examples (e.g., an actual intent query returning a real action for products or orders), and the 'Popular actions' section lists none.

4 / 5

Workflow Clarity

The install → login → connection ensure → poll states → search actions → run sequence is present, and connection state handling is well covered (--wait polling, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR → check error field). However, 'If the returned connection has state: READY, skip to Step 2' references a 'Step 2' that is never defined, and the proxy path permits arbitrary POST/PUT/DELETE requests with no validation or caution guidance, so the destructive/batch cap holds it at 'steps listed but validation gaps'.

3 / 5

Progressive Disclosure

This is a single self-contained ~140-line file with no bundle files, organized under clear headers (Install → Authentication → Connecting → Searching → Running → Proxy → Best practices) appropriate to its size — 'good structure; most content is appropriately placed'. It misses 5 due to organization gaps such as the empty 'Popular actions' section and the bare nested entity list under 'Cafe 24 Overview' that serves no navigational purpose.

4 / 5

Total

14

/

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 Cafe 24 niche and includes an explicit Use-when clause, but its capability statement is generic boilerplate that would fit almost any data-integration skill. Adding concrete operations (e.g., managing products, orders, customers) and natural trigger terms would lift it substantially.

Suggestions

Replace the generic phrase 'Manage data, records, and automate workflows' with the concrete Cafe 24 operations the skill supports, e.g. 'Manage Cafe 24 products, orders, customers, and mall/board data, and run or build workflows against them'.

Expand the trigger clause with natural user phrasings and synonyms, e.g. 'Use when the user mentions Cafe24/Cafe 24, their Cafe 24 store, or wants to manage Cafe 24 orders, products, or customers'.

Name the platform consistently (the body uses 'Cafe24' without the space) so the description's trigger terms match both how the user and the docs write it.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Cafe 24 domain but the actions are entirely generic, matching the anchor 'Names the domain but actions are minimal or generic' (cf. "Processes PDF files"). No concrete actions like listing orders or creating products are stated.

2 / 5

Completeness

Both parts are explicitly present: what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Cafe 24 data"). The when-clause is circular — it merely restates the domain — fitting anchor 4's caveat that the trigger guidance 'could be more explicit or specific', and it lacks the concrete trigger phrases required for a 5.

4 / 5

Trigger Term Quality

"Cafe 24" is the one relevant natural keyword, but common user phrasings such as orders, products, store, e-commerce, or online mall are missing. This matches 'Some relevant keywords but missing common variations or synonyms', and falls short of anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"Cafe 24" is a clearly named niche unlikely to be confused with other e-commerce skills, but the generic verb phrases ("Manage data, records, and automate workflows") create minor overlap risk with other data/integration skills. Mostly distinct with minor overlap risk, per anchor 4.

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.

Validation — 15 / 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

Path

skills/cafe-24/SKILL.md

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.