Name: blue
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

blue

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

Quality

64%

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

Quality

Content

63%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 delivers executable CLI guidance and a reasonably clear connection workflow with validation checkpoints, but is undercut by leftover generated placeholder text, an off-topic Bluetooth docs link, and a bulky inline entity/action catalog that should be split out. The core integration instructions are solid; the surrounding noise should be removed.

Suggestions

Delete the placeholder line ("I don't have enough information to describe this app.") and the irrelevant Apple Bluetooth docs link, which are clearly generated artifacts.

Move the 37-line entity list and full popular-actions table into a separate reference file, keeping only the most-used actions inline in SKILL.md.

Add an explicit error-recovery checkpoint for CONFIGURATION_ERROR/SETUP_FAILED states (e.g., inspect the error field, retry ensure) to strengthen the feedback loop to a 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but carries dead weight: a generated placeholder ("I don't have enough information to describe this app"), an irrelevant Apple Bluetooth docs link, and a 37-line near-combinatorial entity list that adds no actionable value, fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Provides concrete, executable CLI commands with real flags (membrane connection ensure, --wait, --json, action run --input), matching the 'mostly executable guidance with minor gaps' anchor; gaps are minor (placeholders like CONNECTION_ID, action IDs left to discovery).	4 / 5
Workflow Clarity	The connection process has a clear sequence with explicit state branching (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-after-action feedback loop, matching the 'clear sequence with most checkpoints present' anchor; not quite a 5 because error-recovery detail is light.	4 / 5
Progressive Disclosure	No bundle files exist, so this is a single ~200-line document with section headers but a large inline action catalog and entity list that arguably belong in a separate reference, fitting the 'some structure but could be better organized; content that should be separate is inline' anchor.	3 / 5
	Total	14 / 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 covers both what and when and is well-scoped to the Blue app, but the action verbs are generic and trigger-term coverage is thin with no synonyms or file extensions. Tightening the action list and broadening natural trigger phrases would raise specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with specific concrete actions a user would request, e.g. "create and update records, manage cases and contacts, assign todos".

Broaden trigger terms with synonyms users actually say, e.g. "tasks", "todos", "projects", "cases" rather than only "Blue data".

Make the 'when' clause more concrete by naming the objects users work with (cases, contacts, todos) so it is distinguishable from generic data skills.

Dimension	Reasoning	Score
Specificity	Names the domain ("data, records") and two concrete actions ("Manage", "automate workflows"), matching the anchor that lists domain plus 1-2 actions but is not comprehensive. The verbs are generic enough to keep it below 4.	3 / 5
Completeness	Explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Blue data"), matching the anchor where both are present but the 'when' could be more specific.	4 / 5
Trigger Term Quality	Includes one natural trigger phrase ("Use when the user wants to interact with Blue data") with relevant keywords, but lacks common variations or synonyms, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The trigger is tied to the specific app "Blue" ("interact with Blue data"), giving it a clear niche with distinct triggers and minimal conflict risk, 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/blue/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.