faq-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill faq-generatorFaq Generator - Auto-activating skill for Technical Documentation. Triggers on: faq generator, faq generator Part of the Technical Documentation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks concrete actions, meaningful trigger terms, and any guidance on when Claude should select this skill. The redundant trigger terms and generic category reference provide almost no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates FAQ sections from existing documentation, extracts common questions from support tickets, formats Q&A pairs in markdown'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user asks to create FAQs, frequently asked questions, Q&A sections, help documentation, or knowledge base articles'
Remove the duplicate trigger term and expand to include variations users would naturally say: 'FAQ', 'FAQs', 'frequently asked questions', 'Q&A', 'help section'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Faq Generator' and 'Technical Documentation' without describing any concrete actions. There are no specific capabilities listed like 'generates FAQ sections from documentation' or 'extracts common questions from user feedback'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundantly listed as 'faq generator, faq generator' (duplicated). Missing natural variations users might say like 'FAQ', 'frequently asked questions', 'Q&A section', 'help documentation', or 'knowledge base'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'FAQ Generator' is somewhat specific to a particular output type, the vague 'Technical Documentation' category could overlap with many documentation-related skills. The lack of specific triggers increases conflict risk. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual substance. It contains zero actionable information about FAQ generation - no format specifications, no examples of good FAQs, no process for extracting questions from documentation, and no code or commands. The entire content could be replaced with 'This skill helps with FAQ generation' without losing any information.
Suggestions
Add concrete examples of FAQ format and structure (e.g., markdown templates, JSON schemas for structured FAQs)
Include a clear workflow: 1) Identify common questions from docs/support tickets, 2) Write clear answers, 3) Organize by category, 4) Validate completeness
Provide executable code or commands for FAQ generation automation (e.g., extracting questions from documentation, formatting output)
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with specific, actionable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about FAQ generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no code, no commands, no examples of FAQ format, no actual instructions on how to generate FAQs. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no process, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for actual learning. No references to detailed materials, no examples section, no clear organization of content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.