CtrlK
BlogDocsLog inGet started
Tessl Logo

kooomo

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/kooomo/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-organized, actionable CLI integration guide with a clear connection state machine and feedback loops, weakened mainly by some marketing prose and inconsistent step numbering.

Suggestions

Trim the opening descriptive paragraph and conversational filler ('so you can focus on integration logic rather than auth plumbing') to improve token efficiency.

Fix the broken 'skip to Step 2' reference and reconcile the '1b' heading so the connection sequence is unambiguous.

Expand the sparse Kooomo Overview beyond a bare Orders/Products/Customers bullet list, or move it into a short orienting sentence tied to the actions.

DimensionReasoningScore

Conciseness

The body is mostly commands and brief explanations, but the opening marketing paragraph ('designed for enterprise-level clients...') and prose like 'so you can focus on integration logic rather than auth plumbing' are unnecessary padding.

3 / 5

Actionability

It provides many concrete, executable commands (connection ensure, action run, request) plus a flags table, but placeholders like CONNECTION_ID and QUERY leave minor gaps before copy-paste readiness.

4 / 5

Workflow Clarity

The connection flow has state polling and a re-check feedback loop, but 'skip to Step 2' references a non-existent Step 2 and the '1b' heading has no labeled '1a', creating minor sequence gaps.

4 / 5

Progressive Disclosure

The single self-contained file is well-sectioned with clear headers and no nested references, but the thin Overview bullet list and lack of any split-out detail keep it from a top score.

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 pairs a 'what' with an explicit 'Use when' trigger for a named platform, but its action language is generic and lacks the concrete ecommerce nouns that would aid trigger matching and distinctiveness.

Suggestions

Replace generic verbs ('Manage data, records, automate workflows') with concrete Kooomo actions such as querying orders, products, and customers.

Broaden the trigger clause to name natural phrases users would say, e.g. 'Use when the user wants to query Kooomo orders, products, or customers'.

Mention the ecommerce/online-store context in the 'what' to sharpen distinctiveness from generic data skills.

DimensionReasoningScore

Specificity

The description names the Kooomo domain but its actions ('Manage data, records, and automate workflows') are generic abstractions rather than concrete ecommerce actions like orders, products, or customers.

2 / 5

Completeness

Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Kooomo data') are present, though the 'when' could be more specific.

4 / 5

Trigger Term Quality

'Kooomo' is a natural keyword and there is a trigger clause, but the phrasing 'interact with Kooomo data' is generic and omits concrete task nouns users would actually mention.

3 / 5

Distinctiveness Conflict Risk

The named platform 'Kooomo' gives a clear niche with distinct triggers, but the generic action language ('data', 'records', 'workflows') creates minor overlap risk with other data-management skills.

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.