CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-skills

Use when creating, updating, or improving agent skills.

48

Quality

51%

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/writing-skills/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 dispatcher skill that efficiently routes users to the right template and standards for skill creation. Its strengths are the clear decision tree, concrete examples (bash commands, YAML frontmatter), and comprehensive pre-deploy checklist. Its main weakness is that most actionable content is delegated to referenced files that weren't provided for verification, and there's minor redundancy between sections.

Suggestions

Remove the 'How It Works' section or merge it into the decision tree, as it largely restates the same flow in a less useful format.

Add a brief feedback loop to the workflow: what to do when testing reveals the skill isn't triggering or is being ignored (beyond just linking to other references).

DimensionReasoningScore

Conciseness

The skill is mostly efficient, using tables, decision trees, and checklists to convey information densely. Minor verbosity in the 'How It Works' section which restates what the decision tree already covers, and the 'When to Use' section is somewhat redundant with the opening line. But overall it respects Claude's intelligence and avoids explaining basic concepts.

4 / 5

Actionability

Provides concrete directory structures, bash commands for creating skills, a YAML frontmatter example, and a pre-deploy checklist with specific criteria. However, the actual skill-writing guidance is delegated entirely to referenced files (templates, CSO, anti-rationalization), so the SKILL.md itself is more of a dispatcher than a hands-on guide. The inline examples are concrete but minimal.

4 / 5

Workflow Clarity

The 'How It Works' section provides a clear 5-step sequence, and the decision tree gives unambiguous routing. The pre-deploy checklist serves as a validation checkpoint. However, there's no explicit feedback loop or error recovery step (e.g., what to do if a skill fails testing), which is a minor gap for a workflow that includes a testing step.

4 / 5

Progressive Disclosure

Excellent structure as a dispatcher with clear one-level-deep references to templates, standards, CSO, anti-rationalization, and testing guides. The component index table and template list are well-organized for navigation. Scored 4 instead of 5 because no bundle files were provided to verify that referenced paths actually exist, and there's some redundancy between the decision tree, component index, and templates sections that could be consolidated.

4 / 5

Total

16

/

20

Passed

Description

27%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.

This description is essentially just a trigger clause with no explanation of what the skill actually does. It lacks concrete actions, specific capabilities, and sufficient trigger terms to reliably distinguish it from other skills. The description needs substantial expansion to be useful for skill selection.

Suggestions

Add a 'what' clause before the 'Use when' that describes concrete actions, e.g., 'Creates and edits SKILL.md files including YAML frontmatter, description fields, and instructional content for agent skills.'

Include more specific trigger terms and synonyms such as 'skill files', 'SKILL.md', 'skill description', 'skill definition', 'markdown skill', or 'skill template'.

Specify what distinguishes this skill from general writing or editing skills, e.g., mention the specific file format, structure, or validation rules involved.

DimensionReasoningScore

Specificity

The description contains no concrete actions—'creating, updating, or improving' are extremely generic verbs, and 'agent skills' is vague without specifying what actions are actually performed (e.g., writing markdown files, editing YAML frontmatter, testing skill behavior).

1 / 5

Completeness

The description only provides a 'when' clause ('Use when...') but has no 'what' component explaining what the skill actually does. There is no explanation of capabilities or concrete outputs.

2 / 5

Trigger Term Quality

The phrase 'agent skills' is a relevant keyword, and 'creating, updating, improving' are natural terms a user might use. However, it lacks synonyms or variations like 'skill files', '.md files', 'skill description', 'SKILL.md', or 'skill definition'.

3 / 5

Distinctiveness Conflict Risk

'Agent skills' is somewhat specific to a domain, but 'creating, updating, or improving' is so broad that it could overlap with many other skills related to writing, editing, or code generation. Without specifying the format, tooling, or concrete deliverables, conflict risk is high.

2 / 5

Total

8

/

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.