CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-writer

Create and improve agent skills following the Agent Skills specification. Use when asked to create, write, or update skills.

53

Quality

60%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/skill-writer/SKILL.md

The canonical home for this skill is skill-writer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%Scale 1-5

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

This is a well-structured meta-skill (skill for writing skills) that serves primarily as an orchestration document routing to detailed reference files. Its strengths are clear workflow sequencing, efficient task-to-reference mapping, and appropriate progressive disclosure. Its main weakness is that almost all actionable content is deferred to reference files, making the SKILL.md itself more of a table of contents than a standalone guide—without the bundle files, a reader would struggle to execute any step.

Suggestions

Add at least one concrete inline example of a key artifact (e.g., a minimal SKILL.md template or a sample frontmatter block) so the skill has some standalone actionability without requiring reference file access.

Include explicit validation criteria or a checklist inline for the depth gates mentioned in Steps 2 and 7, rather than fully deferring to reference files, so Claude can perform basic validation without loading additional context.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient with a well-structured table for task-to-reference mapping and numbered steps that avoid excessive explanation. Minor verbosity exists in some step descriptions (e.g., 'Primary success condition' preamble, 'Skip this step when selected path does not include iteration'), but overall it respects Claude's intelligence.

4 / 5

Actionability

The skill provides a clear sequence of steps with sub-steps, but nearly all concrete guidance is deferred to reference files (e.g., 'Read references/synthesis-path.md'). The SKILL.md itself contains no executable code, no concrete examples, and no specific commands—it's essentially a routing document. The sub-steps describe what to do at a high level but lack the specifics needed to execute without the reference files.

3 / 5

Workflow Clarity

The 7-step workflow is clearly sequenced with logical progression from classification through synthesis, authoring, optimization, evaluation, and registration. Step 3 includes a conditional skip, and Step 7 includes validation/rejection gates. However, explicit validation checkpoints and feedback loops within steps are mostly delegated to reference files rather than stated inline, creating minor gaps.

4 / 5

Progressive Disclosure

The skill uses a well-organized table mapping tasks to specific reference files, with clear one-level-deep references. The structure is logical and navigable. However, since no bundle files were provided, we cannot verify that the referenced files exist or are well-structured. The pattern of references is appropriate for a meta-skill of this complexity, though the inline content could include slightly more substance to be useful without immediately loading references.

4 / 5

Total

15

/

20

Passed

Description

53%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 functional but lean, providing a basic 'what' and 'when' without enough specificity to confidently distinguish it in a large skill library. It correctly uses third person voice and includes a 'Use when' clause, but the actions described are generic and the trigger terms lack natural variations and domain-specific keywords like 'SKILL.md' or 'skill file'.

Suggestions

Add concrete actions such as 'generates YAML frontmatter, writes markdown instructions, defines trigger terms and descriptions' to improve specificity.

Expand trigger terms to include natural variations like 'SKILL.md', 'skill file', 'skill template', 'new capability', or 'define a skill'.

Improve distinctiveness by referencing the specific artifact type (e.g., 'SKILL.md files') and the specification format to reduce overlap with general file creation skills.

DimensionReasoningScore

Specificity

Names the domain ('agent skills') and mentions 'create and improve' as actions, but these are generic verbs without concrete details about what creating or improving entails (e.g., generating YAML frontmatter, writing markdown instructions, defining trigger terms).

2 / 5

Completeness

Has both 'what' (create and improve agent skills following the Agent Skills specification) and 'when' (when asked to create, write, or update skills), though the 'when' clause could be more specific with additional trigger scenarios like 'when the user wants to define a new capability' or 'when editing SKILL.md files'.

4 / 5

Trigger Term Quality

Includes some relevant keywords like 'skills', 'create', 'write', 'update', but misses natural variations users might say such as 'skill file', 'SKILL.md', 'skill template', 'skill description', 'add a new skill', or 'edit skill'.

3 / 5

Distinctiveness Conflict Risk

The term 'skills' is somewhat specific to this domain, but 'create' and 'write' are very broad verbs that could overlap with many other skills. Without mentioning specific artifacts like 'SKILL.md' or 'skill files', there's moderate overlap risk with general code/file creation skills.

3 / 5

Total

12

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.