Sync Clawdbot skills between local installation and the shared skill repository. Use when asked to install, update, list, or push skills.
Overall
score
88%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 well-structured description that clearly communicates both purpose and trigger conditions. The explicit 'Use when...' clause with specific action verbs makes skill selection straightforward. The main weakness is that the capabilities could be slightly more detailed about what each action (install, update, list, push) actually does.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clawdbot skills, skill repository) and mentions actions (install, update, list, push), but doesn't elaborate on what these actions entail or provide comprehensive detail about the sync process. | 2 / 3 |
Completeness | Clearly answers both what ('Sync Clawdbot skills between local installation and the shared skill repository') and when ('Use when asked to install, update, list, or push skills') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'install', 'update', 'list', 'push', 'skills', 'sync'. These are common verbs users would naturally use when managing skills. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche - Clawdbot skill management with clear triggers (install/update/list/push skills). The 'Clawdbot' and 'skill repository' terms make it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 skill that efficiently documents a CLI tool with concrete, executable commands. The security warning is appropriately prominent. The main weakness is the push workflow could benefit from explicit validation/verification steps after the PR is created.
Suggestions
Add verification step to push workflow: 'After pushing, verify PR was created: `gh pr view` or check the URL output'
Consider adding error handling guidance for common failures (e.g., 'If push fails with permission error, ensure you have write access to the repo')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary information. No unnecessary explanations of what skills are or how git works - assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands for every operation. The quick reference and examples sections give executable bash commands with clear syntax. | 3 / 3 |
Workflow Clarity | Commands are clearly documented but the push workflow lacks explicit validation steps. No feedback loop for verifying the PR was created successfully or handling push failures. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections: quick reference for immediate use, detailed command docs, configuration, and examples. Appropriate length for a single-file skill with no need for external references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
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.