CtrlK
BlogDocsLog inGet started
Tessl Logo

workshop-facilitation

Facilitate workshop sessions in a one-step, multi-turn flow. Use when an interactive skill needs consistent pacing, options, and progress tracking.

71

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, actionable facilitation protocol with a clear multi-step workflow and concrete examples. The only real gap is a dangling reference to a missing examples file, which keeps progressive disclosure from a top score.

Suggestions

Create the referenced 'examples/inline-input-flow.md' file (or remove the link) so the one-level-deep reference resolves and navigation is trustworthy.

If additional detail grows, move the worked 'Examples' section into a separate examples file referenced one level deep, keeping SKILL.md as a concise overview.

DimensionReasoningScore

Conciseness

The body is lean and well-structured with bullet lists and short examples, assuming Claude's intelligence and avoiding padding or explanations of concepts Claude already knows.

3 / 3

Actionability

As an instruction-only skill it gives concrete, executable guidance — exact progress label formats ('Context Qx/8', 'Scoring Qx/5'), explicit selection parsing ('#1', '1 and 3', '1,3'), and worked dialogue examples — so absent code is not penalized.

3 / 3

Workflow Clarity

A clear 12-step numbered sequence with explicit checkpoints and feedback loops: interrupt handling ('halt immediately and wait for explicit resume'), meta-question handling, and an 'Assumptions to Validate' end-state for best-guess mode.

3 / 3

Progressive Disclosure

Sections are well-organized (Purpose, Input, Key Concepts, Application, Examples, Pitfalls, References), but the body references a bundle file '[examples/inline-input-flow.md](examples/inline-input-flow.md)' that does not exist in the bundle, so navigation is not actually resolvable.

2 / 3

Total

11

/

12

Passed

Description

85%

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 concise, third-person description with an explicit 'Use when' trigger and concrete actions. Its main weakness is trigger phrasing aimed at skill authors rather than the natural language end-users would say.

Suggestions

Reframe the trigger toward end-user language (e.g., 'Use when running or structuring a workshop, discovery sprint, or guided interactive session') so it matches phrases users actually say.

Add a couple of concrete user-utterable keywords such as 'workshop', 'facilitate', 'discovery sprint', or 'guided session' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Facilitate workshop sessions in a one-step, multi-turn flow', 'consistent pacing, options, and progress tracking' — matching the anchor for several specific actions rather than a single vague verb.

3 / 3

Completeness

Explicitly states both what it does ('Facilitate workshop sessions in a one-step, multi-turn flow') and when to use it via a 'Use when...' clause, matching the what-and-when anchor.

3 / 3

Trigger Term Quality

Triggers like 'interactive skill needs consistent pacing, options, and progress tracking' and 'workshop sessions' are relevant but framed toward skill authors rather than end-user phrasing, missing common user variations.

2 / 3

Distinctiveness Conflict Risk

The 'workshop facilitation' / 'interactive skill' framing carves a clear niche with distinct triggers, unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 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

Total

14

/

16

Passed

Repository
deanpeters/Product-Manager-Skills
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.