CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

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

Quality

Content

65%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 body is compact and well-organized, but it functions as a quality checklist rather than the promised template: it describes what a good skill contains without showing one. Adding a concrete SKILL.md template/example and a validation step would close the main gaps.

Suggestions

Include an actual SKILL.md template or worked example (frontmatter + body) since the skill bills itself as 'template + checklist' but ships only the checklist.

Add a validation step to the authoring checklist (e.g., verify the resulting SKILL.md meets the design goals or passes the checklist before finishing).

Either make the 'Design goals' bullets actionable guidance or fold them into the checklist so every section earns its tokens.

DimensionReasoningScore

Conciseness

The body is lean with no padding and no explanations of general concepts, matching 'efficient; minor instances of over-explanation'; the 'Design goals' bullets are aspirational adjectives with no instructional payoff and could be trimmed or made actionable.

4 / 5

Actionability

The checklist gives some specific guidance ('at least 2 realistic user prompts', 'Include "Setup" steps') but the skill claims to be a 'template + checklist' while providing no template, example SKILL.md, or frontmatter example, matching 'some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

The numbered authoring checklist provides a rough sequence (purpose → inputs/outputs → setup → examples → safety) but has no validation or verification checkpoint (nothing confirms the design goals are met), matching 'steps listed but validation gaps'.

3 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and has well-organized sections, which the rubric's simple-skill exception scores as 5.

5 / 5

Total

15

/

20

Passed

Description

65%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 has an explicit and well-formed 'Use when' trigger clause and a clear niche, but the capability statement is generic — it says the skill is a 'guide' without naming any concrete actions. Adding 2-3 specific actions would raise both specificity and completeness.

Suggestions

Replace the generic 'Guide for creating effective skills' with 2-3 concrete actions, e.g., 'Scaffolds skill folders, drafts SKILL.md frontmatter and body, and checks skills against an authoring checklist.'

Add natural trigger synonyms such as 'SKILL.md', 'add a skill', or 'make a skill' to broaden trigger-term coverage.

Tighten the 'when' clause to the concrete moments of use (creating a new skill vs. reviewing an existing one) rather than the broad 'specialized knowledge, workflows, or tool integrations' phrasing.

DimensionReasoningScore

Specificity

The description names the domain ("creating effective skills") but the only action stated is generic ("Guide for creating"), matching 'names the domain but actions are minimal or generic'; no concrete actions like scaffolding, validating, or generating are stated.

2 / 5

Completeness

It has both an explicit 'Use when users want to create or update a skill' trigger and a 'what' ("Guide for creating effective skills"), matching 'has both what and when; when could be more explicit'; it falls short of 5 because the 'what' is generic rather than a concrete capability list.

4 / 5

Trigger Term Quality

Natural phrases a user would say are present ("create or update a skill"), giving good keyword coverage, but a few natural terms/synonyms are missing (e.g., "SKILL.md", "add a skill", "scaffold"), so it matches 'good coverage; a few natural terms missing' rather than the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Skill creation for OpenCode is a distinct niche with clear triggers, matching 'mostly distinct; minor overlap risk' since broad terms like 'workflows' and 'tool integrations' could overlap with related skills.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Mirxa27/arabclue

Path

.opencode/skills/skill-creator/SKILL.md

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.