pdf-fill-studio
Fill any PDF locally and place each value precisely in a visual editor. Use when the user wants to fill out a PDF form, enter data into a PDF, complete a tax/insurance/bank form, or position text on a flat/scanned PDF. Handles flat (field-less) PDFs, per-character (comb) fields, and native AcroForm fields; leaves the signature blank for the user to sign.
What this skill does
# pdf-fill-studio Fill a PDF locally, place the values precisely, then export. Flat PDFs use a browser editor; AcroForm PDFs fill natively; the signature is always left blank for the user to sign. ## When to use The user gives you a PDF to fill (form, claim, tax/bank/insurance document). ## Setup (once) `pip install pdf-fill-studio` (provides the `pdf-fill-studio` command). From source instead: `python3 -m venv .venv && .venv/bin/pip install -e .`, then use `.venv/bin/pdf-fill-studio`. ## Flow (Replace `form.pdf` and `profile.json` with the user's actual file paths.) 1. Start: `pdf-fill-studio form.pdf -o out/form_filled.pdf`. It detects the form type. 2. **AcroForm (native fields):** re-run with a profile of known facts: `pdf-fill-studio form.pdf -o out/form_filled.pdf --profile profile.json`. Matched fields fill automatically; it prints "Needs manual input: [...]" for the rest. Ask the user for each listed field, add them to the profile, re-run, then render to verify. 3. **Flat (no fields):** a local browser editor opens. Tell the user to type values, drag boxes onto the lines, nudge with arrow keys, and click "Export PDF". Comb fields (one box per character, e.g. postal code) are detected and filled one character per cell automatically. 4. **XFA:** tell the user this form type is not supported yet (open it in free Adobe Reader). 5. The filled PDF is written to `out/`. The user signs it themselves. ## Self-check (before declaring done) Render and look: `python -m pdf_fill_studio.render_page out/form_filled.pdf out/preview`. Check each value sits on its line / inside its cell, not too low or spilling outside. Apply minimal coordinate corrections and re-bake if needed. ## Rules - Never fill a signature field. - Never store or hard-code a SIN, bank account, or card number (the profile matcher skips them). - Everything runs locally; no document is uploaded.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.