Back to Phase 1

Skill Definition WF2 - Bundle Browser

Source: c92 skill-definition — wireframe 2. Argument: a skill is a directory on disk, and the honest way to show it is as one — a file tree on the left, the selected file raw on the right, SKILL.md open by default. What you see is byte-for-byte what the harness will read.

fixture
/inventory/skills/detail?skill=pdf
Harness Inventory › Skills › pdf
✦pdf
configured/claude-cli/ never invoked at runtime
Installs
12
Metadata
NamepdfDescriptionUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Harness typesclaude-cliPeople9
Show all metadata
Installs
12
with this skill configured
People
9
who own those installs
Sessions
31
on those installs · could have run it, not did
Invocations
0
no harness emits skill calls yet
FilesInstallsSessionsSurface← new sections in bold

Files

12 · 48.8 KB · ~/.claude/skills/pdf

The skill directory as scanned on the canonical install. ● referenced from SKILL.md · ⚙ executable.

scripts/
6 referenced · 6 bundled only · 8 executable
SKILL.md7.9 KB314 linessha256 bc37f77b0644modified 2026-09-02copydownload
name pdflicense Proprietary. LICENSE.txt has complete termsinvocation: model + usertools: (unrestricted — no allowed-tools)
1---
2name: pdf
3description: Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
4license: Proprietary. LICENSE.txt has complete terms
5---
6# PDF Processing Guide
7
8## Overview
9
10This guide covers essential PDF processing operations using Python libraries and command-line tools. For advanced features, JavaScript libraries, and detailed examples, see REFERENCE.md. If you need to fill out a PDF form, read FORMS.md and follow its instructions.
11
12## Quick Start
13
14```python
15from pypdf import PdfReader, PdfWriter
16
17# Read a PDF
18reader = PdfReader("document.pdf")
19print(f"Pages: {len(reader.pages)}")
20
21# Extract text
22text = ""
23for page in reader.pages:
24 text += page.extract_text()
25```
26
27## Python Libraries
28
29### pypdf - Basic Operations
30
31**Merge PDFs**
32
33```python
34writer = PdfWriter()
35for pdf_file in ["doc1.pdf", "doc2.pdf"]:
36 reader = PdfReader(pdf_file)
37 for page in reader.pages:
38 writer.add_page(page)
39with open("merged.pdf", "wb") as output:
40 writer.write(output)
41```
42
43### pdfplumber - Text and Table Extraction
44
45Use `scripts/extract_form_structure.py` to dump the field tree before filling a form, and `scripts/check_bounding_boxes.py` to validate placement afterwards.
46
47## Command-Line Tools
48
49- `pdftotext -layout in.pdf out.txt` keeps column layout
50- `qpdf --decrypt --password=… in.pdf out.pdf` strips owner encryption
51- `gs -sDEVICE=pdfwrite -dPDFSETTINGS=/ebook` compresses for email
52
53## Scanned PDFs
54
55Run OCR (`ocrmypdf --skip-text`) first; the extraction recipes above only see the text layer.
Installs — 12 with this skill configured
as built (providers-skills, 2026-09-22) — unchanged by this option
Sessions — 31 on those installs, past 7 days
as built (providers-skills, 2026-09-22) — unchanged by this option
Surface
as built (providers-skills, 2026-09-22) — unchanged by this option

Readout

Best for the audit posture — a security reviewer wants the artifact, not a rendering of it, and the browser makes the scripts as visible as the prose (docx's script tree is 40 files; the prose is 91 lines). Every file is one click and the meta header (hash · size · mode · modified) is the evidence line. Weakest as reading: a 300-line instruction file as numbered raw text is a wall, and frontmatter semantics (invocation policy, tools) stay implicit unless the header decodes them.

Costs: the inspector must ship the full file inventory with per-file hashes and modes, and a bounded fetch for any text file's contents (a size cap, and a denylist for binaries); nothing rendered, so no Markdown pipeline needed.

Qpoint Brand Style Guide