faq-generator
Faq Generator - Auto-activating skill for Technical Documentation. Triggers on: faq generator, faq generator Part of the Technical Documentation skill category.
34
0%
Does it follow best practices?
Impact
100%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/17-technical-docs/faq-generator/SKILL.mdQuality
Discovery
0%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 essentially a placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be nearly impossible for Claude to reliably choose this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates FAQ sections from technical documentation by identifying common user questions, organizing Q&A pairs, and formatting them for readability.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create FAQs, frequently asked questions, Q&A sections, help pages, or knowledge base articles from existing technical documentation.'
Remove the duplicated trigger term and expand with natural language variations users would actually say, such as 'FAQ', 'frequently asked questions', 'Q&A', 'help section', 'knowledge base'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Faq Generator' and 'Technical Documentation' without describing any concrete actions. There are no specific capabilities listed such as 'generates FAQ sections from documentation' or 'extracts common questions from technical content.' | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' guidance. The 'Triggers on' line is just the skill name repeated, not meaningful trigger context. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'faq generator' repeated twice. It misses natural variations users would say like 'FAQ', 'frequently asked questions', 'generate questions', 'Q&A section', 'help page', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Technical Documentation' could overlap with many documentation-related skills, and 'faq generator' alone doesn't carve out a clear niche or explain what differentiates it from other documentation generation skills. | 1 / 3 |
Total | 4 / 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 template with no substantive content. It contains only generic boilerplate descriptions that repeat the phrase 'faq generator' without ever defining what an FAQ generator does, how to create one, what format to use, or any actionable instructions. It provides zero value beyond what the skill's title alone conveys.
Suggestions
Add concrete, executable guidance: include a step-by-step workflow for generating FAQs from source material (e.g., extracting common questions from support tickets, API docs, or user feedback), with specific output format examples.
Provide at least one complete input/output example showing source content and the resulting FAQ in a specific format (e.g., Markdown, JSON-LD FAQ schema).
Define a clear workflow with validation steps, such as: 1) Identify source material, 2) Extract candidate Q&A pairs, 3) Validate coverage and accuracy, 4) Format output in the target schema.
Remove all generic boilerplate ('This skill provides automated assistance...', 'Follows industry best practices...') and replace with actual instructions that teach Claude something it doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'faq generator' excessively, and provides zero substantive information about how to actually generate FAQs. | 1 / 3 |
Actionability | There are no concrete steps, code examples, commands, templates, or executable guidance whatsoever. The skill describes what it could do in abstract terms but never instructs Claude on how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints—just vague claims like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to external files, no structured sections with real content, and no navigation to deeper resources. | 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
4dee593
- 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.