CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

to-questionnaire

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

Quality

81%

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

The canonical home for this skill is to-questionnaire in mattpocock/skills

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 exemplary short-form instruction skill: lean, concrete, and structured as a three-step workflow with explicit per-step completion checkpoints, culminating in a ready-to-adapt template. No weaknesses were identified on any dimension.

DimensionReasoningScore

Conciseness

The ~49-line body is lean and efficient with no padding and no explanation of concepts Claude already knows; every instruction ("Grill the send, not the subject", "Done when" criteria, the template) earns its place.

5 / 5

Actionability

For an instruction-only skill, the guidance is fully concrete: three defined exchanges with what to ask, an explicit output path (`to-questionnaire-<slug>.md`), and a complete copy-adaptable template with answer stubs and a worked question example.

5 / 5

Workflow Clarity

The three steps are clearly sequenced and each ends with an explicit validation checkpoint ("Done when you know who the recipient is...", "Done when you have a concrete list...", "Done when the file exists and every item... is covered"), which functions as a feedback loop before proceeding.

5 / 5

Progressive Disclosure

The body is under 50 lines with no need for external references (none exist in the bundle), and it is well organized into numbered steps, a Document structure section, and a clearly delimited template block — the simple-skill case where well-organized sections alone merit a 5.

5 / 5

Total

20

/

20

Passed

Description

53%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 communicates a clear, distinct capability in one concise sentence, but it omits any explicit 'Use when...' trigger guidance and lacks common trigger synonyms. Adding a trigger clause with natural user phrases would lift both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user mentions wanting to ask someone else, send questions async, or prepare a survey/intake for a decision they can't resolve alone."

Add natural trigger synonyms users would actually say — "survey", "questions to ask", "interview questions", "intake form" — to broaden keyword coverage.

Optionally enumerate the concrete deliverables (intake questions, a Markdown questionnaire file with answer stubs) to raise specificity from one action to a short list.

DimensionReasoningScore

Specificity

"Turn a decision you can't fully answer into a questionnaire for someone else to fill in" names the domain and one concrete action, but does not list several specific actions, matching the anchor for 1-2 concrete actions with gaps in coverage.

3 / 5

Completeness

The 'what' is clear (turn a decision into a questionnaire), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3; the 'when' is only weakly implied by "a decision you can't fully answer".

3 / 5

Trigger Term Quality

"questionnaire", "decision", and "fill in" are relevant keywords a user might say, but common variations like "survey", "questions to ask someone", or "interview questions" are missing.

3 / 5

Distinctiveness Conflict Risk

The questionnaire-for-knowledge-extraction framing carves out a mostly distinct niche with minor overlap risk against general drafting or writing skills, but the absence of explicit trigger phrases keeps it below the clear-niche anchor.

4 / 5

Total

13

/

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

tonykay/transcriber

Path

.agents/skills/to-questionnaire/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.