Name: unleash
Rating: 60 (1 reviews)
Author: membranedev

unleash

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

Quality

70%

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

Quality

Content

78%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-checkpointed connection workflow, and it stays reasonably concise. Its main gaps are in progressive disclosure — denser reference material is inlined in a single file rather than split out, and an inconsistent step numbering makes navigation slightly rough.

Suggestions

Fix the step numbering: define an explicit 'Step 2' or replace 'Skip to Step 2' with a concrete in-page anchor so the connection flow is unambiguous.

Move the connection-state taxonomy and proxy flags table into a separate reference file (e.g. references/connection-states.md) and link to it from the overview to reduce inlined bulk.

Trim the editorial sentences in Best practices ('This will burn less tokens...') to keep the section as terse, directive guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient: short overview, direct executable commands, and no padding explaining what feature flags are. A few sentences could be trimmed ('This is the fastest way to get a connection', the chatty best-practice intros), matching 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request with a complete flags table), covering the common cases. This matches 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit state-check checkpoints and a feedback loop (poll again after CLIENT_ACTION_REQUIRED, inspect error on CONFIGURATION_ERROR). However the numbering is broken — it references 'Step 2' and labels a sub-step '1b' with no visible Step 2 — which is a navigation gap, so it sits at 'clear sequence with most checkpoints present; minor validation gaps' rather than a 5.	4 / 5
Progressive Disclosure	Sections are well-organized with headers, but the full connection-state taxonomy and the proxy flags table are inlined content that would fit better in separate reference files, and the dangling 'Step 2' reference weakens navigation. With no bundle files to offload detail, this is 'some structure but could be better organized; content that should be separate is inline' rather than the well-split structure of a 4.	3 / 5
	Total	16 / 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 cleanly states both what the skill does and when to use it, anchored by a distinct product name. Its weakness is generic action language and missing natural trigger terms (feature flags, rollouts) that would make it more specific and discoverable.

Suggestions

Replace generic actions with concrete Unleash operations, e.g. 'Manage feature flags, variants, segments, projects, and environments'.

Expand the trigger clause with natural phrases users say: 'Use when the user wants to manage feature flags, toggles, rollouts, or run experiments in Unleash'.

Add file-format or API synonyms (e.g. 'feature toggles', 'Unleash API') to strengthen trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the Unleash domain with a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Unleash operations like feature flags or variants. It matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor, and lacks the multiple specific actions needed for a 4.	3 / 5
Completeness	Both a clear 'what' ('Unleash integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Unleash data') are present, but the trigger could be more specific with concrete phrases. This matches 'has both what and when; when could be more explicit or specific' rather than the fully concrete trigger phrases of a 5.	4 / 5
Trigger Term Quality	It surfaces 'Unleash' and 'data' as keywords but misses the natural terms users would say for this product (feature flags, toggles, rollouts, experimentation). This fits 'some relevant keywords but missing common variations or synonyms' and falls short of the comprehensive coverage required for a 4.	3 / 5
Distinctiveness Conflict Risk	Naming the product 'Unleash' gives it a clear, distinct niche with low conflict risk, but the generic phrasing ('Manage data, records, and automate workflows') leaves minor overlap with adjacent data/workflow skills. It is 'mostly distinct; minor overlap risk' rather than the minimal-risk clear-niche of a 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/unleash/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.