endaoment

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

Quality

72%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/endaoment/SKILL.md

Quality

Discovery

N/A

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

Something went wrong

Implementation

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is concise and well-structured for its scope, with clear contract addresses and command syntax. However, it lacks executable code showing how the slash commands actually interact with the smart contracts, and the workflow could benefit from explicit sequencing and validation checkpoints for financial transactions.

Suggestions

Add executable code showing how to call the smart contracts (e.g., ethers.js or viem examples for approval and donation transactions)

Include an explicit workflow sequence: 1) Search/verify charity 2) Check USDC balance 3) Approve if needed 4) Execute donation 5) Verify transaction success

Add validation guidance for checking approval status before donating and confirming transaction completion

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient - no unnecessary explanations of what charities are, how crypto works, or what USDC is. Every line provides actionable information Claude needs.	3 / 3
Actionability	Commands are clearly listed with examples, but they appear to be slash commands without showing the underlying implementation. No executable code for the actual donation flow (contract calls, ABI interactions) is provided.	2 / 3
Workflow Clarity	The sequence is implied (search → info → approve → donate) but not explicitly stated. Missing validation steps - no guidance on checking approval status, verifying transaction success, or handling failures.	2 / 3
Progressive Disclosure	For a skill under 50 lines with a focused purpose, the content is well-organized with clear sections (contracts, commands, examples, fees, setup). No need for external references given the scope.	3 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: 2a8c94e

Reviewed: 29 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.