CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

render-html

Render an ARIS Markdown / JSON artifact (IDEA_REPORT, AUTO_REVIEW, KILL_ARGUMENT, PAPER_PLAN, research-wiki state, etc.) into a single-file HTML view designed for human reading. Use when the user says "渲染 HTML", "出一份 HTML 报告", "render html", "make this readable", "export to html", or wants a polished web-rendered view of a Markdown artifact.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/skills-codex/render-html/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 highly actionable with a well-sequenced, validated workflow and fully executable commands and prompts throughout. Its weaknesses are repetition of the review-gate rules across three sections plus non-operational roadmap content, and navigation gaps from references to non-existent shared-references files and a large inline reviewer prompt.

Suggestions

State the review-gate rules once in Step 4 and reduce the Core invariants and Key rules entries to one-line pointers, cutting the ~40 lines of repeated review/gating text.

Move the full reviewer prompt template into a reference file (e.g. references/reviewer-prompt.md) and link to it one level deep, keeping only the resolution rule and verdict handling inline.

Drop or relocate the two-phase roadmap and External alternatives section (including the time-sensitive '3000⭐ at time of writing') to a separate planning document outside SKILL.md.

DimensionReasoningScore

Conciseness

The review-gate rules are restated three times ("Fresh review at the artifact boundary" in Core invariants, the full Step 4 gate, and the Key rules recap), and the Phase 2 roadmap plus External alternatives section ("3000⭐ at time of writing" — time-sensitive) are planning content rather than execution guidance. Not 4: the repetition and non-operational sections go beyond 'minor instances of over-explanation'; not 2: the bulk is dense, skill-specific operational content (resolver chain, flags, verdict handling) that Claude does not already know.

3 / 5

Actionability

Everything is copy-paste executable: the full $RENDER_HTML resolver bash block, exact invocations for every option (--template, --out, --state, --json, --offline, --lang, --review/--no-review), the complete reviewer prompt, and exact output paths for verdicts and traces. Not 4: the examples cover all common cases with concrete commands — nothing remains as pseudocode or high-level hints.

5 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced with an explicit validation checkpoint (the Step 4 review gate: "should_review = explicit --review present or (template == 'academic' ...)"), and every verdict branch has a feedback loop — FAIL: "Tell the user the blocking issues ... and re-render. Do not silently overwrite"; WARN: deliver but surface warnings; unavailable route: "do not fabricate PASS". Not 4: validation and error recovery are explicit at each branch rather than implicit.

5 / 5

Progressive Disclosure

The implementation is properly externalized (scripts/render_html.py and scripts/templates/{academic,dashboard}.html exist in the bundle and match the body's references), but three references point outside the bundle to missing files ("../shared-references/reviewer-backends.md", "../shared-references/reviewer-routing.md", "shared-references/review-tracing.md" — no shared-references directory exists), and the ~60-line reviewer prompt is inlined in the body. Not 4: dangling references and the large inline block fall short of 'references mostly clear'; not 2: sections are well-organized with clear headers and the heavy lifting lives in the bundled script.

3 / 5

Total

16

/

20

Passed

Description

78%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 with an explicit what/when structure and concrete quoted trigger phrases in both English and Chinese. Its main gaps are capability coverage (only the core render action is stated) and a few missing natural trigger variants such as the .html extension.

DimensionReasoningScore

Specificity

Names the domain concretely ("ARIS Markdown / JSON artifact (IDEA_REPORT, AUTO_REVIEW, KILL_ARGUMENT, PAPER_PLAN, research-wiki state, etc.)") with one concrete action — "render ... into a single-file HTML view designed for human reading". Not 4: only a single action verb is listed; capabilities like templating, review gating, and offline mode are absent, so coverage is not 'several specific actions'.

3 / 5

Completeness

Explicitly answers both parts: what ("Render an ARIS Markdown / JSON artifact ... into a single-file HTML view designed for human reading") and when ("Use when the user says '渲染 HTML', ..., 'render html', 'make this readable', 'export to html', or wants a polished web-rendered view"). Not 4: the 'when' clause is fully explicit with concrete quoted trigger phrases, exactly matching the 5 anchor.

5 / 5

Trigger Term Quality

Good natural coverage: "render html", "export to html", "make this readable", "polished web-rendered view of a Markdown artifact", plus Chinese equivalents ("渲染 HTML", "出一份 HTML 报告"). Not 5: common variations like ".html" extension, "convert to html", or "HTML report/view" are missing, so it falls short of comprehensive synonym and extension coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche — ARIS workflow artifacts rendered to HTML — with distinct triggers, so it is mostly distinguishable from generic formatting skills. Not 5: "make this readable" is generic enough to fire for non-HTML readability requests; not 3: the ARIS-artifact scoping and render-to-HTML verbs make it far more distinct than 'Works with document files'.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 missing, 1 suspicious

Warning

Total

13

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex/render-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.