CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

questionnaire-artifact

Publish a questionnaire as an Artifact page that collects answers from one or more people, then read the answers back.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally lean and actionable body: precise commands, exact tool parameters, data-contract tables, and per-step 'Done when' validation checkpoints with feedback loops. The one structural weakness is that the referenced template.html is missing from the bundle, making the build step's referenced material unavailable.

Suggestions

Ship template.html with the skill (e.g. as references/template.html) and update the [`template.html`](template.html) link to its actual path — step 2 cannot be executed without it.

Inline the few template invariants the instructions depend on (the Answers section, the bar, the scripts, `.qc`/`.qv` classes) or state where they are defined, so the page structure is not lost when the template file is absent.

DimensionReasoningScore

Conciseness

The body is telegraphic and assumes competence throughout — e.g. "Done when every decision has a recommended answer and a reason" and "Prefer `single` and `multi`: they tally across people" — with zero tokens spent explaining concepts Claude already knows. Every sentence instructs, matching the 'lean and efficient; every token earns its place' anchor, and sits clearly above 4 ('minor instances of over-explanation'), of which there are none.

5 / 5

Actionability

Guidance is fully executable: a copy-paste placeholder check (`grep -nE 'QUESTIONNAIRE TITLE|questionnaire-slug|...' <path>`), concrete serving commands (`python3 -I -m http.server`, `playwright-cli`), exact publish parameters (`icon: "checklist"`, `capabilities: {"db": {}, "user": {}}`), a field-by-field `responses` schema table, and precise data contracts (`data-kind` values, `data-rec`, stable `data-q` ids). This matches 'fully executable; copy-paste ready commands covering the common cases' and exceeds 4, which permits minor gaps.

5 / 5

Workflow Clarity

Five clearly sequenced steps, each ending in an explicit validation checkpoint ("Done when every decision from step 1 has a question... and this prints nothing", "Done when every `data-q` on the page is in the report and every respondent is named", "Done when every conflict has a decision document, and a `list` of `decisions` shows them"), with feedback loops for batch writes (grep placeholder check, playwright visual check at two widths, ArtifactData `list` confirmations of `responses` and `decisions`). This matches the top anchor including its error-recovery loops; no batch operation lacks verification, so no cap applies.

5 / 5

Progressive Disclosure

Sections are well organized and the design correctly pushes the page scaffold out of SKILL.md via a one-level-deep link ([`template.html`](template.html)), but scoring against the actual bundle shows no template.html exists (no references/, scripts/, or assets/ directories and no file at the skill root), leaving step 2's core instruction ("Copy the template to `<scratchpad>/<slug>.html`") without its referenced material. It also delegates voice and style rules to the external `temp-html` skill with no path. It is above 2 (the body is not an unstructured wall of inlined content) but below 4 because the primary reference is broken in the bundle as provided.

3 / 5

Total

18

/

20

Passed

Description

70%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 concise, third-person description that clearly states what the skill does across its full lifecycle and occupies a distinct niche. Its main weakness is the complete absence of 'when to use it' trigger guidance, which both caps completeness and leaves natural entry phrases like 'survey' or 'collect feedback' uncovered.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to survey a group, collect feedback or answers on decisions, or read answers from a published questionnaire."

Include natural synonyms such as "survey", "poll", or "feedback form" so the description matches the phrasing users actually say when they need this skill.

DimensionReasoningScore

Specificity

"Publish a questionnaire as an Artifact page", "collects answers from one or more people", and "then read the answers back" list several concrete actions spanning the full publish-to-report lifecycle, matching the 'several specific actions; minor gaps' anchor. It is not 5 because coverage is incomplete (conflict detection, decision recording, and recommendations are unmentioned), and not 3 because it goes beyond 1-2 actions with a clearly named domain.

4 / 5

Completeness

The 'what' is explicit (publish a questionnaire artifact page, collect answers, read them back), but there is no "Use when..." clause or any equivalent trigger guidance, which caps completeness at 3 per the rubric guideline. It cannot be 4 because 'when' is entirely absent rather than merely imprecise, and it is above 2 because 'what' is clear and specific.

3 / 5

Trigger Term Quality

Natural phrases like "questionnaire", "collects answers", and "read the answers back" are what a user would actually say, giving good keyword coverage in the style of "PDF files, forms, document extraction". It falls short of 5 because common synonyms ("survey", "poll", "feedback form") are missing and "Artifact page" leans on platform jargon rather than user vocabulary.

4 / 5

Distinctiveness Conflict Risk

"Questionnaire" plus "Artifact page" carves a clear, narrow niche (survey-style answer collection via an artifact with a database) that no generic skill description would match, giving minimal conflict risk. This squarely matches the 'clear niche with distinct triggers' anchor and is above 4, which allows minor overlap with closely related skills.

5 / 5

Total

16

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 1 possibly missing (template.html)

Warning

Total

14

/

16

Passed

Repository

aabuhijleh/abed-hub

Path

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