CtrlK
BlogDocsLog inGet started
Tessl Logo

unblu

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

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/unblu/SKILL.md
SKILL.md
Quality
Evals
Security

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 delivers executable Membrane CLI commands with a clear, state-aware connection workflow and good section structure, though it has some redundancy and a few dangling step references that slightly reduce clarity.

Suggestions

Remove the duplicated action-list command in "Popular actions" or merge it with the earlier "Searching for actions" section.

Fix the dangling "skip to Step 2" references by labeling the actual next section (e.g. "Skip to Searching for actions").

Trim marketing-style padding like "so you can focus on the integration logic rather than auth plumbing" to keep the body lean.

DimensionReasoningScore

Conciseness

The body is mostly focused on concrete CLI commands, but the "Popular actions" section repeats the action-list command already shown, and lines like "so you can focus on the integration logic rather than auth plumbing" are slight padding.

3 / 5

Actionability

Commands like `membrane connection ensure`, `membrane action run ... --input '{...}'`, and the proxy flag table are concrete and copy-paste ready, with only minor reliance on placeholders like CONNECTION_ID.

4 / 5

Workflow Clarity

The install → authenticate → connect → poll-for-state → handle branches → search → run sequence is clear with feedback loops (re-poll after CLIENT_ACTION_REQUIRED), but dangling "skip to Step 2" references with no labeled Step 2 are a minor gap.

4 / 5

Progressive Disclosure

The body is organized into well-labeled sections with no nested references and no bundle files to navigate; content is appropriately inline for a CLI usage guide, with only minor redundancy in the Popular actions section.

4 / 5

Total

15

/

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 has an explicit trigger clause and a distinct brand niche, but its capability list is generic and misses the concrete Unblu-specific actions and natural terms (messaging, chat, video) a user would actually say.

Suggestions

Replace generic verbs with concrete Unblu capabilities, e.g. "Send secure messages, start live chats, and launch video calls with visitors".

Add natural trigger terms users say, such as "messaging", "live chat", "co-browsing", or "video calls".

Tighten the "Use when" clause to reference those concrete intents, e.g. "Use when the user wants to manage Unblu conversations, agents, or co-browsing sessions."

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Unblu domain and lists several actions, but the actions are generic rather than concrete Unblu capabilities (messaging, live chat, video calls).

3 / 5

Completeness

Both a "what" (manage data, records, automate workflows) and an explicit "Use when the user wants to interact with Unblu data" trigger are present, though the "what" could be more specific.

4 / 5

Trigger Term Quality

The natural keyword "Unblu" is present in the trigger clause, but common variations a user might say (messaging, chat, co-browsing) are absent, so coverage is partial.

3 / 5

Distinctiveness Conflict Risk

The "Unblu" brand trigger is a clear niche with minimal conflict risk, but the generic "manage data, records, workflows" phrasing leaves minor overlap with general data skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.