Name: cubicl
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

cubicl

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

86%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 highly actionable CLI integration guide with executable commands and a well-checkpointed connection-state workflow. Its only weaknesses are minor conciseness padding and slightly inconsistent step numbering that creates small ambiguity in the workflow sequence.

Suggestions

Remove the redundant action-list instruction in "Popular actions" since "Searching for actions" already covers `membrane action list`.

Fix the workflow numbering: add a labeled "Step 1a/Step 2" (or relabel "1b") so cross-references like "skip to Step 2" resolve unambiguously.

Trim the introductory overview paragraph and the "focus on integration logic rather than auth plumbing" aside, which explain concepts not needed for execution.

Dimension	Reasoning	Score
Conciseness	Commands are direct and mostly lean, but the opening overview paragraph, the "focus on integration logic rather than auth plumbing" aside, and a duplicated action-list instruction between "Searching for actions" and "Popular actions" are minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every key operation (install, login, connection ensure/get with --wait, action list/run with JSON input, request proxy) covering the common cases with appropriate placeholders.	5 / 5
Workflow Clarity	The connection lifecycle is sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/ERROR) and a poll-handle-repoll feedback loop, but inconsistent numbering (a "1b" with no "1a" and an unlabeled "Step 2") introduces minor sequence ambiguity.	4 / 5
Progressive Disclosure	As a single-file skill with no external bundle files, it is well-organized into clear headed sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) that make navigation easy, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	18 / 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 the skill does and when to use it with an explicit trigger clause, and its product-specific naming keeps conflict risk low. Its main weakness is generic action verbs and a lack of natural synonym coverage in the trigger terms.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Cubicl-specific operations (e.g., "create and assign tasks, track projects, manage team availability").

Expand trigger terms to include natural user phrases like "tasks", "projects", or "team collaboration" rather than only "Cubicl data".

Tighten the "when" clause to name the concrete Cubicl objects users mention (tasks, meetings, participants) instead of the abstract "interact with Cubicl data".

Dimension	Reasoning	Score
Specificity	It names the Cubicl domain and a few actions ("Manage data, records, and automate workflows"), but the verbs are generic ("manage") rather than concrete operations, matching the 1-2 concrete-actions anchor without being comprehensive.	3 / 5
Completeness	It explicitly provides both a "what" (manage data, records, automate workflows) and a "when" ("Use when the user wants to interact with Cubicl data"), though the trigger could be more specific, matching the "both what and when, when could be more explicit" anchor.	4 / 5
Trigger Term Quality	Natural trigger terms like "Cubicl" and "interact with Cubicl data" are present, but it lacks common synonyms or variations a user might actually say (tasks, projects, team collaboration), fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the specific Cubicl product name makes it largely distinct with minimal conflict risk, though the broad "manage data, records, automate workflows" phrasing keeps it just shy of a fully clear niche.	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/cubicl/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.