CtrlK
BlogDocsLog inGet started
Tessl Logo

survey

Create a lightweight survey as a plain Slack message and answer surveys others share. Every question lets the respondent add a free-text note, skip, or say "I don't know", so answers always carry context. Use when the user says "make a survey", "create a poll", "answer this survey", "run this survey", or pastes a survey message/link and wants to respond.

74

Quality

93%

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

85%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 a clear, actionable, well-sequenced skill with explicit validation gates for its posting operations. Its main weakness is mild redundancy between the Guardrails and Common mistakes sections rather than any lack of clarity or actionability.

Suggestions

Trim the Common mistakes section to points not already stated in Guardrails (link-not-a-trigger, don't-paste-the-body, don't-style-the-permalink) to remove redundancy and tighten conciseness.

The anonymized placeholder note at the top is helpful context but could be shortened to a single line to reduce overhead for the active reader.

DimensionReasoningScore

Conciseness

Mostly lean and well-organized with purposeful sections, but the Common mistakes list repeats several guardrail points already covered (e.g., link-is-not-a-trigger, don't-paste-the-body, don't-style-the-permalink), adding mild redundancy.

4 / 5

Actionability

Provides concrete parsing rules, a complete JSON structure, filename format, and named Slack tool calls (post_message, edit_message, lookup_user, open_dm_channel); gaps are mostly around the non-working/anonymized nature rather than missing specifics.

4 / 5

Workflow Clarity

Both flows are numbered with explicit validation checkpoints — allowlist verification before posting, confirm-before-every-send as the safety gate, parse-confirmation on ambiguity, and a post-send save step — giving strong feedback loops for the batch/destructive posting operations.

5 / 5

Progressive Disclosure

No bundle files exist, but the single SKILL.md is well-organized into clear sections (Overview, format, Author/Respond flows, Storage, Guardrails, Common mistakes, Quick reference) with a Quick reference summary; it stays single-file appropriately for its size.

4 / 5

Total

17

/

20

Passed

Description

100%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 is concrete, third-person, and explicitly pairs a clear 'what' with a specific 'Use when' trigger clause covering natural phrasings and link-paste cases. It is a strong, comprehensive description with no notable gaps.

DimensionReasoningScore

Specificity

Names concrete actions ('Create a lightweight survey as a plain Slack message and answer surveys others share') plus the per-question note/skip/don't-know behavior, covering both authoring and responding comprehensively.

5 / 5

Completeness

Explicitly states what it does (create/answer Slack-message surveys with note/skip/don't-know per question) and when to use it (the quoted 'Use when...' clause with concrete trigger phrases), satisfying both halves.

5 / 5

Trigger Term Quality

Includes the natural phrases users would say ('make a survey', 'create a poll', 'answer this survey', 'run this survey', 'pastes a survey message/link'), covering synonyms and link-paste triggers.

5 / 5

Distinctiveness Conflict Risk

The Slack-message survey niche with note/skip/don't-know context is a clear, distinct trigger set unlikely to fire for unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
Alexhans/blog-samples
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.