CtrlK
BlogDocsLog inGet started
Tessl Logo

doc-kami-parchment

Warm parchment canvas (#f5f4ed), monochrome ink-blue accent (#1B365D), one serif family, and editorial-grade typography.

51

Quality

56%

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/doc-kami-parchment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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, well-structured visual spec that gives Claude exact design constraints and clearly organized document-type options. Its main gaps are the absence of any executable starter template and a lack of explicit rendering/validation workflow.

Suggestions

Include a minimal single-file HTML/CSS starter snippet so the spec is immediately executable rather than interpretive.

Add a short explicit workflow (pick doc type → apply signature → render single-file HTML → self-check forbidden properties) with a verification checkpoint.

Optionally split the document-type catalog into a reference file once the skill grows, keeping SKILL.md as an overview.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — exact hex codes, font stacks, line-heights, and a forbidden-list with no padding or explanation of concepts Claude already knows; only the document-type catalog could be trimmed slightly.

4 / 5

Actionability

It gives highly concrete specs ("#f5f4ed", "Charter", line-height 1.5–1.55, "Tailwind CDN", "single-file HTML") but provides no copy-paste starter template or CSS, so the guidance is specific yet not directly executable.

3 / 5

Workflow Clarity

The intended output is clear and doc-type selection is laid out, but there is no explicit step sequence (apply signature → choose type → render → verify) and no validation checkpoint for the produced HTML.

3 / 5

Progressive Disclosure

Under 50 lines with no bundle files, the body is cleanly sectioned (意图 / 硬性视觉签名 / 可选文档类型 / 设计准则), meeting the simple-skill exception for well-organized single-file content.

5 / 5

Total

15

/

20

Passed

Description

48%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 a precise visual style spec but reads as a noun phrase rather than a capability statement, omitting both the skill's action and any usage trigger. It is distinctive but incomplete as a skill description.

Suggestions

Lead with the action, e.g. "Renders user content as a warm parchment document..." so the capability is explicit.

Add a 'Use when...' clause naming natural triggers like report, letter, resume, one-pager, or changelog.

Mention the supported document types (one-pager, long doc, letter, portfolio, resume, slides) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists concrete visual specifics ("#f5f4ed", "#1B365D", "one serif family", "editorial-grade typography") but states no actions at all — it is a noun phrase describing appearance rather than what the skill does.

2 / 5

Completeness

It conveys a clear visual "what" (the look of the output) but provides no action/capability verb and no "Use when..." trigger clause, so the cap at 3 applies.

3 / 5

Trigger Term Quality

It includes some natural terms ("parchment", "serif", "editorial typography") but omits the document-type phrases users would actually say (report, letter, resume, one-pager) that appear only in the body.

3 / 5

Distinctiveness Conflict Risk

The parchment + ink-blue + single-serif signature is a narrow niche with low overlap risk, though the description alone lacks explicit triggers that would fully separate it from generic document skills.

4 / 5

Total

12

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.