skill-creator

Guide for creating effective skills. Use when creating or updating a skill.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./runtime/harnesses/src/embedded-skills/skill-creator/SKILL.md

Quality

Content

78%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 a concise, well-structured authoring guide with concrete paths, format requirements, a ready template, and built-in validation/iteration steps. It is appropriately scoped for a simple meta-skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with only minor over-explanation (e.g. step 4's restatement of the embedded-skills caveat) that could be trimmed.	4 / 5
Actionability	Provides concrete, executable guidance — specific paths (skills/<skill-id>/), required frontmatter fields, and a copy-paste SKILL.md template — with only minor gaps.	4 / 5
Workflow Clarity	A clear 10-step sequence with an explicit validation step (step 9) and feedback loop (step 10); it is not a destructive/batch operation so the cap does not apply, but checkpoints are not as explicit as the score-5 anchor.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references and well-organized sections plus an inline template; per the simple-skill exception this earns the top score.	5 / 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 is third-person, concise, and answers both what and when with an explicit 'Use when' clause. Its main weakness is limited trigger-term variety and only modest action specificity.

Suggestions

Add concrete trigger phrases users would actually say, e.g. 'Use when the user asks to create, scaffold, or update a reusable skill'.

Expand the 'what' with a couple more concrete actions (e.g. 'define frontmatter, structure helper files, validate the skill').

Include natural synonyms such as 'scaffold', 'author', or 'skill template' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('creating effective skills') and two concrete actions ('creating or updating'), matching the score-3 anchor of domain plus 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Explicitly states both what ('Guide for creating effective skills') and when ('Use when creating or updating a skill'); the when is present and explicit but less specific than the multi-trigger score-5 example.	4 / 5
Trigger Term Quality	Contains relevant natural terms ('creating', 'updating', 'skill') a user might say, but lacks common synonyms or variations, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (skill authoring) with distinct triggers and only minor overlap risk with general coding/authoring skills, matching the score-4 anchor.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: holaboss-ai/holaOS
Path: runtime/harnesses/src/embedded-skills/skill-creator/SKILL.md
Commit: 4684714

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.