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

Blog Docs Log in Get started

spade

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

Quality

65%

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

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 body is a well-structured, actionable guide to the Membrane/Spade integration with concrete commands and useful connection-state feedback loops. It would improve by removing the redundant 'Popular actions' section and tightening filler phrases.

Suggestions

Remove or merge the 'Popular actions' section, which duplicates the 'Searching for actions' command without adding concrete action names.

Delete filler lines like 'Use action names and parameters as needed.' and 'This is the fastest way to get a connection.' to improve token efficiency.

Label the implicit 'Step 2' referenced in the connection flow so the READY/skip routing is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands throughout, but includes redundancy (the 'Popular actions' section restates the action-list command already shown) and minor filler like "Use action names and parameters as needed" and "This is the fastest way to get a connection", fitting 'mostly efficient but could be tightened'.	3 / 5
Actionability	Provides copy-paste-ready CLI commands with flags for login, connection, action listing/running, and proxy requests, plus a clear options table; the 'Popular actions' section stays abstract without naming actual actions, a minor gap that keeps it at anchor 4 rather than 5.	4 / 5
Workflow Clarity	Clear install-authenticate-connect-search-run sequence with explicit state-based checkpoints and polling feedback loops for connection readiness; the 'If READY skip to Step 2' reference points to an unlabeled Step 2, a minor validation/sequencing gap capping it at 4.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline in a single well-organized SKILL.md with clear section headers; structure is good and content is appropriately placed, though the proxy/state-handling detail could conceptually live in separate reference files, fitting anchor 4.	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 correctly pairs a product-specific domain with an explicit 'Use when' trigger, satisfying both the what and when requirements. Its main weakness is generic, buzzword-heavy action language ('manage data', 'automate workflows') that lacks concrete capabilities.

Suggestions

Replace generic verbs with concrete Spade capabilities (e.g., 'Create and assign tasks, track project progress, manage documents and team members').

Add natural trigger synonyms a user might say, such as 'tasks', 'projects', or 'team collaboration', to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Spade domain and lists several action categories ("Manage data, records, and automate workflows"), but the actions are generic verbs rather than concrete capabilities, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	States what it does ("Manage data, records, and automate workflows") and gives an explicit trigger ("Use when the user wants to interact with Spade data"); the 'when' is present and reasonably explicit but the 'what' is somewhat generic, matching anchor 4 rather than 5.	4 / 5
Trigger Term Quality	Includes the natural product term "Spade" and phrases like "interact with Spade data" and "records"/"workflows", but misses common synonyms or variations a user might say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named product "Spade" gives it a clear niche with minimal conflict risk, though the generic action verbs ("manage data", "automate workflows") create minor overlap with other data/productivity skills, fitting 'mostly distinct; minor overlap risk'.	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/spade/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.