Name: blend
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

blend

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

Quality

72%

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

Quality

Content

82%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 is action-dense and executable with a clear connection workflow and polling feedback loop. Main weaknesses are inconsistent step numbering and a few trimmable filler lines.

Suggestions

Fix step numbering: label 'Step 1' / 'Step 2' explicitly so the 'skip to Step 2' reference resolves, and reconcile the orphaned '1b' heading.

Remove filler directives like 'Use action names and parameters as needed.' that add tokens without actionable value.

Dimension	Reasoning	Score
Conciseness	Largely efficient with copy-paste commands and minimal padding; only minor over-explanation (e.g., 'Use action names and parameters as needed.') could be trimmed. Not 5 because a few filler sentences remain.	4 / 5
Actionability	Fully executable, copy-paste-ready commands with flags throughout (install, login, connection ensure/get with --wait, action list/run, request proxy) covering the common cases. Fits anchor 5.	5 / 5
Workflow Clarity	Clear connection sequence with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop after user action. Not 5 because step numbering is inconsistent ('skip to Step 2' with no labeled Step 2, '1b' without a '1a').	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Working with Blend, Install, Auth, Connecting, Searching, Actions, Best practices) with no nested references. Not 5 because the skill is longer than the simple-skill threshold and the proxy/action reference could arguably live in a separate file.	4 / 5
	Total	17 / 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 is concise, in third person, and covers both what and when, but the action list is generic and trigger-term coverage is thin. It is clearly distinguishable due to the named Blend niche.

Suggestions

Replace generic actions ('Manage data, records, automate workflows') with concrete Blend-specific operations (e.g., 'create marketing materials, manage borrower and loan records').

Expand trigger terms with natural synonyms and specifics users would say (e.g., 'Blend', 'Blend data', 'Blend records', 'loan officer marketing content').

Dimension	Reasoning	Score
Specificity	Names the domain (Blend) and a few actions ('Manage data, records, and automate workflows') but the actions are generic rather than concrete; not comprehensive. Fits anchor 3 (names domain and 1-2 concrete actions) and not 4 since no specific operations are listed.	3 / 5
Completeness	Has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Blend data'), but the when could be more specific. Not 5 because trigger phrases are not comprehensive.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Blend', 'data', 'records', 'workflows') but lacks common variations, synonyms, or file extensions users would naturally say. Not 4 because coverage of natural terms is thin.	3 / 5
Distinctiveness Conflict Risk	'Blend' is a distinct niche and the trigger ('interact with Blend data') is mostly distinct with only minor overlap risk. Not 5 because the surrounding language ('data, records, workflows') is somewhat broad.	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/blend/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.