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

spydra

Spydra integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Spydra 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/spydra/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 content is a well-structured, actionable guide built around concrete Membrane CLI commands and an explicit connection-state feedback loop. Its main weaknesses are occasional marketing/explanatory prose and a broken "Step 2" cross-reference in the workflow.

Suggestions

Remove promotional and audience prose ("used by data scientists, researchers, and businesses...", "so you can focus on the integration logic rather than auth plumbing") to tighten token efficiency.

Fix the "skip to Step 2" reference by labeling the target section "Step 2: Search for actions" (or reword to "skip to Searching for actions") so the workflow cross-reference resolves.

Flesh out the "Popular actions" section with at least one concrete worked example (a real actionId and --input) instead of restating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but includes unnecessary prose Claude does not need, such as "It's used by data scientists, researchers, and businesses to collect information from websites" and the marketing line "so you can focus on the integration logic rather than auth plumbing", fitting anchor 3's "mostly efficient but includes some unnecessary explanation".	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection, action search/run, and proxying with a clear flags table, but the "Popular actions" section only restates the discovery command without a worked example of a real action invocation, leaving the minor gap of anchor 4.	4 / 5
Workflow Clarity	The install -> authenticate -> connect -> poll-until-ready -> discover -> run sequence is clear and includes an explicit state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED with re-polling), but the "skip to Step 2" reference points to a header that is not labeled "Step 2", a minor sequencing gap consistent with anchor 4.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a single self-contained document organized into well-labeled sections with no nested references, giving good structure per anchor 4; at ~140 lines it is somewhat long and the proxy flags / clientAction detail could potentially be split into a reference file, so it does not reach the lean ideal of anchor 5.	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 is a solid, third-person statement that covers both what the skill does and when to use it, anchored on a distinct product name. Its main weakness is the single generic verb "Manage" and a trigger clause that names the product but not the concrete tasks users would request.

Suggestions

Replace the single verb "Manage" with distinct concrete actions per resource, e.g. "Create and configure Pipelines, invite Users, and track Goals and Filters in Spydra".

Expand the trigger clause with task-oriented natural phrases, e.g. "Use when the user wants to scrape data, build Spydra pipelines, or manage Spydra organizations and users".

Mention Spydra's core purpose (web scraping / data extraction) so the description is distinguishable from generic data-tool skills.

Dimension	Reasoning	Score
Specificity	The description names the domain and lists five concrete resource types ("Organizations, Pipelines, Users, Goals, Filters"), but the only action verb is the generic "Manage" applied to all of them, so it does not enumerate distinct concrete actions as anchor 4 requires.	3 / 5
Completeness	It answers both "what" ("Manage Organizations, Pipelines, Users, Goals, Filters") and "when" ("Use when the user wants to interact with Spydra data"), but the "when" clause is generic rather than tied to concrete triggers, matching anchor 4 rather than the fully explicit anchor 5.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Spydra data" surfaces the product name as the primary keyword but omits natural task-oriented phrases users would say (scrape, extract data, create a pipeline), fitting anchor 3's "some relevant keywords but missing common variations".	3 / 5
Distinctiveness Conflict Risk	The named product "Spydra" plus its specific resource list gives it a clear niche with minimal conflict risk, though the description never names Spydra's actual purpose (scraping/extraction), leaving minor overlap risk with generic data-extraction skills per anchor 4.	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/spydra/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.