write-ok

Write a deterministic OK file to out/ok.txt.

Quality

73%

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 ./examples/evaluation/skill/skills/write-ok/SKILL.md

Quality

Content

100%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 model of brevity and actionability for a simple skill: a clear overview, an executable command backed by a real script, and an explicit output-file listing. Nothing is missing for its scope.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean with no padding or explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	It provides a single copy-paste-ready command, `bash scripts/write_ok.sh`, that fully executes the task, and the referenced script is real and complete.	5 / 5
Workflow Clarity	This is a simple single-action skill where the one action (run the script) is unambiguous, satisfying the simple-skill exception for a 5; no destructive or batch operation requires a validation loop.	5 / 5
Progressive Disclosure	Under 50 lines with well-organized sections (Overview, Command, Output Files) and a single real one-level reference to scripts/write_ok.sh, meeting the simple-skill exception for progressive disclosure.	5 / 5
	Total	20 / 20 Passed

Description

46%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 concrete and unambiguous about what it does but omits any "when to use" trigger guidance and lacks natural user-facing keywords. It is distinctive but would be hard for a user to discover by intent.

Suggestions

Add a 'Use when...' clause stating when this skill should be invoked, e.g. 'Use when a downstream step needs a deterministic OK marker file for validation.'

Replace jargon like 'deterministic OK file' with natural trigger phrases a user would say, such as 'write an OK validation file' or 'create a success marker file'.

Clarify the action vocabulary with a few synonyms (e.g. 'create', 'write', 'emit an OK marker') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Write a deterministic OK file to out/ok.txt" names a single concrete action with a precise output path, but only covers one action rather than a comprehensive set.	3 / 5
Completeness	It clearly states what the skill does but provides no "Use when..." trigger guidance, so per the missing-trigger cap it cannot exceed 3.	3 / 5
Trigger Term Quality	Terms like "deterministic OK file" and "out/ok.txt" are technical/jargon and lack the natural phrases a user would actually say to invoke this skill.	2 / 5
Distinctiveness Conflict Risk	The purpose is highly niche and tied to a specific output artifact, giving it low overlap risk, though the weak trigger terms leave a minor chance of misfiring.	4 / 5
	Total	12 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: trpc-group/trpc-agent-go
Path: examples/evaluation/skill/skills/write-ok/SKILL.md
Commit: 9f7e561

Reviewed: ~16 hours 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.