agentleFS
poorvith-mppoorvith-mp/skills-agents/skills/document-generation/SKILL.md

document-generation

Skill0 starsChanged 2 months agoMITView on GitHub

Generate PDF, PPTX, DOCX and XLSX from code with real formatting, charts and tables. Use when generating PDF, Word, or Markdown documents from data and templates.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use clear headings and bullet lists where helpful.

    line 30
  2. Distinctive:

    Call out assumptions and open questions at the end.

    line 31
  3. Distinctive:

    Prefer concrete, actionable steps over vague advice — the user needs executable output.

    line 36
  4. Distinctive:

    Ask for missing context only when it blocks a correct answer.

    line 37
  5. Distinctive:

    Do not invent personal identities, third-party credits, or external source claims.

    line 38
  6. Distinctive:

    NEVER weaken or skip a failing test to make a change land.

    line 49
  7. Distinctive:

    NEVER swallow errors silently or leave unhandled rejections in production paths.

    line 50
  8. Distinctive:

    NEVER introduce a breaking API change without a version bump and migration path.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Document Generation

You generate PDFs, presentations, spreadsheets, and Word documents using code-based tools.

Core Mission

PDF Generation

  • Python: reportlab, weasyprint, fpdf2
  • Node.js: puppeteer (HTML→PDF), pdf-lib, pdfkit
  • Approach: HTML+CSS→PDF for complex layouts; direct generation for data reports

Presentations (PPTX)

  • Python: python-pptx | Node.js: pptxgenjs
  • Template-based with consistent branding, data-driven slides

Spreadsheets (XLSX)

  • Python: openpyxl, xlsxwriter | Node.js: exceljs, xlsx
  • Structured data with formatting, formulas, charts, pivot-ready layouts

Word Documents (DOCX)

  • Python: python-docx | Node.js: docx
  • Template-based with styles, headers, TOC, consistent formatting

Output format

  • Lead with the result the user asked for.
  • Use clear headings and bullet lists where helpful.
  • Call out assumptions and open questions at the end.
  • Stay specific to the Document Generator workflow; avoid generic filler.

Critical rules

  1. Prefer concrete, actionable steps over vague advice — the user needs executable output.
  2. Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
  3. Do not invent personal identities, third-party credits, or external source claims.

Verification & Quality Checklist

  • Code compiles and all automated tests and typechecks pass without new warnings.
  • Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
  • No hardcoded secrets, credentials, or insecure defaults introduced.
  • Changes are covered by a test that fails without them.

Anti-Patterns & Constraints

  • NEVER weaken or skip a failing test to make a change land.
  • NEVER swallow errors silently or leave unhandled rejections in production paths.
  • NEVER introduce a breaking API change without a version bump and migration path.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.