CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-scratch

Create a new scratch file in .agents/scratches/

Quality

68%

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 ./.opencode/skills/create-scratch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 delivers fully executable, copy-paste-ready commands with a clear workflow for a simple task, and is well sectioned. Its main weakness is repetition: the same framing and script-behavior details appear across the intro, Usage, Guidelines, and Begin sections.

Suggestions

Collapse the duplicated framing — merge the '## Begin' section and opening line into '## Your Task', since both restate the same instruction.

Trim the '## Guidelines' bullets that restate Usage-section details ('The unique ID ensures no filename conflicts', 'Files are automatically dated for organization') and keep only the actionable slug guidance.

DimensionReasoningScore

Conciseness

The commands and examples are lean, but the framing is stated three times ("You are creating a new scratch file", "## Your Task", "## Begin"), and the Guidelines section repeats Usage details ("The unique ID ensures no filename conflicts", "Files are automatically dated for organization"). This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4, where only minor trimming would be needed.

3 / 5

Actionability

Three copy-paste-ready commands cover the common input modes (direct argument, heredoc for multi-line, pipe), the output filename pattern and frontmatter format are shown concretely, and the slug-to-title transformation is illustrated ("quick-notes" → "Quick Notes"). This matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill and the single action is unambiguous: a clear 3-step sequence (determine slug → gather content → create file) with an explicit "Ask the user if unclear" checkpoint, and the script handles the rest deterministically. Per the simple-skill exception, workflow clarity can score 5; the operation is non-destructive, so no validation cap applies.

5 / 5

Progressive Disclosure

Sections are well-organized and logically ordered (Task, Usage, Creating the File, File Format, Guidelines) with no unnecessary external references for a skill this size. It falls short of 5 because the body exceeds 50 lines and carries duplicated framing content that could be trimmed or split, matching 'Good structure; most content is appropriately placed; minor organization gaps'.

4 / 5

Total

17

/

20

Passed

Description

42%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 states a single clear action in a specific location but omits any usage trigger, leaving the 'when' question unanswered and limiting natural keyword coverage. It is serviceable but would benefit most from an explicit invocation clause and a fuller inventory of what the skill handles.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g., 'Use when the user wants to save temporary notes, scratch ideas, or exploratory work.'

Enumerate what the skill actually does beyond file creation: slug derivation, unique three-word ID generation, automatic dating and title formatting of the scratch file.

Include natural trigger synonyms users would say ("scratch notes", "quick notes", "temporary ideas") to improve both keyword coverage and distinctiveness from generic note-taking skills.

DimensionReasoningScore

Specificity

"Create a new scratch file in .agents/scratches/" names the domain and one concrete action with a specific location, but lists no other capabilities (slug generation, ID, formatting), matching 'Names domain and 1-2 concrete actions, but not comprehensive'. It is below 4 because coverage stops at a single action.

3 / 5

Completeness

It has a clear 'what' (create a scratch file in a specific directory) but the 'when' is entirely absent, which caps completeness at 3 per the judging guidelines. Not 4 because no trigger guidance exists even implicitly.

3 / 5

Trigger Term Quality

The only keyword is "scratch file"; there is no "Use when" phrasing and no natural synonyms ("temporary notes", "quick notes", "idea dump") that a user would actually say. It sits between 'No natural keywords' and 'Some relevant keywords but missing common variations', closer to the former because the phrase is a bare filename operation rather than a natural trigger.

2 / 5

Distinctiveness Conflict Risk

The dedicated .agents/scratches/ location gives it a specific niche, but with no trigger terms it could overlap with general note-taking or file-creation skills, matching 'Somewhat specific but could still overlap with similar skills'. Not 4 because nothing in the description distinguishes when this skill applies over alternatives.

3 / 5

Total

11

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

LibPDF-js/core

Path

.opencode/skills/create-scratch/SKILL.md

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.