CtrlK
BlogDocsLog inGet started
Tessl Logo

clawddocs

Clawdbot documentation expert with decision tree navigation, search scripts, doc fetching, version tracking, and config snippets for all Clawdbot features

76

5.68x
Quality

66%

Does it follow best practices?

Impact

91%

5.68x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./clawdbot/clawddocs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%Scale 1-3

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

This is an excellent skill that efficiently teaches Claude how to navigate and use Clawdbot documentation. It combines a clear decision tree for routing questions, executable scripts for discovery, organized documentation categories, and concrete examples with config snippets. The structure is scannable and actionable without any unnecessary verbosity.

DimensionReasoningScore

Conciseness

The skill is lean and efficient, using bullet points, code blocks, and structured sections without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context.

3 / 3

Actionability

Provides fully executable bash commands, specific file paths, and copy-paste ready config snippets. The example interactions show concrete workflows with actual JSON configuration.

3 / 3

Workflow Clarity

Clear 5-step workflow with explicit sequence (identify → search → fetch → reference → cite). The decision tree provides unambiguous routing for different user needs, and example interactions demonstrate the complete process.

3 / 3

Progressive Disclosure

Well-organized with clear sections, references to external files (snippets/common-configs.md), and one-level-deep navigation to documentation categories. The structure allows quick scanning while pointing to detailed resources.

3 / 3

Total

12

/

12

Passed

Description

32%Scale 1-3

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 identifies a specific product domain (Clawdbot) and lists several capability areas, but suffers from missing explicit trigger guidance and somewhat abstract action descriptions. The lack of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill, and the listed features read more like a feature list than actionable capabilities.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Clawdbot setup, configuration, features, or needs help navigating Clawdbot documentation'

Include natural user phrases as trigger terms: 'Clawdbot help', 'Clawdbot docs', 'how to configure Clawdbot', 'Clawdbot features'

Make capabilities more concrete by specifying user outcomes: 'Fetches official Clawdbot documentation, provides configuration examples, and guides users through feature setup'

DimensionReasoningScore

Specificity

Names the domain (Clawdbot documentation) and lists several actions (decision tree navigation, search scripts, doc fetching, version tracking, config snippets), but these are somewhat abstract and don't explain what concrete tasks a user would accomplish.

2 / 3

Completeness

Describes what it does (documentation expert with various features) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.

1 / 3

Trigger Term Quality

Includes 'Clawdbot' and 'documentation' as relevant keywords, but lacks natural user phrases like 'how do I configure', 'help with Clawdbot', 'docs', or common variations users would actually say when seeking help.

2 / 3

Distinctiveness Conflict Risk

'Clawdbot' is a specific product name which helps distinctiveness, but 'documentation expert' is generic and could overlap with other documentation-related skills without clearer trigger boundaries.

2 / 3

Total

7

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
bap-jorkim/agent-skills-fork-feb-25
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.