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

Blog Docs Log in Get started

waydev

Waydev integration. Manage data, records, and automate workflows. Use when the user wants to interact with Waydev 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/waydev/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 a strong, actionable integration guide built almost entirely from executable Membrane CLI commands with a clear connection-state workflow. Its main weaknesses are minor verbosity in the intro, slightly inconsistent step numbering, and a monolithic single-file structure with no progressive disclosure into reference files.

Suggestions

Trim the opening marketing paragraph and editorializing asides (e.g. "so you can focus on the integration logic rather than auth plumbing") to assume Claude's competence.

Fix the step numbering: replace the orphaned "1b" subsection and "skip to Step 2" references with a consistent Step 1 / Step 2 / Step 3 sequence for the connect-search-run flow.

As the skill grows, move the report taxonomy and the proxy flag reference table into separate reference files (e.g. REPORTS.md, PROXY.md) referenced from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is dominated by concrete, copy-pasteable commands and a tight report taxonomy, with only minor padding such as the marketing-style opening paragraph ("engineering intelligence platform that provides data-driven insights...") and editorial lines like "so you can focus on the integration logic rather than auth plumbing".	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every stage (install, login, connection ensure, connection get --wait, action list/run, request proxy) plus a flag table, covering the common cases with explained placeholders.	5 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop, but step labels are inconsistent — it references "Step 2" and a "1b" subsection without a matching numbered step structure.	4 / 5
Progressive Disclosure	With no bundle files present, all content lives inline in a single well-sectioned SKILL.md (Overview, Working with Waydev, Install, Auth, Connecting, Searching, Popular actions, Best practices) that is easy to navigate, though some content (the report taxonomy or proxy flag reference) could be split into reference files as the skill grows.	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 correctly pairs a what and a when and leverages a distinct brand name, but it stays generic on capabilities and trigger vocabulary. Expanding the actions and triggers to mention reports, metrics, and developer-productivity use cases would lift it toward the top anchors.

Suggestions

Replace generic "Manage data, records, and automate workflows" with concrete Waydev capabilities such as pulling Daily/Team Performance/Sprint reports and tracking commits, reviews, and developer activity.

Broaden the trigger clause to list natural phrases users say, e.g. "Use when the user asks for Waydev reports, engineering metrics, developer productivity, or delivery tracking."

Consider mentioning the data domains (commits, pull requests, reviews, goals, projects) so the skill is distinguishable from generic data-integration skills.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Waydev domain with a couple of actions, but the actions are generic ("manage data, records") rather than concrete capabilities like reports or commits.	3 / 5
Completeness	Both halves are present — a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Waydev data") — but the trigger clause is generic rather than listing concrete use cases.	4 / 5
Trigger Term Quality	It surfaces the brand term "Waydev" and "Waydev data" but omits the natural vocabulary users would actually say (reports, engineering metrics, developer productivity, commits, pull requests).	3 / 5
Distinctiveness Conflict Risk	The named product "Waydev" gives it a clear, low-conflict niche, but the generic "manage data, records" phrasing leaves minor overlap risk with other data-management skills.	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/waydev/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.