Name: donately
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

donately

Donately integration. Manage Organizations, Projects, Users. Use when the user wants to interact with Donately data.

Quality

67%

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

Quality

Content

68%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 skill body is highly actionable with executable CLI commands and a clear connection-state workflow. It loses points on conciseness (intro filler about what Donately is) and progressive disclosure (bulk action/field reference inlined rather than referenced).

Suggestions

Remove the opening "Donately is a fundraising platform..." paragraph; Claude already knows or can infer this, and it costs tokens without adding guidance.

Move the Popular actions table and the clientAction field schema into a separate references file (e.g., actions.md) and link to it from SKILL.md to improve progressive disclosure.

Add an explicit recovery loop for CONFIGURATION_ERROR / SETUP_FAILED (read error -> fix connection -> re-run ensure) to push workflow clarity to 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable CLI snippets, but includes Claude-known filler such as "Donately is a fundraising platform for nonprofits. It provides tools to create donation pages, manage campaigns, and engage donors," pushing it to anchor 3 rather than 4.	3 / 5
Actionability	Concrete, copy-paste-ready commands cover the common cases (login, connection ensure, action list/run, request proxy) and include JSON-output and parameter-passing variants, matching the fully-executable anchor 5.	5 / 5
Workflow Clarity	A clear sequence exists with a polling loop and explicit state outcomes (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), which is strong validation; it is capped just below 5 because there is no explicit "fix and re-validate" recovery loop for CONFIGURATION_ERROR.	4 / 5
Progressive Disclosure	The content is well sectioned, but the Popular actions table (~13 rows) and detailed clientAction field descriptions are inlined in SKILL.md with no external reference files to offload them, matching the anchor 3 example of inline content that could be split out.	3 / 5
	Total	15 / 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 is app-specific and third-person with an explicit Use-when clause, giving it solid completeness and distinctiveness. It is weakest on trigger-term breadth and action specificity, since "Manage" is generic and natural synonyms are absent.

Suggestions

Replace the generic verb "Manage" with concrete actions (e.g., "Create, list, and update Organizations, Projects, Users") to raise specificity.

Add natural trigger phrases and synonyms users say, such as "donations, donors, fundraisers, campaigns," so the description surfaces for more requests.

Tighten the "Use when" clause to name concrete intents (e.g., "Use when listing donors, creating campaigns, or retrieving donations from Donately").

Dimension	Reasoning	Score
Specificity	Quotes "Manage Organizations, Projects, Users" name the domain and three concrete entity types, but "Manage" is a generic verb so coverage is not comprehensive — matching anchor 3 rather than 4.	3 / 5
Completeness	Both "what" (manage Organizations, Projects, Users) and an explicit "when" ("Use when the user wants to interact with Donately data") are present; the "when" is generic, so it sits above anchor 3 but below a fully concrete anchor 5.	4 / 5
Trigger Term Quality	Natural keyword "Donately" plus entity terms ("Organizations, Projects, Users") are present, but common synonyms or extensions a user might say are missing, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	The app-specific name "Donately" combined with named entities carves a clear niche with minimal overlap risk, matching the anchor 5 example of a distinct trigger.	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/donately/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.