Faq Generator
Generates FAQ lists from complex medical policies or protocols. Trigger when user provides medical documents, policies, or protocols and requests FAQ generat...
AIpoch
@aipoch-ai
Install
$ openclaw skills install @aipoch-ai/faq-generatorFAQ Generator
Creates FAQ lists from medical documents.
Features
- Automatic Q&A generation
- Policy interpretation
- Patient-friendly language
- Structured formatting
Parameters
| Parameter | Type | Default | Required | Description |
|---|---|---|---|---|
--input, -i | string | - | Yes | Source document file path |
--audience, -a | string | general | No | Target audience (patients, researchers, general) |
--output, -o | string | stdout | No | Output file path |
--format, -f | string | json | No | Output format (json, markdown, text) |
Output Format
{
"faqs": [{"question": "", "answer": ""}],
"topic": "string"
}
Risk Assessment
| Risk Indicator | Assessment | Level |
|---|---|---|
| Code Execution | No scripts included | Low |
| Network Access | No external API calls | Low |
| File System Access | Read-only within workspace | Low |
| Instruction Tampering | Standard prompt guidelines | Low |
| Data Exposure | Input/output within session | Low |
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
- Basic FAQ Generation: Input simple medical protocol → Output valid FAQ list
- Audience Adaptation: Same input with different audiences → Appropriate tone shift
- Complex Document: Input lengthy policy document → Comprehensive FAQ coverage
- 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
Top skills in this category
Playwright (Automation + MCP + Scraper)
@ivangdavilaAutomates, tests, and debugs browsers with Playwright: locators, auto-waiting, traces, CI runs, and MCP browser control. Use when a test is flaky, times out, or fails only in CI or headless; when a locator matches multiple elements or the wrong one (strict mode violation); when clicks need force, waits become sleeps, or networkidle never settles; for storageState and login setup, request mocking and HAR replay, uploads and downloads, iframes and shadow DOM, popups and dialogs, screenshot diffs that change per machine, trace and report artifacts, sharding a slow suite, device and permission emulation, accessibility checks, driving a real browser through Playwright MCP, extracting data from JS-rendered pages, or porting a Cypress, Puppeteer, or Selenium suite to Playwright. Not for maintaining an existing Cypress or Puppeteer suite (cypress, puppeteer) or for work a plain HTTP request answers (http).
Agent Browser
@matrixyHeadless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection
Free Ride - Unlimited free AI
@shaivpidadiManages free AI models from OpenRouter for OpenClaw. Automatically ranks models by quality, configures fallbacks for rate-limit handling, and updates opencla...
Browser Use
@shawnpanaAutomates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with w...
Playwright MCP
@spiceman161Browser automation via Playwright MCP server. Navigate websites, click elements, fill forms, extract data, take screenshots, and perform full browser automation workflows.