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

cumulio

Cumul.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cumul.io 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/cumulio/SKILL.md

Quality

Content

63%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 actionable with executable commands and a clear, validated connection workflow, but it carries marketing/filler prose and keeps detailed reference material inline in a single file instead of offloading it. Strengths are actionability and workflow clarity; weaknesses are conciseness and progressive disclosure.

Suggestions

Trim the marketing intro and filler ('Use action names and parameters as needed', 'so you can focus on the integration logic') to assume Claude's competence.

Move the proxy flag table and clientAction state-handling detail into a referenced file (e.g. references/connection-states.md) and link to it from SKILL.md.

Resolve the 'skip to Step 2' reference by labeling the action-search/run section as Step 2 so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes padding Claude does not need: the marketing intro ('Cumul.io is an embedded analytics platform that allows SaaS companies...'), 'so you can focus on the integration logic rather than auth plumbing', and the filler line 'Use action names and parameters as needed.'	3 / 5
Actionability	It provides copy-paste-ready membrane CLI commands for install, auth, connection, action list/run, and proxy requests plus a flag table, fitting 'mostly executable guidance with minor gaps' — the remaining placeholders (CONNECTION_ID, QUERY) require user-supplied values.	4 / 5
Workflow Clarity	The install → auth → connect → poll sequence is clear with explicit state feedback loops (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll instruction, matching level 4; the dangling 'skip to Step 2' reference with no matching labeled Step 2 is a minor checkpoint gap.	4 / 5
Progressive Disclosure	No bundle files exist and the body references no offloaded materials; content is organized by headers but detailed reference material (the proxy flag table, clientAction state handling) is inlined in a single ~159-line file rather than split into a clearly signaled one-level-deep reference.	3 / 5
	Total	14 / 20 Passed

Description

62%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 covers both what and when with a named-platform trigger, but relies on generic action verbs and lacks keyword variations. It is solidly above average yet short of the comprehensive, concrete exemplars.

Suggestions

Replace generic verbs with concrete Cumul.io operations, e.g. 'Create and filter datasets, design dashboards, manage users and groups, schedule exports'.

Add natural trigger variations such as 'dashboards', 'reports', 'datasets', or 'embedded analytics' alongside 'Cumul.io data'.

Tighten the 'Use when' clause to name specific intents, e.g. 'Use when the user wants to build or query Cumul.io dashboards, datasets, or scheduled reports'.

Dimension	Reasoning	Score
Specificity	Names the Cumul.io domain and three actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete operations, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor rather than the more specific level 4.	3 / 5
Completeness	It states both what ("Cumul.io integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Cumul.io data"), but the when clause could be more specific, matching the level 4 anchor rather than the fully explicit level 5.	4 / 5
Trigger Term Quality	"Cumul.io" and "interact with Cumul.io data" are relevant natural terms, but coverage is thin with no synonyms or common variations, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Cumul.io platform gives it a clear niche with minimal conflict risk, but the generic action verbs ("manage data, records") leave minor overlap risk with adjacent data skills, fitting level 4 rather than the cleanly distinct level 5.	4 / 5
	Total	14 / 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/cumulio/SKILL.md
Commit: f484c82

Reviewed: ~15 hours 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.