CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

temp-html

Build a temp HTML report in a neobrutalist style, with a reading-progress rail and click-to-zoom images. Use when the user asks for a temp HTML, a temp document, or a report to read in the browser.

Quality

86%

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

85%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 tight, highly actionable skill body with excellent workflow sequencing, explicit validation checkpoints, and a fix-and-rerun loop. Its main defect is that the entire build step rests on template.html, which is absent from the bundle, breaking both executability of step 2 and the skill's single core reference.

Suggestions

Bundle template.html with the skill (e.g., in the skill root or a references/ directory) so the 'Copy the template to the path' step and the linked single source of truth are actually available.

If the template cannot be bundled, inline the essential class inventory and placeholder list in SKILL.md so an agent can reconstruct the page without the missing file.

Make the placeholder replacement step concrete: enumerate the placeholders (the grep check already names several) next to the copy instruction, so step 2 is executable without inspecting template.html.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout ("A paragraph holds at most 3 sentences. A list item holds one fact."), explains nothing Claude already knows, and every section is direct instruction — every token earns its place.

5 / 5

Actionability

Nearly every step is copy-paste ready ("git check-ignore -q <dir>", "python3 -I -m http.server <port> --bind 127.0.0.1", the executable JS eval check, the grep placeholder check), but the central build step "Copy the template to the path" depends on template.html, which is missing from the bundle — a key gap that keeps it from fully executable.

4 / 5

Workflow Clarity

Four numbered phases each end in an explicit "Done when…" checkpoint, and verification includes concrete pass criteria (overflow, offscreen, and broken are 0; rail equals sections) plus a feedback loop ("Fix what fails and rerun the pass") and cleanup, matching the anchor-5 example structure.

5 / 5

Progressive Disclosure

Sections are well organized and the reference to template.html is clearly signaled one level deep, but the referenced file does not exist in the bundle (no references/, scripts/, assets/, or template.html are present), so the declared "single source of truth for the look" is unreachable — a broken core reference rather than a minor organization gap.

3 / 5

Total

17

/

20

Passed

Description

83%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 that clearly and explicitly states both what the skill builds and when to use it, with concrete style features (neobrutalist, progress rail, click-to-zoom) and natural trigger phrases. Coverage of synonyms is good but not comprehensive, keeping specificity and trigger quality at the 4 level.

DimensionReasoningScore

Specificity

"Build a temp HTML report in a neobrutalist style, with a reading-progress rail and click-to-zoom images" names one concrete action plus three specific deliverable features, which is above the anchor-3 example ('Processes PDF files and extracts content') but lacks the several distinct actions of anchor 5.

4 / 5

Completeness

It explicitly answers both questions: "Build a temp HTML report in a neobrutalist style, with a reading-progress rail and click-to-zoom images" states the what, and "Use when the user asks for a temp HTML, a temp document, or a report to read in the browser" states the when with concrete trigger phrases, mirroring the anchor-5 example.

5 / 5

Trigger Term Quality

"temp HTML", "temp document", and "report to read in the browser" are phrases a user would naturally say, but common variations like "quick HTML page", "one-off report", or ".html" are missing, matching the good-coverage-with-gaps anchor.

4 / 5

Distinctiveness Conflict Risk

"temp HTML report" carves a clear niche with distinct triggers, but "a report to read in the browser" is broad enough to overlap with general report-generation skills, so it is mostly distinct rather than minimal-conflict.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 1 possibly missing (template.html)

Warning

Total

14

/

16

Passed

Repository

aabuhijleh/abed-hub

Path

skills/temp-html/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.