CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-creator

Guide for creating effective skills. Use when users want to create or update a skill that extends OpenCode with specialized knowledge, workflows, or tool integrations.

58

Quality

66%

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

Quality

Content

71%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 a lean, well-organized template-and-checklist with a clear sequenced workflow, but its guidance tells the author what to include rather than how to execute the build, and it lacks an explicit verification step.

Suggestions

Add a concrete execution step showing how to scaffold a skill (e.g., the exact folder/command to create the SKILL.md and structure), not just what it should contain.

Append a verification checkpoint to the checklist (e.g., 'Confirm the skill triggers on a sample prompt and loads without errors').

Provide a minimal SKILL.md template the author can copy, since the skill calls itself a 'template + checklist' but ships no template file.

DimensionReasoningScore

Conciseness

The body is lean (~40 lines) with no padding or explanation of concepts Claude already knows; the only mildly conceptual parts are the short 'What is a skill?' definition and 'Design goals' list, which keeps it just below the fully lean anchor.

4 / 5

Actionability

The authoring checklist gives specific, actionable items ('at least 2 realistic user prompts', 'avoid destructive defaults; ask for confirmation') and a concrete structure tree, but it describes what to include rather than how to build a skill, leaving guidance incomplete.

3 / 5

Workflow Clarity

The 5-step numbered authoring checklist is a clear sequence for a simple single-purpose skill (which can score highly), but it lacks an explicit verification checkpoint (e.g., 'confirm the skill loads/triggers'), a minor validation gap.

4 / 5

Progressive Disclosure

At under 50 lines with no need for external references and well-organized sections (What is a skill, Design goals, Recommended structure, Authoring checklist), the body meets the simple-skill exception for a top score; no bundle files exist to verify.

5 / 5

Total

16

/

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 cleanly states what the skill does and when to use it with an explicit trigger, but the capability framing is somewhat abstract and a few natural trigger synonyms are missing.

Suggestions

Replace the generic 'Guide for creating effective skills' with the concrete actions the skill performs (e.g., 'Scaffold, validate, and document new skills').

Add natural trigger synonyms such as 'build', 'make', or 'add a skill' alongside 'create or update a skill'.

Tighten 'extends OpenCode with specialized knowledge, workflows, or tool integrations' into a concrete outcome (e.g., 'that adds commands, workflows, or tool integrations to OpenCode').

DimensionReasoningScore

Specificity

Names the domain ('creating effective skills') and concrete actions ('create or update a skill'), but the rest ('specialized knowledge, workflows, or tool integrations') describes what skills contain rather than the skill's own actions, matching the anchor for domain + 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Both 'what' ('Guide for creating effective skills') and 'when' ('Use when users want to create or update a skill...') are present with the trigger explicit, but the 'what' is somewhat generic, so it is not a full 5.

4 / 5

Trigger Term Quality

'Use when users want to create or update a skill' is a natural trigger, and the extension categories add some coverage, but common variations like 'build', 'make', or 'add a skill' are missing, fitting the anchor for relevant keywords with missing synonyms.

3 / 5

Distinctiveness Conflict Risk

Skill creation is a clear meta-niche with the distinctive 'create or update a skill' trigger, with only minor overlap risk against general coding/editing skills; it is mostly distinct rather than fully conflict-free.

4 / 5

Total

14

/

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
Mirxa27/arabclue
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.