CtrlK
BlogDocsLog inGet started
Tessl Logo

clawddocs

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

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

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

82%Weight 40%Scale 1-5

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

The content is highly actionable with real, copy-paste script commands and a clear workflow, organized into well-signaled sections; its main gaps are a broken snippet reference and minor padding.

Suggestions

Create the referenced './snippets/common-configs.md' (or a snippets/ directory) so the config-snippet reference resolves to a real file.

Remove the redundant Capability Summary line that duplicates the frontmatter description to save tokens.

Add an explicit verification checkpoint in the Workflow (e.g., 'Confirm the fetched doc addresses the user's question before answering').

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explanation of what OpenClaw is), with only minor padding such as the Capability Summary duplicating the frontmatter and decorative emoji headers.

4 / 5

Actionability

Provides copy-paste ready, verified-real script commands (e.g., './scripts/search.sh discord', './scripts/fetch-doc.sh gateway/configuration') plus a concrete JSON config snippet covering common cases.

5 / 5

Workflow Clarity

A clear 5-step Workflow sequence (identify → search → fetch → reference snippets → cite URL) is present; this is a read-only doc-lookup skill so no destructive/batch validation is required, but explicit checkpoints like confirming the fetched doc answers the question are missing.

4 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep references to real scripts in ./scripts/, but the referenced './snippets/common-configs.md' does not exist in the bundle and no references/ or assets/ directories are present.

4 / 5

Total

17

/

20

Passed

Description

62%Weight 40%Scale 1-5

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 states concrete capabilities and occupies a clear, low-conflict niche, but omits any explicit 'when to use' trigger guidance and leans on capability labels over natural user phrases.

Suggestions

Add a 'Use when...' clause with natural trigger phrases (e.g., 'Use when the user asks about OpenClaw setup, configuration, providers, or troubleshooting').

Include common synonyms users might say, such as 'OpenClaw docs', 'configure OpenClaw', or 'OpenClaw gateway/providers'.

Soften the over-claim 'for all OpenClaw features' to concrete feature areas to avoid inflated scope.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'decision tree navigation, search scripts, doc fetching, version tracking, and config snippets' — rather than vague language, though 'for all OpenClaw features' is a slight over-claim keeping it below 5.

4 / 5

Completeness

It clearly answers 'what' (documentation expert with listed capabilities) but provides no 'Use when...' trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

'OpenClaw documentation' is a natural term, but the description relies on capability names rather than the natural phrases and synonyms users would say, missing common variations.

3 / 5

Distinctiveness Conflict Risk

Tied to the distinct OpenClaw product niche with product-specific triggers, giving minimal overlap risk with other skills.

5 / 5

Total

15

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jdrhyne/agent-skills
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.