Name: cascade-strategy
Rating: 49.6 (1 reviews)
Author: membranedev

cascade-strategy

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

Quality

53%

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/cascade-strategy/SKILL.md

Quality

Content

50%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 mostly actionable with solid CLI examples and a real connection-state feedback loop, but it is marred by leaked refusal text at the top, a dangling "Step 2" reference, and a large inline actions table that belongs in a reference file. Removing the garbage opening and tightening the workflow would materially improve quality.

Suggestions

Delete the leaked refusal text on line 17 ("I don't have enough information to do that...") and the filler "Use action names and parameters as needed" — they add noise and no value.

Fix the dangling "skip to Step 2" by labeling the searching/actions section as Step 2 or removing the cross-reference.

Move the full popular-actions table into a references/actions.md file and keep only a short representative subset inline, with a clear link to the full list.

Dimension	Reasoning	Score
Conciseness	The body opens with leaked model refusal text ("I don't have enough information to do that. I'm a large language model...") and filler like "Use action names and parameters as needed", which are noticeable padding that should not be in a skill.	2 / 5
Actionability	It provides concrete, copy-pasteable commands (npm install, membrane login, connection ensure, action list/run, request) plus a populated actions table, with only minor gaps such as placeholder CONNECTION_ID handling.	4 / 5
Workflow Clarity	A sequence exists with explicit connection-state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the dangling "skip to Step 2" reference is undefined and create/update operations lack validation feedback loops.	3 / 5
Progressive Disclosure	Sections are organized with headers, but the large inline popular-actions table (~20 rows) is content that could live in a separate reference file, and there are no one-level-deep reference links to defer detail.	3 / 5
	Total	12 / 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 identifies a clear niche (Cascade Strategy) and includes an explicit use-when clause, but its action verbs are generic and trigger-term coverage is thin. Tightening the capability list with concrete operations would lift specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete operations such as "list, create, and update goals, tasks, and users in Cascade Strategy".

Add natural trigger synonyms users would say, e.g. "Use when the user mentions Cascade Strategy, Cascade goals, or Cascade tasks."

Dimension	Reasoning	Score
Specificity	Phrases like "Manage data, records, and automate workflows" name the domain but the actions are minimal and generic rather than concrete capabilities.	2 / 5
Completeness	It states a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Cascade Strategy data"), though the when could be more specific.	4 / 5
Trigger Term Quality	"Cascade Strategy" is a relevant named trigger and "data, records, workflows" appear, but common synonyms and variations users might say are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific "Cascade Strategy" app gives it a clear niche with low conflict risk, but the generic verbs leave minor overlap risk with other integration skills.	4 / 5
	Total	13 / 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/cascade-strategy/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.