Content
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-organized skill that clearly communicates the Endaoment donation interface. Its main weaknesses are the lack of explicit workflow sequencing with validation steps (important for financial transactions) and the ambiguity around whether the slash commands are pre-built tools or need implementation. The command reference format is clean but would benefit from a clear step-by-step donation flow with confirmation checkpoints.
Suggestions
Add an explicit numbered workflow: 1) Search/verify charity → 2) Check USDC balance → 3) Approve USDC if needed → 4) Execute donation → 5) Verify transaction success
Clarify whether the /donate commands are pre-existing tool integrations or need to be implemented, and if the latter, provide the actual contract ABI calls or SDK code
Add validation checkpoints for the financial operations, such as confirming the org fund exists on-chain before donating and verifying transaction receipts after submission
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. Every section serves a purpose—contract addresses, commands, examples, fees—with no unnecessary explanation of what USDC, Base, or 501(c)(3) charities are. Every token earns its place. | 3 / 3 |
Actionability | The skill provides clear command syntax and examples, but lacks executable code showing how the smart contract interactions actually work (e.g., ABI calls, approval transactions, how the registry lookup is performed). The slash commands suggest a pre-built tool interface but there's no indication of the underlying implementation or how Claude should execute these. | 2 / 3 |
Workflow Clarity | The implicit workflow (search → info → approve → donate) is discernible from the commands but never explicitly sequenced. There are no validation checkpoints—e.g., checking approval status before donating, verifying the EIN resolves to a valid org fund, or confirming transaction success. For financial/destructive operations, this lack of explicit validation caps the score. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~50 lines), the content is well-organized into logical sections (contracts, commands, examples, fees, setup) with clear headers. No external references are needed and the structure supports easy scanning. | 3 / 3 |
Total | 10 / 12 Passed |