Tessl • The package manager for agent skills

SkillPublic

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

88%

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

88%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 strong, executable spec: a precise workflow, a self-check checklist, and an exact output contract. Its only real inefficiency is the appended example-question catalog, which pads token cost without adding much Claude doesn't already know.

Suggestions

Condense 'Example questions by category' to 2–3 exemplar entries per category (or a one-line note on tone/specificity) to save ~15 lines of token budget.

Add a one-line error-recovery hint to the self-check (e.g., 'if any check fails, fix and re-verify before emitting') to strengthen the feedback loop.

Optionally move the full example-question bank to a references file and keep a pointer in SKILL.md for cleaner progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is directive and lean (specific counts, semantic HTML, animation techniques, exact artifact contract), but the 24-line 'Example questions by category' appendix is content Claude could largely generate itself and could be trimmed or condensed.	4 / 5
Actionability	Fully actionable for an instruction-only skill: 12–18 entries across 3–4 categories, ordered section spec, data-category/data-od-id attributes, edge cases for low FAQ counts, and a copy-paste-ready artifact output contract — no gaps in executable guidance.	5 / 5
Workflow Clarity	A clear five-step numbered sequence (read design → pick domain → sections → write → self-check) capped by an explicit self-check checklist covering keyboard navigation, search behavior, and mobile usability. This is not a destructive or batch operation, so no validation cap applies.	5 / 5
Progressive Disclosure	A single well-sectioned file with clear headers and no nested or dangling references (the only external mention, DESIGN.md, is environment-injected). It sits just over the ~50-line simple-skill threshold, and the example-questions block is borderline content that could live in a reference file, so structure is good but not exemplary.	4 / 5
	Total	18 / 20 Passed

Description

83%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.

A strong description: concrete capabilities, an explicit 'Use when' clause with natural trigger phrases, and a distinct FAQ niche. The only weaknesses are feature-styled (rather than action-styled) phrasing and a couple of missing trigger synonyms.

Suggestions

Lead with a verb to state capabilities as actions, e.g., 'Builds a FAQ page with collapsible accordion sections, search, and category filtering'.

Add missing natural trigger synonyms such as 'Q&A' and 'knowledge base' to the 'Use when' clause so the description matches the frontmatter triggers list.

Tighten the trigger 'questions' to something less collision-prone (e.g., 'FAQ questions') to reduce overlap with quiz/survey-style briefs.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete capabilities ('collapsible accordion sections, search functionality, and category filtering'), but these are stated as product features rather than explicit actions, leaving minor coverage gaps relative to the comprehensive-action anchor.	4 / 5
Completeness	Explicitly answers both what ('A FAQ page with collapsible accordion sections, search functionality, and category filtering') and when ('Use when the brief asks for...') with concrete trigger phrases, exactly matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural terms users would say — 'FAQ', 'help center', 'questions', 'support page' — plus the spelled-out 'Frequently Asked Questions', but a few natural variations (e.g., 'Q&A', 'knowledge base') are missing from the description itself.	4 / 5
Distinctiveness Conflict Risk	FAQ/help-center is a clear niche with distinct triggers, but 'questions' is a common word that could plausibly fire on non-FAQ briefs (quizzes, surveys), creating minor overlap risk rather than minimal.	4 / 5
	Total	17 / 20 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
Revision: 78d5637

Reviewed: 17 days ago

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.

faq-page

Table of Contents

Is this your skill?