endaoment

Donate to 501(c)(3) charities onchain via Endaoment - tax-deductible crypto donations

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/endaoment/SKILL.md

Quality

Content

87%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 lean, well-structured, and highly actionable, but the irreversible onchain donation workflow is missing explicit validation/verification steps, which caps workflow clarity.

Suggestions

Add an explicit numbered workflow with validation checkpoints, e.g. 1. search by name/EIN, 2. run /donate info to verify the charity, 3. approve USDC, 4. donate, 5. confirm the transaction onchain.

Include a pre-donation validation step that confirms the EIN resolves to a valid 501(c)(3) and that the wallet has sufficient USDC on Base.

Note the irreversibility of onchain donations and recommend confirming the amount with the user before executing large donations.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: tables for contracts, commands, and charities, brief examples, and a short setup note, with no padding explaining concepts Claude already knows. Every token earns its place.	5 / 5
Actionability	Fully executable commands (/donate search, info, approve, <EIN> <amount>) with concrete contract and USDC addresses, plus copy-paste ready examples covering common cases.	5 / 5
Workflow Clarity	Commands are listed but the irreversible financial donation flow lacks an explicit sequenced workflow with validation checkpoints (e.g. search -> verify info -> approve -> donate -> confirm); per rubric guidance, a destructive/financial operation without validation caps workflow clarity at 3.	3 / 5
Progressive Disclosure	A simple, under-50-line single-purpose skill with no external references needed and well-organized sections (Contracts, Commands, Popular Charities, Examples, Fees, Setup); meets the simple-skill exception for progressive disclosure.	5 / 5
	Total	18 / 20 Passed

Description

70%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 specific and occupies a distinct niche, but it lacks an explicit 'Use when...' trigger clause, which caps completeness. Adding concrete trigger phrases would raise the score.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to donate crypto to a charity or nonprofit, or mentions tax-deductible onchain giving.'

Broaden keyword coverage with synonyms like 'nonprofit' and 'give' to match more natural phrasings.

Optionally enumerate the concrete sub-actions (search, get info, approve, donate) to strengthen specificity.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Donate to 501(c)(3) charities') with specific mechanisms ('onchain via Endaoment', 'tax-deductible crypto donations'), though it is essentially one action verb with rich modifiers rather than a list of several actions.	4 / 5
Completeness	Has a clear 'what' (donate to charities onchain via Endaoment, tax-deductible crypto donations) but no 'Use when...' clause or equivalent explicit trigger guidance, so 'when' is only weakly implied.	3 / 5
Trigger Term Quality	Natural terms a user would say are present ('Donate', 'charities', 'tax-deductible', 'crypto donations'), but common synonyms like 'nonprofit' or 'give' are missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche (onchain 501(c)(3) crypto donations via Endaoment) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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: alsk1992/CloddsBot
Path: src/skills/bundled/endaoment/SKILL.md
Commit: c930628

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.