Source profileQuality 68/100

nexu-io/open-design/skills/faq-page/SKILL.md

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".

Source repository stars
91,167
Declared platforms
0
Static risk flags
0
Last source update
2026-08-25
Source checked
2026-08-25
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSourceFAQ

Decision brief

What it does: where it fits

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

Best for

  • Use when the brief asks for "FAQ", "help center", "questions", or "support page".

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/nexu-io/open-design --skill "skills/faq-page"
Safe inspection promptEditorial

Inspect the Agent Skill "faq-page" from https://github.com/nexu-io/open-design/blob/edfa6b5f447e95cb120eae030f03baba00dc34de/skills/faq-page/SKILL.md at commit edfa6b5f447e95cb120eae030f03baba00dc34de. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    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.…

    Read the active DESIGN.md (injected above). Use the component tokens forPick the domain from the brief (e.g., SaaS product, e-commerce, service)Edge cases:
  2. 02

    Output contract

    One sentence before the artifact, nothing after.

    One sentence before the artifact, nothing after.
  3. 03

    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?

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

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score68/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars91,167SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
nexu-io/open-design
Skill path
skills/faq-page/SKILL.md
Commit
edfa6b5f447e95cb120eae030f03baba00dc34de
License
Apache-2.0
Collected
2026-08-25
Default branch
main
View the original 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-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?

Frequently asked questions

What to verify before installation and use

What does the faq-page source document cover?

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

How do I install faq-page?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "skills/faq-page". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing

Computed 10029,034

garrytan/gbrain

bulk-ingestion

End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

2026-08-250 platforms
Computed 10024,921

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

2026-08-240 platforms
Computed 10015,122

wanshuiyin/Auto-claude-code-research-in-sleep

citation-audit

Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.

2026-08-240 platforms
Computed 10014,671

prowler-cloud/prowler

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance

2026-08-240 platforms