CtrlK
BlogDocsLog inGet started
Tessl Logo

add-testimonial

Collect a testimonial (name, rating, text, email) and publish it to testimonials.html

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tight, highly actionable seven-step workflow with a copy-paste HTML block, explicit placement instructions, and a preview/confirm checkpoint before the destructive publish, requiring no external references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — each step is a brief directive with no padding or explanation of concepts Claude already knows, and the only prose ("Work through the following steps in order, waiting for user input at each stage") earns its place.

3 / 3

Actionability

Provides a fully copy-paste-ready HTML block with explicit placement ("FIRST child element inside <div class='testimonials-grid' id='testimonials-grid'>... directly after the opening div tag, before the existing comment") and concrete star-fill examples, matching the anchor for executable, copy-paste-ready guidance.

3 / 3

Workflow Clarity

Seven steps are clearly sequenced with an explicit validation checkpoint — Step 5 previews the testimonial and offers a change-anything feedback loop before the destructive publish in Step 6 — satisfying the validation requirement for a page-modifying operation.

3 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, and has no bundle files or external references, yet is well-organized into clearly labeled numbered steps, which per the guideline allows progressive disclosure to score 3 on organization alone.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and concrete about what the skill does and has a clear niche, but it lacks an explicit "Use when..." trigger clause and offers limited keyword variation, capping completeness and trigger quality.

Suggestions

Add a "Use when..." clause stating when to invoke the skill (e.g., when the user wants to add or submit a testimonial/review).

Broaden trigger terms to include natural variations like "review", "feedback", or "endorsement" that users might actually say.

Keep the concrete action list and target file as-is; these are already strong.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Collect a testimonial (name, rating, text, email) and publish it to testimonials.html" — naming both the operations and the exact data fields, matching the anchor for several specific concrete actions.

3 / 3

Completeness

It clearly states what the skill does (collect and publish a testimonial) but provides no "Use when..." clause or equivalent explicit trigger guidance, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Contains natural terms a user would say ("testimonial", "rating"), but coverage is thin with no common variations such as "review", "feedback", or "endorsement", fitting the anchor for some relevant keywords but missing variations.

2 / 3

Distinctiveness Conflict Risk

The testimonial-collection niche with a concrete target (testimonials.html) is distinct and unlikely to trigger for unrelated skills, matching the anchor for a clear niche with distinct triggers.

3 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
basdijkstra/agentic-engineering-training
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.