clawdnet
Register and manage AI agents on ClawdNet, the decentralized agent registry. Use when you need to register an agent, send heartbeats, update agent status, invoke other agents, or discover agents on the network.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the specific platform (ClawdNet), lists concrete actions (register, heartbeat, update status, invoke, discover), and includes an explicit 'Use when' clause with natural trigger terms. The description is concise, uses third person voice, and is highly distinctive due to the named platform and domain-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: register an agent, send heartbeats, update agent status, invoke other agents, discover agents on the network. | 3 / 3 |
Completeness | Clearly answers both 'what' (register and manage AI agents on ClawdNet, the decentralized agent registry) and 'when' (explicit 'Use when' clause listing specific trigger scenarios: register an agent, send heartbeats, update status, invoke agents, discover agents). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'register', 'agent', 'heartbeat', 'status', 'invoke', 'discover', 'ClawdNet', 'decentralized agent registry', 'network'. These are domain-specific but exactly what a user working with this system would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific product name 'ClawdNet' and domain-specific terms like 'decentralized agent registry', 'heartbeats', and 'invoke other agents'. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with concrete curl examples that Claude can immediately use. Its main weaknesses are the lack of validation/error-handling steps in the workflow (what happens when registration or heartbeats fail?) and some inline content that could be trimmed or moved to the referenced API doc. The referenced bundle file (references/api.md) is not provided, making it impossible to verify the progressive disclosure structure.
Suggestions
Add error handling and validation checkpoints to the Integration Pattern (e.g., check registration response status, handle heartbeat failures, verify claim_url was processed)
Move the Standard Capabilities list and detailed Discovery endpoints to references/api.md to keep SKILL.md leaner
Provide the referenced references/api.md bundle file so the progressive disclosure structure is complete
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with concrete curl examples, but includes some unnecessary content like the Standard Capabilities list (which is essentially a glossary Claude doesn't need) and the brief descriptions next to each capability ID add little value. The Environment Variables section is also somewhat obvious. | 2 / 3 |
Actionability | Provides fully executable curl commands with complete request bodies, headers, and example responses. The registration, heartbeat, invocation, and discovery endpoints are all copy-paste ready with concrete JSON payloads. | 3 / 3 |
Workflow Clarity | The Integration Pattern section provides a clear 4-step sequence, but lacks validation checkpoints. There's no guidance on what to do if registration fails, if heartbeats fail, or how to verify successful registration beyond saving the API key. For an API-based workflow involving agent registration and ongoing state management, explicit error handling and verification steps are missing. | 2 / 3 |
Progressive Disclosure | References 'references/api.md' for complete API documentation which is good structure, but no bundle files are provided so the reference is unverifiable. The main file includes inline content (Standard Capabilities, Discovery endpoints) that could arguably live in the referenced API doc, making the SKILL.md slightly heavier than needed. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
f45fcb5
- Reviewed
Table of Contents
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.