# PDF Sign

> Signatures (`pdf-sign`)

- Skill: `samraddhashrivastavatech/pdf-sign` (Agent Skill)
- Install (CLI): `npx skillmds@latest add samraddhashrivastavatech/pdf-sign`
- Raw SKILL.md: https://api.skillmd.com/api/skills/samraddhashrivastavatech/pdf-sign/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: SAMRADDHASHRIVASTAVATECH (https://skillmd.com/u/samraddhashrivastavatech)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/samraddhashrivastavatech/pdf-sign

---

# Signatures  (`pdf-sign`)

Signatures

> Part of the **Universal PDF Management & Creation Skill Repository**.
> Category: **PDF Management**.
> Every skill is individually callable (INDIVIDUAL MODE) and may also be
> invoked automatically by the orchestrator (SYSTEM MODE).

## When to use
Add a signature or inspect signature fields. Visual placement never claims cryptographic validity.

## Operations
- inspect signature fields
- place a visible signature image/text

## Engine (what actually executes this)
`universal_pdf/core.security:sign_pdf / inspect_signatures`

All heavy lifting is done on disk / one page at a time by the shared engine —
never by loading the document into an LLM context.

## Tools & graceful degradation
- Preferred tool: **PyMuPDF widget/image placement**
- Fallback: **pypdf (certificate signature infra)**

If the preferred backend is unavailable the skill transparently uses the
fallback or reports a documented limitation. It **never** reports success when
an operation did not actually happen.

## Validation (this skill attaches checks to its Outcome)
signature placed; clearly reported as visual unless crypto infra used

## Related skills
`pdf-fill-forms`, `pdf-validation`, `pdf-orchestrate`

## Example requests it handles
  * "Place my signature image on the last page."

## Notes
Provenance: outputs cite their source page/section where relevant.