Name: wirewheel
Rating: 51.2 (1 reviews)
Author: membranedev

wirewheel

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

Quality

56%

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

Quality

Content

50%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 strong executable CLI guidance for connecting to and acting on WireWheel via Membrane, but is undermined by a bloated, largely generic entity catalog and missing validation checkpoints in its action workflows.

Suggestions

Move the ~210-item entity catalog into a separate references file (e.g. references/entities.md) and keep only a concise summary plus a one-level-deep link in SKILL.md.

Add explicit validation/verification checkpoints to the action-run and proxy workflows, e.g. check the response `output`/`error` fields and retry or surface errors before proceeding.

Prune generic policy and risk-assessment entries from the catalog that are not real WireWheel actions to reduce token load.

Dimension	Reasoning	Score
Conciseness	The ~210-item inlined entity catalog includes large amounts of generic policy and risk-assessment boilerplate that is unlikely to be actionable, making the body noticeably padded beyond minor trimming, matching anchor 2.	2 / 5
Actionability	Provides concrete, copy-pasteable Membrane CLI commands for install, auth, connection, action list/run, and proxy with a flags table, with only minor gaps such as unresolved placeholders and no fully concrete end-to-end example, matching anchor 4.	4 / 5
Workflow Clarity	The connect workflow is sequenced with state-based branching and re-polling, but action runs and proxy mutations lack explicit validation/verification checkpoints, which per the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The body has clear section headers but no bundle files; the large entity catalog is inlined where it should be a separate one-level-deep reference, matching anchor 3 for content that should be separate being inline.	3 / 5
	Total	12 / 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 answers both 'what' and 'when' with an explicit trigger, anchored by a distinct product name. It is weakened by generic action language and trigger terms that don't reflect WireWheel's actual privacy-management use cases.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with WireWheel-specific capabilities such as handling data subject rights requests, managing consent, and running vendor assessments.

Expand the trigger clause with concrete natural-language phrases a user would say, e.g. 'Use when the user wants to process data subject requests, manage consent, or assess vendors in WireWheel'.

Dimension	Reasoning	Score
Specificity	Names the WireWheel domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and not tied to the platform's actual privacy-compliance capabilities, matching anchor 3.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when...' trigger, but the 'when' is generic rather than concrete trigger phrases, fitting anchor 4.	4 / 5
Trigger Term Quality	The trigger relies almost entirely on repeating the product name ('interact with WireWheel data') and omits natural task phrases users would say (privacy requests, consent, DSRs, vendor assessments), matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ('WireWheel integration') gives a clear niche with low conflict risk, though the generic 'manage data, records' phrasing leaves minor overlap, matching 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/wirewheel/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.