faq-page

A Frequently Asked Questions (FAQ) page with collapsible accordion sections, search functionality, and category filtering. Use when the brief asks for "FAQ", "help center", "questions", or "support page".

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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 lean, well-structured, single-purpose skill with a clear sequenced workflow and a validation self-check. Its main gap is the absence of an executable HTML/CSS/JS starter template, leaving the implementation entirely described rather than copy-paste ready.

Suggestions

Add a minimal inline HTML/CSS/JS scaffold (doctype, a single accordion item with details/summary, the search input, and one category pill) so the skill provides copy-paste-ready code instead of only describing it.

Include one concrete CSS snippet for the smooth expand/collapse (e.g. grid-template-rows: 0fr/1fr transition) and one JS snippet for case-insensitive search filtering, since the skill currently only names these techniques.

Show a short example of the data-od-id and data-category attributes applied to actual markup so the attribute guidance is unambiguous and directly reusable.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not explain what a FAQ, HTML, or ARIA is, and every section (workflow, output contract, example questions) earns its place, matching the score-3 'lean and efficient' anchor.	3 / 3
Actionability	Guidance is concrete (exact data-category/data-od-id attributes, details/summary or ARIA, case-insensitive search, max-height transitions) but no executable HTML/CSS/JS scaffold is provided and the output contract uses a '<html>...</html>' placeholder, so it falls short of the score-3 'copy-paste ready code' anchor for a code-producing skill.	2 / 3
Workflow Clarity	A clear 5-step sequence (Read DESIGN.md, Pick domain, Sections, Write, Self-check) ends with an explicit validation checklist of six checkpoints, matching the score-3 'clear sequence with explicit validation steps' anchor; no destructive/batch feedback loop is required here.	3 / 3
Progressive Disclosure	Content is appropriately self-contained with well-organized sections (Workflow, Output contract, Example questions by category) and no nested or dangling references, fitting the score-3 'clear overview, well-organized' anchor for a skill that needs no external files.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 concise, third-person, and explicitly covers both capabilities and trigger conditions with natural user terms. It hits every dimension at the top of the scale.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'collapsible accordion sections, search functionality, and category filtering' — matching the score-3 anchor rather than the single-action score-2 example.	3 / 3
Completeness	Clearly answers both what (an FAQ page with accordion/search/filtering) and when (explicit 'Use when the brief asks for...' trigger clause), satisfying the score-3 anchor; it is not the score-2 case where 'when' is only implied.	3 / 3
Trigger Term Quality	The 'Use when' clause supplies natural terms users would say — 'FAQ', 'help center', 'questions', 'support page' — giving good coverage rather than the sparse score-2 case.	3 / 3
Distinctiveness Conflict Risk	The FAQ/help-center niche with accordion and filtering triggers is distinct and unlikely to fire for unrelated skills, matching the score-3 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/faq-page/SKILL.md
Commit: f2760fd

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

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.