CtrlK
BlogDocsLog inGet started
Tessl Logo

fastclaw-skill-guide

Create new skills for FastClaw agents. Use when the user asks to create a skill, turn a workflow into a skill, or build reusable automation. Also use when discussing skill format, structure, or best practices.

66

Quality

78%

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 ./skills/fastclaw-skill-guide/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The content is a clear, well-organized guide that explains skill structure, storage, and progressive disclosure effectively. Its weakness is mild redundancy between the inline frontmatter example and the field table, and the workflow steps lack explicit validation checkpoints.

Suggestions

Replace the placeholder frontmatter in the template with at least one fully-populated, realistic example so the guidance is copy-paste ready.

Add an explicit validation checkpoint in Creation Steps — e.g., a concrete command or expected load_skill output that signals success before considering the skill done.

Trim redundancy between the inline frontmatter code block and the Frontmatter Fields table, or cross-reference one from the other to reduce token cost.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-structured, but the frontmatter table and the full inline frontmatter example repeat field definitions, and some explanatory prose ("Guide for creating new skills...") restates what the heading already conveys.

2 / 3

Actionability

Concrete examples (a full SKILL.md template, the git-pr-review example) are present, but the main template uses placeholder values and the example's output-format section is left as labeled stubs rather than fully executable guidance.

2 / 3

Workflow Clarity

The five-step "Creation Steps" sequence is listed, but checkpoints are implicit and the "Verify" step lacks a concrete validation command or error-recovery loop beyond calling load_skill.

2 / 3

Progressive Disclosure

No bundle files exist and the skill is well under the 500-line limit; sections are clearly organized and the Three-Level Loading model explains the disclosure model, which is appropriate for a guide of this size.

3 / 3

Total

9

/

12

Passed

Description

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.

The description is strong: third-person, specific, and equipped with explicit "Use when" trigger clauses covering both creation and discussion contexts. It is concise yet comprehensive with no over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Create new skills," "turn a workflow into a skill," and "build reusable automation" — rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both what it does and when to use it via the "Use when the user asks..." and "Also use when discussing..." clauses, with explicit trigger guidance.

3 / 3

Trigger Term Quality

Covers natural phrases a user would say ("create a skill," "turn a workflow into a skill," "skill format, structure, or best practices") with good variation across trigger contexts.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — authoring FastClaw skills — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fastclaw-ai/fastclaw
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.