Name: spondyr
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

spondyr

Spondyr integration. Manage Organizations. Use when the user wants to interact with Spondyr data.

Quality

63%

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

Quality

Content

61%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 highly actionable, well-organized CLI reference with a genuine polling feedback loop for connection setup. It is held back by unnecessary background prose, a low-value glossary list, and the absence of verification steps around destructive proxy requests.

Suggestions

Remove the SaaS background paragraph and the bare Table/Column/Record/View/Dashboard overview list, which add tokens without actionable value.

Add an explicit verify/confirm checkpoint before destructive proxy requests (e.g. suggest confirming -X DELETE/-X PUT outcomes or dry-running), which would lift workflow_clarity above the destructive-operation cap.

Replace the placeholder-heavy run examples with at least one fully-substituted end-to-end example to move actionability from 4 toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the SaaS background paragraph ('Spondyr is a SaaS application used by healthcare providers...') and the vague Table/Column/Record/View/Dashboard list are unnecessary padding Claude does not need, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-pasteable commands with flags and a flag table covering common cases, but placeholders like <actionId> and CONNECTION_ID require substitution, leaving minor gaps versus the fully-ready score-5 anchor.	4 / 5
Workflow Clarity	The install→auth→connect→search→run flow is sequenced with a polling feedback loop on connection state, but the proxy path enables destructive ops (-X DELETE) with no verification step, so the destructive-operation cap holds this at 3.	3 / 5
Progressive Disclosure	There are no bundle files and the content is a single well-sectioned file appropriate for a CLI integration skill of this size, fitting 'good structure; most content appropriately placed' rather than the vague-structure score 3.	4 / 5
	Total	14 / 20 Passed

Description

66%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' with an explicit 'Use when' trigger and pins a clear niche via the named Spondyr app. Its main weakness is thin capability coverage — only 'Manage Organizations' is named — leaving specificity and trigger richness below the top anchors.

Suggestions

List more concrete capabilities in the description (e.g. query records, run actions, proxy API requests) to lift specificity from 3 toward 5.

Add natural trigger synonyms users might say (e.g. 'Spondyr records', 'patient data', 'Spondyr API') to broaden trigger term coverage beyond 'Spondyr data'.

Dimension	Reasoning	Score
Specificity	Names the Spondyr domain and one concrete action ('Manage Organizations') but offers no further actions, matching the '1-2 concrete actions, not comprehensive' anchor rather than the multi-action score 4.	3 / 5
Completeness	Both 'what' ('Manage Organizations') and 'when' ('Use when the user wants to interact with Spondyr data') are present and explicit, but the 'what' is thin so it falls short of the comprehensive score-5 anchor.	4 / 5
Trigger Term Quality	'Spondyr data' and 'Organizations' are relevant natural terms a user might say, but there are few synonyms or variations, fitting 'some relevant keywords but missing common variations' rather than the fuller coverage at 4.	3 / 5
Distinctiveness Conflict Risk	Spondyr is a named niche application with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	15 / 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/spondyr/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.