CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

decision-questionnaire

Turn an unanswerable decision into a questionnaire doc.

Quality

75%

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 ./optional-skills/productivity/decision-questionnaire/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

96%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 content is an exemplary lean, single-purpose instruction skill: a crisp interview-the-send principle, a copy-paste document template, concrete pitfalls, and a verification checklist. Its only structural improvement would be moving the questionnaire template into an asset file to slim the main body further.

DimensionReasoningScore

Conciseness

The body is lean throughout — every section ('When to Use', 'Core Principle', 'Document Structure', 'Pitfalls', 'Verification') adds non-obvious guidance and explains nothing Claude already knows. It is not 4 because there is no identifiable padding or over-explanation to trim; even the attribution line ('Ported from mattpocock/skills' MIT-licensed to-questionnaire skill') carries provenance information.

5 / 5

Actionability

Guidance is fully executable: a complete copy-paste markdown template, an exact output filename convention ('decision-questionnaire-<slug>.md in the current directory'), and explicit done-when criteria for each interview step. This is an instruction-only skill and the guidance is concrete and specific, so the absence of code is not penalized per the scoring notes.

5 / 5

Workflow Clarity

The process is clearly sequenced (two short interview exchanges, each with a 'Done when' checkpoint, then drafting, then reporting the absolute path) and closes with an explicit Verification checklist — matching the anchor for clear sequence with validation checkpoints. The workflow is not destructive or batch-oriented, so no cap applies.

5 / 5

Progressive Disclosure

Sections are well-organized with all content appropriately inline for a skill of this size, and no nested or buried references exist (the bundle has no other files). It is not 5 because the body exceeds 50 lines and the questionnaire template is a strong candidate for an assets/ file the skill could reference one level deep, which would keep SKILL.md as a pure overview.

4 / 5

Total

19

/

20

Passed

Description

46%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 single concrete capability in an appropriately terse, third-person voice, but it omits any 'when to use' guidance and natural trigger phrases. A user who needs this skill (e.g., 'I need to ask the ops team about this before deciding') would not reliably match on this description alone.

Suggestions

Append an explicit trigger clause, e.g., 'Use when a decision is blocked on someone else's knowledge — the user says they need to ask a stakeholder, expert, or vendor before deciding.'

Add one or two natural user phrasings as keywords: 'ask X about', 'stakeholder input', 'questions for', 'async questionnaire' — the current description has only 'decision' and 'questionnaire'.

Briefly enumerate the concrete actions (interview the user about the send, draft the questionnaire doc, write it to a file) to lift specificity above a single named action.

DimensionReasoningScore

Specificity

The phrase 'Turn an unanswerable decision into a questionnaire doc' names the domain (decision questionnaires) and exactly one concrete action, matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not 2 because the action is specific rather than generic ('Processes PDF files'-style), and not 4 because no additional capabilities are enumerated.

3 / 5

Completeness

The 'what' is clear (turn an unanswerable decision into a questionnaire doc) but there is no 'Use when...' or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not 4 because the 'when' is not present even weakly — it is entirely missing.

3 / 5

Trigger Term Quality

Only two relevant keywords appear ('decision', 'questionnaire') and the natural phrases a user would actually say ('I need to ask X about this', 'stakeholder input', 'send questions to') are absent. It edges toward 3 since the keywords are domain-relevant, but coverage is too thin to reach it.

2 / 5

Distinctiveness Conflict Risk

'Questionnaire' carves a fairly distinct niche with specific trigger vocabulary, creating only minor overlap risk with closely related communication/skills (e.g., meeting action items or stakeholder outreach skills). It is not 5 because 'decision' alone is broad and the lack of explicit triggers leaves some ambiguity.

4 / 5

Total

12

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/productivity/decision-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.