CtrlK
BlogDocsLog inGet started
Tessl Logo

html-ppt-zhangzara-monochrome

A grant proposal on CRISPR base-editing for sickle-cell disease — the hypothesis, the approach, the milestones, and the risk. Built as a decision-grade academic research deck for grant review committee.

62

Quality

75%

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 ./design-templates/html-ppt-zhangzara-monochrome/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a lean, well-organized instruction-only skill with a clear 6-step workflow and a precise output contract, scoring high on conciseness and progressive disclosure. It lacks explicit validation checkpoints and an inline slide HTML example, which keep actionability and workflow clarity at 4.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: "Ivory ledger paper with all-black type; Lora serif headlines, Jost body, no color at all" and tight sections (At a glance, Best for, Avoid for) with no padded explanations of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Gives concrete executable guidance — "Clone `example.html` into the user's workspace", an exact output contract with `<artifact identifier="zhangzara-monochrome" type="text/html">`, and "duplicate an existing slide of the most appropriate layout" — but stops short of an inline slide HTML example, leaving a minor gap for a 5.

4 / 5

Workflow Clarity

Presents a clear numbered 6-step sequence (Clone, Replace, Preserve, Adjust length, Design missing layouts, Keep nav runtime), but includes no explicit validation checkpoints or feedback loops; the operation is not high-risk destructive, so it stays at 4 rather than being capped at 3.

4 / 5

Progressive Disclosure

No bundle directories exist (references/, scripts/, assets/ all absent), and the single self-contained ~45-line body is well-organized with clear section headers; references to ./LICENSE and template.json are one-level-deep and clearly signaled, satisfying the simple-skill exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

65%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 domain-specific and distinctive but describes the deck's subject matter rather than the concrete actions the skill performs, and it lacks an explicit "Use when..." trigger clause, capping completeness at 3. Trigger-term coverage is good but not comprehensive.

Suggestions

Add an explicit trigger clause such as "Use when producing a grant review deck, a research committee brief, or an academic funding proposal" to raise completeness above 3.

Reframe the description around the skill's actions (e.g., "Builds a decision-grade academic research deck from a research subject..." instead of describing the subject) to improve specificity.

Include common synonyms/variations ("funding proposal", "research deck", "study section brief") to broaden natural trigger-term coverage.

DimensionReasoningScore

Specificity

Names a concrete domain ("CRISPR base-editing for sickle-cell disease") and enumerates the four content pillars ("the hypothesis, the approach, the milestones, and the risk") plus format ("decision-grade academic research deck"), but describes the output subject rather than actions Claude performs, so it does not reach the multi-action comprehensiveness of 4-5.

3 / 5

Completeness

Clearly answers "what" (a grant proposal deck on a specific topic with its hypothesis/approach/milestones/risk) but the description itself has no explicit "Use when..." trigger clause, which caps completeness at 3 per the guideline even though triggers exist elsewhere in frontmatter.

3 / 5

Trigger Term Quality

Contains natural phrases a user would say ("grant proposal", "grant review committee", "CRISPR base-editing", "sickle-cell disease") but lacks common synonyms and variations that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

The highly specific subject (CRISPR base-editing sickle-cell grant review deck) carves a clear niche with minimal overlap risk against other skills.

5 / 5

Total

15

/

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

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.