Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
nexu-io avatar

Faq Page

  • 1.7k installs
  • 82k repo stars
  • Updated July 28, 2026
  • nexu-io/open-design

faq-page is an agent skill that agent skill for faq-page workflows documented in skill.md.

About

faq-page is an agent skill from nexu-io/open-design that agent skill for faq-page workflows documented in skill.md. # FAQ Page Skill Produce a single FAQ page with collapsible accordion sections, search, and category filtering. ## Workflow 1. **Read the active DESIGN.md** (injected above). Use the component tokens for interactive elements (accordion headers, search input, category pills). 2. **Pick the domain** from the brief (e.g., SaaS product, e-commerc Developers invoke faq-page during operate/infra work for cloud & infrastructure tasks. The skill documents triggers, prerequisites, and step-by-step workflows grounded in SKILL.md. Compatible with Claude Code, Cursor, and Codex agent runtimes that load marketplace skills. Review the Security Audits panel on this listing before installing in production environments. Category Cloud & Infrastructure with operations vertical focus supports repeatable agent-guided delivery.

  • Produce a single FAQ page with collapsible accordion sections, search, and category filtering.
  • 1. **Read the active DESIGN.md** (injected above). Use the component tokens for
  • interactive elements (accordion headers, search input, category pills).
  • 2. **Pick the domain** from the brief (e.g., SaaS product, e-commerce, service)
  • and write 12–18 real FAQ entries across 3–4 categories.

Faq Page by the numbers

  • 1,736 all-time installs (skills.sh)
  • +122 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #206 of 1,041 Cloud & Infrastructure skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

faq-page capabilities & compatibility

Capabilities
produce a single faq page with collapsible accor · 1. **read the active design.md** (injected above · interactive elements (accordion headers, search · 2. **pick the domain** from the brief (e.g., saa · and write 12–18 real faq entries across 3–4 cate
Use cases
orchestration
From the docs

What faq-page says it does

Produce a single FAQ page with collapsible accordion sections, search, and category filtering.
SKILL.md
1. **Read the active DESIGN.md** (injected above). Use the component tokens for
SKILL.md
interactive elements (accordion headers, search input, category pills).
SKILL.md
npx skills add https://github.com/nexu-io/open-design --skill faq-page

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.7k
repo stars82k
Security audit3 / 3 scanners passed
Last updatedJuly 28, 2026
Repositorynexu-io/open-design

What it does

Agent skill for faq-page workflows documented in SKILL.md.

Who is it for?

Developers working on cloud & infrastructure during operate tasks.

Skip if: Tasks outside Cloud & Infrastructure scope described in SKILL.md.

When should I use this skill?

Agent skill for faq-page workflows documented in SKILL.md.

What you get

Completed cloud & infrastructure workflow aligned with SKILL.md steps.

  • index.html FAQ page
  • Accordion and search components

By the numbers

  • Design system requires 4 sections: color, typography, layout, components
  • Craft checklist includes 3 requirements: typography, accessibility-baseline, state-coverage
  • Lists 8 trigger phrases including FAQ, help center, support page, and Q&A

Files

SKILL.mdMarkdownGitHub ↗

FAQ Page Skill

Produce a single FAQ page with collapsible accordion sections, search, and category filtering.

Workflow

1. Read the active DESIGN.md (injected above). Use the component tokens for interactive elements (accordion headers, search input, category pills). 2. Pick the domain from the brief (e.g., SaaS product, e-commerce, service) and write 12–18 real FAQ entries across 3–4 categories.

  • Edge cases:
  • If the brief provides fewer than 8 FAQs, ask for more content or generate

realistic questions based on the domain.

  • For 1–5 FAQs, skip categories and search; show a simple list.
  • For very long answers (>100 words), break into paragraphs or bullet points

to maintain readability. 3. Sections, in order:

  • Header — page title ("Frequently Asked Questions" or "Help Center"),

optional subtitle (1 sentence explaining what users can find here).

  • Search bar — prominent search input with placeholder text and icon.

Functional JS to filter questions in real-time.

  • Category filters — 3–4 pill-style buttons to filter by category

(e.g., "Billing", "Account", "Technical", "General"). "All" selected by default.

  • FAQ accordion — collapsible question/answer pairs:
  • Question as clickable header with expand/collapse icon (chevron or plus/minus).
  • Answer hidden by default, expands on click with smooth animation.
  • Each entry has data-category attribute for filtering.
  • Footer CTA — "Still have questions?" section with contact link or

support email. 4. Write a single HTML document:

  • <!doctype html> through </html>, CSS and JS inline.
  • Accordion uses semantic HTML (<details> and <summary> for progressive

enhancement, or custom JS with proper ARIA attributes).

  • Search filters questions by matching text in question or answer.
  • Category filters show/hide questions based on data-category.
  • Smooth transitions for expand/collapse (max-height or grid-template-rows).
  • data-od-id on header, search, categories, accordion container, footer.

5. Self-check:

  • Questions are specific and realistic (not generic placeholders).
  • Answers are concise (2–4 sentences) but complete.
  • Keyboard navigation works (Tab through questions, Enter to expand).
  • Search is case-insensitive and filters by matching text.
  • Only one accordion item expanded at a time (optional, depends on UX preference).
  • Mobile-friendly (accordion headers are tappable, search is usable).

Output contract

Emit between <artifact> tags:

<artifact identifier="faq-page" type="text/html" title="FAQ Page">
<!doctype html>
<html>...</html>
</artifact>

One sentence before the artifact, nothing after.

Example questions by category

Billing

  • How do I update my payment method?
  • What payment methods do you accept?
  • Can I get a refund?
  • How do I cancel my subscription?

Account

  • How do I reset my password?
  • Can I change my email address?
  • How do I delete my account?
  • What happens to my data after I cancel?

Technical

  • What browsers do you support?
  • Is there a mobile app?
  • How do I export my data?
  • What are your API rate limits?

General

  • What is [Product Name]?
  • How do I get started?
  • Do you offer customer support?
  • Where can I find your terms of service?

Related skills

How it compares

Pick faq-page for a self-contained interactive FAQ prototype; pick a docs CMS skill when content is managed at scale with versioning.

FAQ

What does faq-page do?

Agent skill for faq-page workflows documented in SKILL.md.

When should I use faq-page?

During operate infra work for cloud & infrastructure.

Is faq-page safe to install?

Review the Security Audits panel on this listing before production use.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.