survey-creator
Survey Creator - Auto-activating skill for Business Automation. Triggers on: survey creator, survey creator Part of the Business Automation skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/survey-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely minimal and template-like, providing almost no useful information beyond the skill name and category. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should select this skill. It reads as auto-generated boilerplate rather than a thoughtful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates survey questionnaires, designs question flows with branching logic, generates response collection forms, and exports survey results.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a survey, build a questionnaire, design a feedback form, make a poll, or collect responses.'
Remove the redundant duplicate trigger term ('survey creator' listed twice) and expand with varied natural language terms users might actually say, such as 'questionnaire', 'feedback form', 'poll', 'survey questions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Survey Creator') and its category ('Business Automation') but lists no concrete actions like creating questions, designing forms, configuring logic, or exporting surveys. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name and provides no explicit 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'survey creator' repeated twice. It misses natural user phrases like 'create a survey', 'questionnaire', 'feedback form', 'poll', or 'survey questions'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'survey creator' is somewhat specific to a niche (surveys), which reduces conflict with unrelated skills, but the lack of detail means it could overlap with form builders or questionnaire tools without clear differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder with no substantive content. It contains only generic boilerplate text that could apply to any topic—simply substituting 'survey creator' into a template. It provides no actionable guidance, no code, no examples, no workflow, and no references to supporting materials.
Suggestions
Add concrete, executable code examples for creating surveys (e.g., generating a Google Form via API, building a survey with a Python library like WTForms, or creating a structured survey JSON schema).
Define a clear workflow with steps: design survey structure → generate questions → validate logic (skip patterns, required fields) → deploy/export, with validation checkpoints at each stage.
Include at least one complete input/output example showing a survey specification and the resulting generated survey artifact.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that add no information and replace with actual domain-specific instructions and constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no domain-specific information, and every section restates the same vague concept ('survey creator') without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of survey structures, no API references, no specific steps for creating a survey. Every bullet point is abstract and vague. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | There are no references to supporting files, no bundle files exist, and the content is a monolithic block of placeholder text with no meaningful structure or navigation to deeper content. | 1 / 3 |
Total | 4 / 12 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.