Name: cirrus-labs
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

cirrus-labs

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

Quality

66%

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/cirrus-labs/SKILL.md

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 content is a well-structured, highly actionable guide built around concrete Membrane CLI commands and a clear connection workflow with state-based checkpoints. Its main gaps are minor prose padding and the lack of a final verification step after running actions.

Suggestions

Trim the introductory paragraph describing what Cirrus Labs is; assume Claude knows the platform and lead directly with the install/connect workflow.

Add a verification checkpoint after running actions, e.g. checking the response `output`/`error` fields and confirming success before reporting completion to the user.

Merge or expand the thin "Popular actions" section so it does not merely repeat the `action list` command from the searching section.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but opens with a descriptive paragraph about what Cirrus Labs is and includes some prose that could be trimmed, fitting the "mostly efficient but could be tightened" anchor.	3 / 5
Actionability	It provides numerous copy-paste-ready commands (login, connection ensure, action list/run, request) with flags explained in a table, which is mostly executable guidance with only minor gaps such as placeholder IDs.	4 / 5
Workflow Clarity	A clear install -> authenticate -> connect -> poll-for-ready -> search -> run sequence exists with explicit state-checking checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but lacks a final verification step for executed actions.	4 / 5
Progressive Disclosure	The single SKILL.md is well organized into clearly labeled sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, though the thin "Popular actions" section is slightly redundant with the searching section.	4 / 5
	Total	15 / 20 Passed

Description

66%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 is clear and product-specific with both a what and a when clause, giving it strong distinctiveness. Its weaknesses are generic action verbs and limited trigger-term coverage that miss the natural CI/CD vocabulary users would actually say.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Cirrus Labs operations, e.g. "trigger builds, view tasks, inspect logs, and automate CI/CD pipelines".

Expand the trigger clause to include natural user phrasings like "Use when the user wants to trigger or monitor Cirrus CI builds, tasks, or pipelines."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Cirrus Labs") and a couple of actions ("Manage data, records, and automate workflows"), but those actions are fairly generic rather than concrete platform-specific operations, so it is not comprehensive enough for a 4.	3 / 5
Completeness	Both a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Cirrus Labs data") are present, but the trigger clause could be more specific with concrete use cases, keeping it below a 5.	4 / 5
Trigger Term Quality	It includes relevant natural terms ("Cirrus Labs", "interact with Cirrus Labs data") a user might say, but misses common variations and synonyms such as CI/CD, builds, pipelines, or tasks that users would naturally mention.	3 / 5
Distinctiveness Conflict Risk	Naming a specific named product ("Cirrus Labs") with a product-scoped trigger gives it a clear niche and minimal conflict risk with other skills, matching the top anchor.	5 / 5
	Total	15 / 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/cirrus-labs/SKILL.md
Commit: f484c82

Reviewed: 3 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.