Name: skyword
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

skyword

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

Quality

66%

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

Quality

Content

75%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, mostly executable guide to the Membrane CLI workflow with a genuine polling/feedback loop for connection readiness. Its main weaknesses are a broken 'Step 2' navigation cue, the absence of result-verification guidance for potentially destructive proxy/action calls, and minor trimming opportunities.

Suggestions

Replace or remove the dangling 'skip to Step 2' references by labeling the action-search/run section as an explicit 'Step 2'.

Add a verification checkpoint after running actions or proxy requests (e.g., check the `output`/error field and confirm the result before proceeding) to support destructive or batch operations.

Trim filler lines ('so you can focus on the integration logic rather than auth plumbing', 'This will burn less tokens') to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with brief framing; minor padded lines like 'so you can focus on the integration logic rather than auth plumbing' and 'This will burn less tokens' could be trimmed, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with flag tables and JSON examples, with only minor gaps such as unresolved 'Step 2' references and placeholder IDs.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with a real feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, repoll), but the 'skip to Step 2' cue points to no labeled Step 2 and action results lack an explicit verification checkpoint.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline in one well-organized file with clear section headers; it is over 50 lines but appropriately structured with no nested or buried references, fitting 'good structure; most content appropriately placed'.	4 / 5
	Total	16 / 20 Passed

Description

57%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 identifies a distinct niche (Skyword) and includes an explicit 'Use when' trigger covering both what and when, but its action language is generic ('manage data, records, automate workflows') rather than concrete. Trigger term coverage is adequate but thin on synonyms or task-specific phrases.

Suggestions

Replace generic verbs with concrete Skyword capabilities (e.g., 'manage content pieces, briefs, and assignments; track content workflows and tasks').

Expand the 'Use when' clause with natural trigger phrases users would say (e.g., 'Use when the user wants to manage Skyword content, briefs, tasks, or content workflows').

Add file- or entity-specific triggers drawn from the body's overview (Content Calendar, Brief, Task, Workflow) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Phrases 'Manage data, records, and automate workflows' name the Skyword domain but the actions are generic and minimal rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Skyword data'), but the 'when' clause is somewhat generic and could be more explicit, matching the 'both what and when; when could be more specific' anchor.	4 / 5
Trigger Term Quality	'Skyword' and 'Skyword data' are relevant natural keywords a user would say, but coverage is limited with no synonyms or task-specific variations, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Skyword' is a specific named platform giving it a clear niche with low conflict risk, though the generic action verbs leave minor overlap risk with other data-management skills.	4 / 5
	Total	13 / 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/skyword/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.