CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

daily-tile

Colour one new tile in tiles.js each day

Quality

76%

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 ./skills/daily-tile/skills/daily-tile/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 is a strong example of a compact operational skill: deterministic rules, copy-paste commands, error recovery, and a pre-push checklist. The only meaningful gap is a lack of verification around the destructive array-reset path and between the edit and the push.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no explanations of concepts Claude already knows — it goes straight to constraints, formulas, and commands. Minor instances of padding ("read these carefully", "this is critical — do not skip", repeated emphatic reminders) keep it at anchor 4 rather than 5.

4 / 5

Actionability

Everything is executable: a copy-paste git remote set-url command with the real repo URL, deterministic formulas (col = N % 28, row = Math.floor(N / 28)), an exact commit message format with an example, and a concrete specialTiles code block. The #YOUR_COLOR placeholder and subjective colour choice are explicitly justified flexibility, not gaps, so this matches anchor 5.

5 / 5

Workflow Clarity

The sequence is clear (read tiles.js → count entries → compute position → edit → commit → push) with a 403 error-recovery branch and a final pre-push checklist serving as validation checkpoints. Anchor 4 rather than 5 because the destructive reset case (N >= 448 → delete ALL entries) has no verification step before deletion, and there is no diff/check step between the edit and the push.

4 / 5

Progressive Disclosure

This is a simple, single-purpose, self-contained skill with no bundle files and well-organized sections (constraints, tile selection, colour, edit, commit/push, checklist); per the simple-skill exception, well-organized sections with no need for external references score 5.

5 / 5

Total

18

/

20

Passed

Description

53%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 concise and names a specific file and action, but it omits any usage guidance. Adding an explicit "Use when..." clause and a hint at the fuller workflow (edit, commit, push) would materially improve completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when running the daily tile ritual, when the user asks to colour/add today's tile, or when a scheduled daily task fires" — this directly lifts completeness and trigger_term_quality.

Mention the full capability set in the "what" (edit tiles.js, commit with the tile message format, push to main) so specificity reflects what the skill actually does rather than only the edit step.

Include natural synonyms such as "bathroom wall tile", "daily tile", and "specialTiles" so users' varied phrasings match the description.

DimensionReasoningScore

Specificity

"Colour one new tile in tiles.js each day" names the domain (tiles.js) and exactly one concrete action, but says nothing about the rest of what the skill does (edit, commit, push, reset). This matches anchor 3 (domain + 1-2 concrete actions, not comprehensive); not 4 because coverage is a single action with no mention of the surrounding workflow.

3 / 5

Completeness

It has a clear "what" (colour one new tile in tiles.js per day) but no "when" — no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

Keywords present are "tile", "tiles.js", "colour", and "each day" — some relevant terms, but missing the natural phrasings a user would actually say ("add a tile", "bathroom wall", "daily tile", "commit a tile"). Anchor 3 (some relevant keywords, missing variations); not 4 because there are no synonyms or natural request forms beyond the bare noun.

3 / 5

Distinctiveness Conflict Risk

The reference to a specific file ("tiles.js") plus the daily cadence gives it a narrow niche with low conflict risk against unrelated skills. Anchor 4 (mostly distinct, minor overlap risk); not 5 because there are no distinct trigger phrases and it could be confused with generic styling/colouring or repo-maintenance skills.

4 / 5

Total

13

/

20

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

Validation for skill structure

No warnings or errors.

Repository

macebake/faucet-simulator

Path

skills/daily-tile/skills/daily-tile/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.