CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tile-creator

Create tessl tiles containing docs, rules, or skills. Use when a user wants to create a tile, package content for tessl, or needs help with tile.json configuration. Also triggers on "create tile from", "convert to tile", "turn into tile", "make tile from", or "tile this repo" for existing content.

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-built procedural skill: executable commands throughout, well-sequenced workflows with explicit lint-validation feedback loops, and clean one-level-deep reference structure. The main gaps are two unreferenced bundle scripts and minor duplication in the command examples.

Suggestions

Reference scripts/create-tile.sh and scripts/lint-tile.sh from the body (e.g., in the workflow steps or References section) — they exist in the bundle but are currently unreachable via navigation.

Deduplicate the 'tessl tile new' invocation: show it once with all flags (or point to cli-commands.md) instead of repeating near-identical blocks in both workflows.

Use generic placeholder versions in the purl examples (e.g., 'pkg:npm/<name>@<version>') instead of pinned versions like 'pkg:npm/openai@6.9.1' to avoid time-sensitive specificity.

DimensionReasoningScore

Conciseness

Lean overall — content-type table, terse numbered steps, no explanation of concepts Claude already knows. Minor trims possible: 'tessl tile new' appears twice with near-identical flags, the cli-commands.md pointer is repeated in both workflow and References, and illustrative purls embed specific version numbers ('pkg:npm/openai@6.9.1'). Fits anchor 4 (efficient, minor over-explanation) rather than 5.

4 / 5

Actionability

Fully executable guidance: copy-paste ready 'tessl tile new' commands with all flags, 'tessl tile lint', a complete tile.json JSON example, index.md templates, the '{ .api }' marker format, and purl formatting with normalization rules. Covers the common cases (from scratch, from existing source, packages) — a direct match for anchor 5.

5 / 5

Workflow Clarity

Both workflows are clearly sequenced with explicit validation checkpoints and feedback loops ('Fail → Fix errors → Re-run lint'), plus a final report step ('Summarize what was created, note any gaps or assumptions for user review'). Matches anchor 5's validate-fix-retry pattern; no gaps that would justify 4.

5 / 5

Progressive Disclosure

All five referenced files exist in references/, are one level deep, and are well-signaled both inline and in a dedicated References section. However scripts/create-tile.sh and scripts/lint-tile.sh exist in the bundle but are never mentioned in the body — orphaned files that hurt navigation. Anchor 4 (good structure, minor organization gaps) fits better than 5.

4 / 5

Total

18

/

20

Passed

Description

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

A strong description: third-person voice, concrete capabilities, explicit 'Use when' guidance, and an unusually rich set of natural trigger phrases including repo/package conversion variants. Only minor specificity gaps (validation/lint capabilities are not mentioned).

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Create tessl tiles containing docs, rules, or skills', 'package content for tessl', 'needs help with tile.json configuration' — with minor gaps (no mention of validation or conversion mechanics). Fits anchor 4 (several specific actions, minor gaps) rather than 3 (only 1-2 actions) or 5 (comprehensive enumeration of all capabilities).

4 / 5

Completeness

Explicitly answers both questions: what ('Create tessl tiles containing docs, rules, or skills... tile.json configuration') and when ('Use when a user wants to create a tile... Also triggers on "create tile from"...'). Concrete trigger phrases make this a direct match for anchor 5, not anchor 4 where 'when' is only adequate.

5 / 5

Trigger Term Quality

Comprehensive natural phrasings including synonyms: 'create a tile', 'create tile from', 'convert to tile', 'turn into tile', 'make tile from', 'tile this repo', plus the concrete filename 'tile.json'. These are all phrases a user would naturally say, matching the anchor 5 example's breadth.

5 / 5

Distinctiveness Conflict Risk

Clear niche ('tessl tiles') with distinct, tile-specific trigger phrases and minimal overlap risk with other skills — only mild ambiguity from the generic word 'tile' outside tessl contexts. Anchor 5 fits better than 4 since the triggers are unambiguously tile-creation phrasings.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository

tesslio/agent-browser-skill

Path

.tessl/tiles/tessleng/tile-creator/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.