Skip to content
Back to skills

Export Documents

ASecurity

Prepare and export lixSearch answers as polished PDF documents. Use only when a user explicitly asks to create, save, download, or export content as a PDF.

  • 85 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 3, 2026
devopsrails

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 30, 2026

npx -y skills add elixpo/elixpo_chapter --skill export-documents --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Export Documents?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Export Documents
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/elixpo-export-documents/badge)](https://www.skillsdirectory.com/skills/elixpo-export-documents)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: export-documents
description: Prepare and export lixSearch answers as polished PDF documents. Use only when a user explicitly asks to create, save, download, or export content as a PDF.
---

# Export Documents

Export completed content without repeating research.

## Workflow

1. Accept the canonical finalized Markdown and an optional title. If research is requested in the same turn, wait until sources are fetched and the final synthesis is complete. Never substitute raw research-thread output or status summaries for that synthesis. For a referential follow-up such as "make that a PDF", export the last substantive grounded assistant answer verbatim; do not regenerate or broaden it.
2. Ensure content is non-empty and remove internal task messages.
3. Reject tool syntax, draft preambles, future-work promises, and documents that do not satisfy an explicit requested count or range.
4. Choose a concise subject-based PDF title. Derive the filename as a lowercase hyphenated slug of that title; never derive either from conversational filler, clarification field labels, or the internal resolved-request envelope.
5. Preserve headings, lists, links, citations, and code blocks.
6. Call `export_to_pdf` exactly once. Never call it once per source or once per reasoning turn.
7. Return the download URL unchanged.

## Guardrails

- Depend on synthesis when content is not finalized.
- Never export search snippets, memory excerpts, placeholders, source-count status messages, prior PDF confirmations, errors, or a draft that has not passed synthesis.
- In a continuation, preserve the earlier answer and its citations. Do not replace it with generic background knowledge.
- A successful export must return its stable download URL; after success, stop exporting.
- Do not invent citations or expand source content.
- Do not export without explicit user intent.
- Never export a clarification question or any task whose required fields remain unresolved. Pending clarification is a hard runtime block, not a suggestion.
- Preserve the text response if export fails.

## Runtime contract

    agent: document
    tools: [export_to_pdf]
    timeout_seconds: 20
    max_concurrency: 1
    depends_on: [synthesize-answer]
    output: document_bundle

Files in this skill

  • SKILL.md1.8 KB
  • agents/openai.yaml191 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.