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

Blog Docs Log in Get started

clyde

Clyde integration. Manage data, records, and automate workflows. Use when the user wants to interact with Clyde 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/clyde/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 content is a strong, command-heavy integration guide with fully executable examples, a well-sequenced connection workflow with state checkpoints and a feedback loop, and clean section organization. Its only notable weakness is a speculative, hedged opening paragraph that pads the context without adding actionable value.

Dimension	Reasoning	Score
Conciseness	The body is predominantly lean, command-driven content, but the hedged speculative opener ("Clyde is a communication and collaboration platform, likely used by teams... It probably offers features like...") and a few padded lines ("so you can focus on the integration logic rather than auth plumbing") are minor over-explanation that could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor rather than the fully-lean anchor 5.	4 / 5
Actionability	The body provides copy-paste-ready, executable commands for every common case (install, login, connection ensure/get, action list/run, request with a full flags table), matching the 'fully executable; copy-paste ready code or commands; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit state checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a feedback loop (poll again after the user acts), but the dangling "skip to Step 2" reference (no labeled Step 2) and the less-sequenced search/run sections are minor gaps, fitting 'clear sequence with most checkpoints; minor validation gaps' rather than the fully-checklisted anchor 5.	4 / 5
Progressive Disclosure	No bundle files exist, so the single-file body is scored on its own structure: it has well-organized, clearly headed sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with content appropriately placed, matching 'good structure; most content appropriately placed; minor organization gaps'; it is not the anchor 5 case because some material (the clientAction state machine, the flags table) could be split into reference files for a >50-line skill.	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 third-person, covers both what and when, and names a distinct product, but its action vocabulary ("manage data, records") is generic and its trigger phrasing lacks synonyms or concrete use cases. It sits solidly above average without reaching the top anchors.

Suggestions

Replace generic verbs with concrete Clyde actions, e.g. "List and run Clyde actions, send proxy API requests, and automate Clyde workflows" to lift specificity.

Expand the 'Use when' clause with natural trigger variations, e.g. "Use when the user wants to query Clyde records, run a Clyde action, or call the Clyde API directly".

Add a file/extension or feature anchor (e.g. meetings, transcriptions, or the Clyde API) to sharpen trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the Clyde domain and lists a few actions ("Manage data, records, and automate workflows"), but "manage data" and "manage records" are generic/abstract with only "automate workflows" being semi-concrete, matching the '1-2 concrete actions but not comprehensive' anchor rather than the comprehensive anchor 5.	3 / 5
Completeness	Both a 'what' ("Clyde integration. Manage data, records, and automate workflows") and a 'when' ("Use when the user wants to interact with Clyde data") are present, but the 'when' clause is somewhat generic, matching the anchor where both exist yet 'when' could be more explicit; it is not the explicit-concrete-trigger anchor 5.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Clyde data" surfaces the natural keyword "Clyde" and "Clyde data", but offers no synonyms or variations a user might actually say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Clyde" gives it a clear niche with low conflict risk, but the generic "interact with Clyde data" trigger leaves minor overlap with other data-management skills, fitting 'mostly distinct; minor overlap risk' rather than the minimal-risk anchor 5.	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/clyde/SKILL.md
Commit: f484c82

Reviewed: ~12 hours 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.