CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

render-template

Render templates with variable substitution using {{variable}} or ${variable} syntax. Use for generating formatted output, reports, commit messages, or any text requiring variable interpolation.

64

Quality

80%

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 ./.claude/skills/render-template/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 concrete, example-driven guidance with a clear five-step sequence and explicit error-handling rules. Its main weaknesses are redundancy (steps 2-3 and Error Handling repeat content) and length for such a simple substitution task, plus an Integration section referencing skills that do not exist in the bundle.

Suggestions

Merge Steps 2 and 3 (both restate the same placeholder patterns) and fold 'Error Handling' missing-variable rules into 'Resolution Rules' to remove duplicated content.

Cut examples from six to three (simple mustache, shell syntax, missing variables) and move the rest to a references file, or drop the redundant ones (Example 6 largely re-covers Example 1).

Remove or substantiate the 'Integration with Other Skills' section — the four named skills (format-commit-message, generate-report-header, etc.) are not in this bundle.

DimensionReasoningScore

Conciseness

Steps 2 and 3 both restate the same placeholder patterns, 'Error Handling' repeats the missing-variable rules from 'Resolution Rules', and six full examples plus an Integration section pad out what is conceptually simple string substitution. Mostly efficient but clearly could be tightened — not the 4 anchor, which requires only minor trimmable instances.

3 / 5

Actionability

Concrete placeholder patterns, explicit resolution rules, filter syntax, and complete input/output example pairs covering the common cases (simple, nested, shell syntax, missing variables). Not 5: no executable implementation is given, and conditionals/loops/filters are named without resolution semantics.

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced, error handling is explicit with defined behaviors, and a Validation checklist exists. Not 5: the checklist is terminal rather than an embedded validate-fix-retry loop; no cap applies since this is not a destructive or batch operation.

4 / 5

Progressive Disclosure

Sections are well organized for a self-contained skill ('Supporting Files: None required' is honest — no bundle files exist). Not 5: the 'Integration with Other Skills' section names four skills absent from the bundle, and the 240-line body (six examples) could plausibly split examples into a reference file.

4 / 5

Total

15

/

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: third-person voice, concrete action with exact syntax tokens, and an explicit 'Use for...' clause listing specific use cases. Only minor gaps in trigger synonyms and a slightly broad catch-all phrase.

DimensionReasoningScore

Specificity

Names the concrete action ('Render templates with variable substitution') plus exact syntax tokens ({{variable}} or ${variable}) and application areas (reports, commit messages). It is one primary action with use cases rather than multiple distinct concrete actions, so it sits at anchor 4, not 5.

4 / 5

Completeness

Explicitly answers 'what' (render templates with variable substitution using both syntaxes) and 'when' ('Use for generating formatted output, reports, commit messages, or any text requiring variable interpolation') with concrete trigger phrases — matching the anchor-5 example's structure.

5 / 5

Trigger Term Quality

Includes natural phrases users would say such as 'templates', 'commit messages', 'reports', and 'variable interpolation'. Missing common synonyms like 'placeholders', 'fill in', or 'boilerplate', which keeps it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The {{variable}}/${variable} syntax markers carve a fairly distinct niche. The catch-all 'any text requiring variable interpolation' phrase creates minor overlap risk with general formatting skills, so not 5.

4 / 5

Total

17

/

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

maslennikov-ig/claude-code-orchestrator-kit

Path

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