Skills faq-generator

Generates FAQ lists from complex medical policies or protocols. Trigger when user provides medical documents, policies, or protocols and requests FAQ generation, patient education materials, or simplified explanations.

install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/aipoch-ai/faq-generator" ~/.claude/skills/openclaw-skills-faq-generator && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/aipoch-ai/faq-generator" ~/.openclaw/skills/openclaw-skills-faq-generator && rm -rf "$T"
manifest: skills/aipoch-ai/faq-generator/SKILL.md
source content

FAQ Generator

Creates FAQ lists from medical documents.

Features

  • Automatic Q&A generation
  • Policy interpretation
  • Patient-friendly language
  • Structured formatting

Parameters

ParameterTypeDefaultRequiredDescription
--input
,
-i
string-YesSource document file path
--audience
,
-a
stringgeneralNoTarget audience (patients, researchers, general)
--output
,
-o
stringstdoutNoOutput file path
--format
,
-f
stringjsonNoOutput format (json, markdown, text)

Output Format

{
  "faqs": [{"question": "", "answer": ""}],
  "topic": "string"
}

Risk Assessment

Risk IndicatorAssessmentLevel
Code ExecutionNo scripts includedLow
Network AccessNo external API callsLow
File System AccessRead-only within workspaceLow
Instruction TamperingStandard prompt guidelinesLow
Data ExposureInput/output within sessionLow

Security Checklist

  • No hardcoded credentials or API keys
  • No unauthorized file system access (../)
  • No network requests to external services
  • Output does not expose sensitive information
  • Prompt injection protections in place

Evaluation Criteria

Success Metrics

  • FAQ accurately represents source document content
  • Language is appropriate for specified audience (patients/researchers)
  • Questions cover key points of the document
  • Answers are clear, concise, and medically accurate
  • Format follows structured JSON schema

Test Cases

  1. Basic FAQ Generation: Input simple medical protocol → Output valid FAQ list
  2. Audience Adaptation: Same input with different audiences → Appropriate tone shift
  3. Complex Document: Input lengthy policy document → Comprehensive FAQ coverage
  4. Edge Case: Input ambiguous content → Handles gracefully with clarifying questions

Lifecycle Status

  • Current Stage: Draft
  • Next Review Date: 2026-03-06
  • Known Issues: None
  • Planned Improvements:
    • Add support for multi-language output
    • Enhance medical terminology handling