write-ok
Write a deterministic OK file to out/ok.txt.
61
51%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/evaluation/skill/skills/write-ok/SKILL.mdQuality
Discovery
17%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 extremely terse and task-specific, describing a single narrow action without context, trigger terms, or a 'Use when' clause. It reads more like a command than a skill description, making it difficult for Claude to know when to select it from a pool of skills. The lack of natural user-facing keywords and explicit trigger guidance are its biggest weaknesses.
Suggestions
Add a 'Use when...' clause explaining the scenarios or user requests that should trigger this skill, e.g., 'Use when the user requests a health check file, status confirmation, or build verification output.'
Include natural trigger terms that users might actually say, such as 'health check', 'status file', 'build ok', or 'verification output'.
Expand the 'what' portion to explain the purpose of the OK file—e.g., 'Generates a deterministic status confirmation file at out/ok.txt to signal successful completion of a build or process.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names a specific action ('write a deterministic OK file') and a specific output path ('out/ok.txt'), but describes only a single narrow action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | It states what the skill does (write an OK file) but provides no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when' clause caps completeness at 2, and the 'what' is also minimal, so this scores a 1. | 1 / 3 |
Trigger Term Quality | The description lacks natural keywords a user would say. Terms like 'deterministic OK file' and 'out/ok.txt' are highly specific internal jargon, not phrases users would naturally use in requests. | 1 / 3 |
Distinctiveness Conflict Risk | The very specific output path 'out/ok.txt' and the unusual term 'deterministic OK file' make it somewhat distinctive, but the description is so terse that it's unclear what domain or context it belongs to, which could cause confusion. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a minimal, well-structured skill for a trivial task. Its main weakness is that it references an external script (`scripts/write_ok.sh`) without showing its contents, which reduces actionability since Claude cannot verify or reproduce the behavior without seeing the script. The conciseness and organization are appropriate for the task's simplicity.
Suggestions
Include the script content inline or show the equivalent command (e.g., `mkdir -p out && echo OK > out/ok.txt`) so the skill is fully self-contained and executable without needing to inspect an external file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is very short and lean. Every line serves a purpose. No unnecessary explanation of concepts Claude already knows. | 3 / 3 |
Actionability | It provides a concrete command to run (`bash scripts/write_ok.sh`), but doesn't show the actual script content or what it does internally. For a skill about writing 'OK' to a file, the script content or an inline equivalent (e.g., `echo OK > out/ok.txt`) would make it fully executable and copy-paste ready. | 2 / 3 |
Workflow Clarity | This is a single-step, non-destructive task (write a file). The single action is unambiguous: run one command, get one output file. No validation checkpoints are needed for this trivial operation. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single purpose, the content is well-organized with clear sections (Overview, Command, Output Files). No external references are needed. | 3 / 3 |
Total | 11 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.