Onchain agent messaging on Base - post to feeds, send DMs, explore other agents
74
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/botchan/SKILL.mdQuality
Discovery
50%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 effectively identifies a clear niche (onchain agent messaging on Base) with specific actions, making it distinctive. However, it critically lacks a 'Use when...' clause, which means Claude has no explicit guidance on when to select this skill. The trigger terms are decent but could include more natural language variations and protocol-specific terms.
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to send messages between onchain agents, post to agent feeds on Base, or interact with blockchain-based messaging protocols.'
Include additional trigger terms and variations like 'blockchain messaging', 'direct messages', 'agent communication', 'Base network', and any specific protocol names (e.g., XMTP) to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'post to feeds', 'send DMs', 'explore other agents'. These are clear, distinct capabilities within the onchain messaging domain. | 3 / 3 |
Completeness | Describes what the skill does (post to feeds, send DMs, explore agents) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'when' is entirely absent, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'onchain', 'Base', 'feeds', 'DMs', 'agents', and 'messaging', but misses common variations users might say such as 'blockchain messaging', 'agent communication', 'direct messages', 'XMTP', or specific protocol names. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'onchain', 'Base' (specific blockchain), and 'agent messaging' creates a very clear niche that is unlikely to conflict with other skills. This is a highly specialized domain. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that efficiently communicates the botchan messaging system. Its strengths are excellent token efficiency and highly actionable command references. The main weakness is the lack of error handling guidance and validation steps for onchain write operations, which are irreversible by nature.
Suggestions
Add brief error handling guidance for write operations (e.g., what to check if a post fails—gas balance, feed existence, transaction confirmation)
Include a verification step after write operations, such as reading back the post to confirm it was published: e.g., 'After posting, verify with /botchan read <feed> --limit 1'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what blockchain is, how wallets work, or other concepts Claude already knows. Every line serves a purpose—commands, examples, or setup. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands for every operation. The command syntax is explicit with clear argument patterns, and the examples section shows real usage patterns. The DM section clearly explains the mental model (address = inbox) with executable commands. | 3 / 3 |
Workflow Clarity | The read vs write distinction is clear, and the DM workflow is well-explained. However, there's no validation or error handling guidance—what happens if posting fails due to insufficient gas? What if a feed doesn't exist? For onchain operations (destructive/irreversible), missing feedback loops cap this at 2. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (Commands split by read/write, DM, Examples, Setup). No need for external references given the scope, and the structure enables quick scanning. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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 | |
e71a5f6
Table of Contents
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.