PDF Mechanics
Role
The mechanical layer for PDF work. Domain skills (legal, finance, regulatory packets) decide what the document should say. This skill decides how to produce it correctly. Domain skills delegate here rather than re-derive PDF mechanics each session.
Scope: PDF only. DOCX track-changes, XLSX, image manipulation belong in their own skills.
First step: inspect, then choose path
SOURCE GOAL PATH
────── ──── ────
PDF (encrypted) anything decrypt first → re-inspect
PDF (AcroForm fields > 0) fill scripts/fill_acroform.py
PDF (AcroForm fields > 0) redline overlay onto AcroForm; fill is for values, not markup
PDF (flat, 0 fields) fill scripts/fill_overlay.py
PDF (flat, 0 fields) redline scripts/render_redlines.py
Markdown generate PDF scripts/markdown_to_pdf.py
More from usetemi/skills
google-drive
Manage Google Drive files with manifest-tracked push/pull workflows via rclone. Use when the user needs to download, upload, list, or manage files on Google Drive shared drives.
22google-search-console
Query Google Search Console analytics, inspect URL indexing status, manage sitemaps, and run PageSpeed Insights audits. Use when the user needs SEO data, search performance reports, indexing diagnostics, or Core Web Vitals analysis.
15google-analytics
Query GA4 reports (users, sessions, conversions, funnels, realtime), manage properties / data streams / key events / custom dimensions / audiences / access bindings, and send Measurement Protocol events via the `ga4` CLI. Use this skill whenever the user mentions GA4, Google Analytics, property IDs starting with `properties/`, tracking events, engagement or traffic metrics, attribution, conversions, key events, audiences, BigQuery links, access roles, or realtime users — even if they don't explicitly say "GA4". Do not use for Google Search Console (see google-search-console skill) or generic web analytics where the source isn't GA4 (ask first).
14template-skill
Replace with a clear description of what this skill does and when Claude should use it. Be specific about trigger words and use cases.
14humanize
Remove signs of AI-generated writing from text. Use when editing, reviewing, or rewriting prose to make it sound natural and human-written, or when the user says "humanize this", "make this sound human", "remove AI-isms", "this sounds AI-generated", or invokes /humanize. Based on Wikipedia's "Signs of AI writing" guide. Detects and fixes 29 patterns including inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, copula avoidance, passive voice, negative parallelisms, sycophantic tone, and filler phrases.
2harness-engineering
Use when improving a codebase for agent legibility, setting up agent workflows, designing AGENTS.md files, eliminating AI slop via linting, or structuring repos for autonomous coding agent delegation. Triggers on tasks involving agent-first development, coding agent optimization, or scaling engineering throughput with agents.
2