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.

65

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 ./skills/workshop-facilitation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured facilitation protocol with concrete, actionable guidance and a clear multi-step workflow. Main weaknesses are minor: duplicated frontmatter intent in Purpose, and a referenced transcript file that is missing from the bundle.

Suggestions

Remove the Purpose section or replace it with non-duplicated content, since it repeats the frontmatter intent verbatim.

Either add the referenced examples/inline-input-flow.md file or drop the broken link, so the one external reference resolves.

Tighten the overlap between Key Concepts and the Application steps so each section adds distinct value.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the Purpose section duplicates the frontmatter intent verbatim and the Key Concepts bullets overlap with the Application steps.

4 / 5

Actionability

Provides concrete, executable guidance — specific entry modes, exact progress labels ('Context Qx/8', 'Scoring Qx/5'), selection syntax ('#1', '1,3', '1 and 3'), and copy-ready example dialogue — with the one gap that the referenced full transcript file does not exist.

4 / 5

Workflow Clarity

A clearly sequenced 12-step facilitation procedure with explicit checkpoints (per-turn progress labels, decision points, interruption handling, stop/pause), though fast-path and resume details are lighter than the main loop.

4 / 5

Progressive Disclosure

Well-organized into clear sections with content appropriately kept inline for a protocol skill; the single external reference (examples/inline-input-flow.md) is clearly signaled but the file is absent from the bundle, a minor navigation gap.

4 / 5

Total

16

/

20

Passed

Description

83%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.

A strong description that clearly states both capability and trigger conditions in third person with concrete facilitation behaviors. It is comprehensive on completeness with only minor gaps in trigger synonym coverage and distinctiveness breadth.

DimensionReasoningScore

Specificity

Names the domain ('Facilitate workshop sessions in a one-step, multi-turn flow') and several concrete behaviors ('consistent pacing, options, and progress tracking'), though the actions are facilitation mechanics rather than a comprehensive enumerated list.

4 / 5

Completeness

Explicitly answers both what ('Facilitate workshop sessions in a one-step, multi-turn flow') and when ('Use when an interactive skill needs consistent pacing, options, and progress tracking') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms a user or skill author would say ('workshop sessions', 'interactive skill', 'pacing', 'options', 'progress tracking') with good coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The facilitation-protocol niche is mostly distinct, but the trigger ('interactive skill needs consistent pacing, options, and progress tracking') is broad enough to risk minor overlap with other interactive skills.

4 / 5

Total

17

/

20

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.