Name: cacoo
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

cacoo

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cacoo/SKILL.md

Quality

Content

76%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 content is highly actionable with executable commands and a well-sequenced connection workflow, but it lacks validation/verification steps for action results and proxy responses, and has minor redundancy in the action-discovery examples.

Suggestions

Add a validation/verification step after running actions or proxy requests, e.g. checking the `output`/response status and error fields before reporting success.

De-duplicate the action-list examples (lines ~110 and ~119) into a single canonical example to tighten conciseness.

Consider extracting the proxy flag table and clientAction state reference into a separate reference file as the skill grows.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with command examples and brief explanations, but the 'action list --intent' pattern is repeated across 'Searching for actions' and 'Popular actions', and best-practices prose could be trimmed slightly.	4 / 5
Actionability	Concrete, copy-paste-ready commands cover the common cases end-to-end (install, login, connection ensure/wait, action list/run with JSON input, proxy request with a full flag table).	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit state checkpoints and a poll-again feedback loop, but running actions and proxy requests (batch/destructive-capable operations) have no output validation step, which caps this at 3.	3 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-sectioned with clear headers and no nested references, though the inline API/flag reference could be split out as the skill grows.	4 / 5
	Total	16 / 20 Passed

Description

50%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 target app and includes a 'Use when' trigger, but its action language is generic and omits the natural Cacoo-specific terms (diagram, flowchart) that users would actually say.

Suggestions

Replace generic verbs with concrete Cacoo actions, e.g. 'Create and edit diagrams, manage folders and projects, automate diagram workflows.'

Add natural trigger terms users say, e.g. 'Use when the user wants to create or edit Cacoo diagrams, flowcharts, mind maps, or network diagrams.'

Tie the 'when' clause to specific artifacts (diagrams, .cacoo) rather than the vague phrase 'interact with Cacoo data'.

Dimension	Reasoning	Score
Specificity	Names the Cacoo domain but the actions ('Manage data, records, and automate workflows') are generic with no concrete Cacoo-specific operations like diagrams, folders, or projects.	2 / 5
Completeness	Both 'what' (Cacoo integration, manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Cacoo data') are present, though the 'when' is somewhat generic.	4 / 5
Trigger Term Quality	'Cacoo' is the only natural keyword; the natural terms users would actually say (diagram, flowchart, mind map, network diagram) are absent from the description.	2 / 5
Distinctiveness Conflict Risk	The named app 'Cacoo' gives it a clear distinct niche with minimal conflict risk, even though the surrounding action phrasing is boilerplate.	4 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/cacoo/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.