원클릭으로 Manus에서 모든 스킬 실행

doc-pdf

스타10

포크1

업데이트2026년 7월 22일 17:22

Create, fill, and extract PDFs — when the deliverable is a PDF, not code. Triggers on "generate a PDF", "make a report or invoice PDF", "fill this PDF form", "extract text or tables from a PDF", "HTML to PDF". Picks the right engine: WeasyPrint or headless Chromium for styled HTML-to-PDF reports, ReportLab for programmatic layout, pypdf for form-filling and merge/split, pdfplumber or PyMuPDF for text/table extraction. Keeps output selectable, styled, and accessible — never a page of rasterized text.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

aturzone

aturzone/Skull

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

doc-pdf — create, fill, and extract PDFs

The deliverable is a PDF a human opens. Pick the engine by the job — don't force one library to do all three.

Choose the approach

Styled report / invoice / letter (HTML you control) → render HTML+CSS to PDF.
- WeasyPrint (pip) — best for print CSS (@page, page numbers, running headers/footers); pure-Python, no browser. The default for tabular reports.
- Headless Chromium (Playwright/Puppeteer page.pdf()) — when the layout already renders in a browser or needs web fonts / JS / exact flexbox. Set print media (emulateMedia('print')), else screen CSS leaks in.
Programmatic layout (precise coordinates, tables, charts) → ReportLab (platypus flowables), or fpdf2 for simple cases.
Fill an existing form → pypdf (read fields, set values, optionally flatten) or pdf-lib (JS). Keep the AcroForm unless the user wants it flattened.
Merge / split / rotate / stamp → pypdf.
Extract text or tables → pdfplumber (layout-aware tables) or PyMuPDF / fitz (fast text, images, coordinates). Scanned PDF? OCR first (ocrmypdf / Tesseract).

Recipes (sketch — adapt to the repo's language)

HTML→PDF: build HTML from a Jinja2 template + one print stylesheet, then weasyprint in.html out.pdf.
Data→table PDF: ReportLab Table + TableStyle; repeat header rows; right-align numbers; page breaks.
Form fill: load with pypdf, map field→value from data, write; flatten only if no further editing is needed.

Quality gate

Text stays selectable — never ship rasterized text unless it's genuinely a scan.
Embed fonts; set page size (A4/Letter) and margins; tag for accessibility (structure, alt text) when it matters.
Verify it opens in a real viewer — that the bytes wrote is not proof it renders.

Pitfalls

Chromium page.pdf() uses screen media by default — force print media or your @page rules vanish.
Redaction: drawing a black box does not remove the text underneath. Use PyMuPDF to actually delete the content (and redact PII with sec-pii before the data ever leaves the box).

Learned from the community's document skills (incl. Anthropic's official PDF skill) — re-implemented as guidance over open libraries, not vendored. See docs/ECOSYSTEM.md. Pairs with doc-office and sec-pii.

이 저장소의 다른 Skills

같은 저장소

fe-refactor

aturzone/Skull

Restructure frontend code so it's testable, predictable, and correctly layered — without changing behavior. Pull pure logic out of framework glue, fix reactivity anti-patterns (derived state synced by a watcher/effect, logic in the view, effects with no cleanup, unstable list keys), name and place extractions right (util vs helper vs colocated), and keep the base ← common ← feature dependency one-way. Triggers on "refactor this component", "logic in the template/JSX", "this is hard to test", "watch/useEffect misused", "component does too much", "where does this helper go". Vue & React.

2026-07-2310

fe-token-audit

aturzone/Skull

Find and fix hardcoded design values that bypass the design system — raw hex/rgb/hsl colors, arbitrary Tailwind classes like `bg-[#1f2432]`, inline-style colors, and magic spacing/radius/shadow — and route each through a token. Triggers on "remove hardcoded colors", "use our design tokens", "enforce the design system", "why isn't dark mode working here", or a linter flagging arbitrary values. Complements `fe-design-system` (which defines the tokens); this enforces their use.

2026-07-2310

test-frontend

aturzone/Skull

Test frontend UI code the way it should be tested — risk-scored per file (P0–P3), behavior-not-implementation, boundary-only mocking, and the minimum valuable set. Covers components, composables/hooks, stores, forms, and SSR/hydration safety using the project's own runner (Vitest/Jest + Testing Library / Vue Test Utils, Playwright for E2E). Triggers on "test this component/page", "frontend/Vue/React/Nuxt tests", "component/composable/store tests", "why is this test flaky", "should this be an E2E?". Not for non-UI logic (use test-code) or outside-in black-box QA (use test-blackbox).

2026-07-2310

codescribe

aturzone/Skull

Capture the *why* after a change — the non-obvious knowledge a future developer or agent can't recover by reading the code: hidden constraints, business rules, rejected alternatives, edge-case guards, invisible API contracts, and what silently breaks if the code changes. Triggers on "document this", "write docs for what we built", "capture why this exists", "document the constraints/decisions", "preserve this for future devs" — after a feature, refactor, or bug fix. NOT for README, API docs, code comments, or CHANGELOG — only the knowledge the code can't tell you.

2026-07-2310

skull

aturzone/Skull

The SKULL leader/conductor. Triggers on "skull", "set up skull", "mc setup", "onboard me", "build my team", "what's new", or when starting work in a new/unfamiliar project. It interviews you (grill-me), maps the project, then assembles a tailored team from the installed skills and agents — Sentinel the project cartographer plus planning, review, understanding, guardrail and security specialists — and runs it on your work. It builds the best `.claude/` workspace per project, delegates to parallel subagents (choosing the right model per agent), brainstorms hard and decides fast, keeps a complete view of every installed capability, keeps itself and you current with the newest Claude Code features, and proactively offers the right tool the moment a need shows up.

2026-07-2310

wf-tester

aturzone/Skull

Drive a full QA pass on any project as a SKULL-led tester team — user-end, black-box, code, and stress/load — then emit a charted skull.html status dashboard. Triggers on "test everything", "QA this", "full test pass", "is it ready to ship", "pre-release check", "the app has no tests", "test this app end to end". Not for a single unit test (use cap-tdd) or a security audit (use wf-security-audit).

2026-07-2310

name	doc-pdf
description	Create, fill, and extract PDFs — when the deliverable is a PDF, not code. Triggers on "generate a PDF", "make a report or invoice PDF", "fill this PDF form", "extract text or tables from a PDF", "HTML to PDF". Picks the right engine: WeasyPrint or headless Chromium for styled HTML-to-PDF reports, ReportLab for programmatic layout, pypdf for form-filling and merge/split, pdfplumber or PyMuPDF for text/table extraction. Keeps output selectable, styled, and accessible — never a page of rasterized text.
allowed-tools	Read, Grep, Glob, Bash, Write, Edit

doc-pdf — create, fill, and extract PDFs

The deliverable is a PDF a human opens. Pick the engine by the job — don't force one library to do all three.

Choose the approach

Styled report / invoice / letter (HTML you control) → render HTML+CSS to PDF.
- WeasyPrint (pip) — best for print CSS (@page, page numbers, running headers/footers); pure-Python, no browser. The default for tabular reports.
- Headless Chromium (Playwright/Puppeteer page.pdf()) — when the layout already renders in a browser or needs web fonts / JS / exact flexbox. Set print media (emulateMedia('print')), else screen CSS leaks in.
Programmatic layout (precise coordinates, tables, charts) → ReportLab (platypus flowables), or fpdf2 for simple cases.
Fill an existing form → pypdf (read fields, set values, optionally flatten) or pdf-lib (JS). Keep the AcroForm unless the user wants it flattened.
Merge / split / rotate / stamp → pypdf.
Extract text or tables → pdfplumber (layout-aware tables) or PyMuPDF / fitz (fast text, images, coordinates). Scanned PDF? OCR first (ocrmypdf / Tesseract).

Recipes (sketch — adapt to the repo's language)

HTML→PDF: build HTML from a Jinja2 template + one print stylesheet, then weasyprint in.html out.pdf.
Data→table PDF: ReportLab Table + TableStyle; repeat header rows; right-align numbers; page breaks.
Form fill: load with pypdf, map field→value from data, write; flatten only if no further editing is needed.

Quality gate

Text stays selectable — never ship rasterized text unless it's genuinely a scan.
Embed fonts; set page size (A4/Letter) and margins; tag for accessibility (structure, alt text) when it matters.
Verify it opens in a real viewer — that the bytes wrote is not proof it renders.

Pitfalls

Chromium page.pdf() uses screen media by default — force print media or your @page rules vanish.
Redaction: drawing a black box does not remove the text underneath. Use PyMuPDF to actually delete the content (and redact PII with sec-pii before the data ever leaves the box).