CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

land

Build a stepped deck an audience works through until one thing of it stays with them. Use when the user needs an audience to come away holding one thing.

Quality

79%

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 ./hold/skills/land/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 an unusually tight instruction-only skill: dense, imperative design rules, a concrete content-type table, explicit output conventions, and clear boundary routing to sibling skills. Its main gap is the absence of any worked example or minimal code for the step-reveal deck it mandates, which caps actionability, and an implicit post-build verification step.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout — e.g. "One idea per slide; cut any slide the one thing does not need" and "text labels, never explains" — with no explanation of concepts Claude already knows; every sentence instructs rather than describes.

5 / 5

Actionability

Concrete specifics are present: the output convention "`YYYY-MM-DD-<slug>.html`, one reveal per press then the next slide", the command "`open <path>`", and a mapping table with a fixed case per content type (e.g. "API = ordering in a restaurant"). It stops short of fully copy-paste-ready guidance in that no example of the step-reveal HTML or a worked slide is given.

4 / 5

Workflow Clarity

The sequence is clear — "Before building, take... the audience... and the one thing", "Say the brief back, then build", then output, open, and "Name what the deck leaves out" — with an explicit user-confirmation checkpoint and error-recovery exits ("One view or one plain line would make the point → not land; say so and stop"). Verification of the produced deck is left implicit, keeping it below the 5 anchor.

4 / 5

Progressive Disclosure

This is a single-purpose skill under 50 lines with no bundle files and no need for external references; the paragraphs are each organized around one topic (brief, opening, visuals, content-type table, output medium, boundaries), satisfying the simple-skill exception for a full score.

5 / 5

Total

18

/

20

Passed

Description

62%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 cleanly pairs a single concrete capability with an explicit "Use when" trigger in third person, with a distinctive outcome-oriented framing. Its weaknesses are thin keyword coverage of natural presentation-domain phrasings and only one named action, which limits specificity and trigger discoverability.

Suggestions

Add 1-2 more concrete actions to the what-clause (e.g. sequencing reveals, drawing concepts as graphics) to lift specificity toward the 4-5 anchors.

Include natural trigger keywords users would say — "presentation", "slides", "talk" — in the Use-when clause so it matches how the need is actually voiced.

State the deliverable (an HTML step-reveal deck) explicitly in the description to sharpen both specificity and distinctiveness.

DimensionReasoningScore

Specificity

"Build a stepped deck an audience works through until one thing of it stays with them" names the domain and one concrete action with a specific outcome, but does not list several distinct concrete actions (e.g. no mention of slide construction, visuals, narration, output) that the 4-5 anchors expect.

3 / 5

Completeness

Both what ("Build a stepped deck...") and an explicit when ("Use when the user needs an audience to come away holding one thing") are present; the when-clause is concrete but abstract rather than rich in trigger phrases, so it falls short of the 5 anchor.

4 / 5

Trigger Term Quality

Relevant terms like "deck", "audience", and "come away holding one thing" appear, but the most natural user phrasings for this domain — "presentation", "slides", "talk", "keynote" — are absent, matching the anchor for some relevant keywords with missing common variations.

3 / 5

Distinctiveness Conflict Risk

The one-memorable-thing outcome framing carves a distinct niche unlikely to collide with generic presentation or document skills; only minor overlap risk with closely related presentation-building skills remains.

4 / 5

Total

14

/

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

saadshahd/moo.md

Path

hold/skills/land/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.