Statement Extract And Prove
OneWave-AI/claude-skills
Converts bank, credit card and brokerage statement PDFs, invoices and vendor price lists into clean CSV or Excel, then proves the extraction is complete and correct - opening balance plus…
Full Productive.io v2 API client — list/get across ~48 resource types (projects, tasks, deals, people, bookings, time entries, invoices, and more), generic create/update/delete, 11 report types, and…
$ npx skills add mvanhorn/printing-press-library --skill pp-productive -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvanhorn/printing-press-library pp-productive --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-skills/pp-productive .claude/skills/pp-productive && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pp-productive" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-productive into .claude/skills/pp-productive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-productive", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-productiveType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mvanhorn/printing-press-library --skill pp-productive -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvanhorn/printing-press-library pp-productive --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-skills/pp-productive .agents/skills/pp-productive && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pp-productive" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-productive into .agents/skills/pp-productive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-productive", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-productive -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvanhorn/printing-press-library pp-productive --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-skills/pp-productive .cursor/skills/pp-productive && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pp-productive" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-productive into .cursor/skills/pp-productive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-productive", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mvanhorn/printing-press-library.git --path cli-skills/pp-productive--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mvanhorn/printing-press-library --skill pp-productive -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvanhorn/printing-press-library pp-productive --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-skills/pp-productive .gemini/skills/pp-productive && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pp-productive" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-productive into .gemini/skills/pp-productive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-productive", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mvanhorn/printing-press-library pp-productiveInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mvanhorn/printing-press-library --skill pp-productive -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-skills/pp-productive .github/skills/pp-productive && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pp-productive" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-productive into .github/skills/pp-productive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-productive", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-productive -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mvanhorn/printing-press-library pp-productive --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-skills/pp-productive .opencode/skills/pp-productive && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pp-productive" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-productive into .opencode/skills/pp-productive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-productive", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
pp-productiveFull Productive.io v2 API client — list/get across ~48 resource types (projects, tasks, deals, people, bookings, time entries, invoices, and more), generic create/update/delete, 11 report types, and…
Pp Productive is an agent skill from mvanhorn/printing-press-library. Full Productive.io v2 API client — list/get across ~48 resource types (projects, tasks, deals, people, bookings, time entries, invoices, and more), generic create/update/delete, 11 report types, and a local sync/search/export/tail data layer, plus first-class revenue-recognition commands (recognized-revenue, invoiced, reconcile, aging). Trigger phrases: list Productive tasks, Productive projects/deals/people/bookings, query the Productive API, recognized revenue by budget, reconcile recognized vs invoiced, pull…
Its SKILL.md is about 5.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering Forms and invoices, Time tracking and reporting and CSV and tabular files. The repository describes itself as: Official library of CLIs generated by the CLI Printing Press. Endorsed, tested, and community-contributed. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 76de244. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
goclaudenpxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
PRODUCTIVE_API_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pp Productive loads about 5.4k tokens when it runs. Until then it costs about 166 tokens; SKILL.md has 2,247 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, BashAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mvanhorn/printing-press-library at commit 76de244, republished under its Apache-2.0 licence (© mvanhorn). 2,247 words, ~5,397 tokens.
.claude/skills/pp-productive/SKILL.md (or your agent's skills folder).<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/productivity/productive/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
This skill drives the productive-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
$HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:npx -y @mvanhorn/printing-press-library install productive --cli-onlyproductive-pp-cli --version$PATH for the agent/runtime that will invoke this skill.If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:
go install github.com/mvanhorn/printing-press-library/library/productivity/productive/cmd/productive-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
A CLI over the entire Productive.io v2 JSON:API — projects, tasks, deals/budgets, people, bookings, time entries, invoices, line items, expenses, and every other resource, each with list/get plus a generic create/update/delete write surface and 11 report types. It removes the MCP token ceiling that forced line-item pulls in 15–20-invoice batches, paginates large result sets to exhaustion, and ships a local SQLite mirror for offline SQL/full-text search. On top of that full-API coverage it adds hand-built revenue-recognition commands (recognized-revenue, invoiced, reconcile, aging).
Use this CLI to extract Productive.io financial data for a revenue-recognition reconciliation pipeline: recognized revenue by budget and month, invoiced amounts via invoice attributions, unpaid receivables, and bulk raw pulls of invoices, line items, and attributions in bulk. It is the right tool when you need paginated, scriptable, offline-queryable financial data rather than interactive chat answers.
Do not use this CLI for:
These capabilities aren't available in any other tool for this API.
recognized-revenue — Pull recognized (earned) revenue grouped by budget and month across a date range in one call.
Reach for this when you need earned revenue per budget per month for revenue recognition — it replaces a chain of manual report calls.
productive-pp-cli recognized-revenue --from 2026-01-01 --to 2026-06-30 --jsoninvoiced — Net finalized invoiced amount attributed per budget per month, drafts reported separately.
Use for the billed side of the ledger when comparing against recognized revenue.
productive-pp-cli invoiced --from 2026-01-01 --to 2026-06-30 --jsonreconcile — Join recognized revenue and invoiced amounts per budget×month and flag the deltas.
This is the reconciliation itself — pick it to surface budgets where earned and billed revenue diverge.
productive-pp-cli reconcile --from 2026-01-01 --to 2026-06-30 --threshold 100 --jsonexport — Stream full paginated pulls of any resource to JSONL or JSON (auto-paginated, no memory pressure).
Use to refresh bulk raw pulls for a downstream pipeline; pair with list --csv when you need CSV.
productive-pp-cli export line_items --format jsonl --output line_items.jsonlsync — Mirror any resource into local SQLite, then query it with SQL and full-text search offline.
Sync once, then run sql/search repeatedly with zero API cost and no rate-limit risk.
productive-pp-cli sync --resources invoices,line_items,invoice_attributions,dealsaging — Bucket unpaid invoice amounts by age past their due date.
Use for a quick receivables snapshot — which invoices are overdue and by how long.
productive-pp-cli aging --as-of 2026-07-04 --jsonactivities — Activity-feed events
productive-pp-cli activities get — Get one activities by idproductive-pp-cli activities list — List activitiesattachments — Uploaded files
productive-pp-cli attachments get — Get one attachments by idproductive-pp-cli attachments list — List attachmentsbookings — Planned work / absence scheduling
productive-pp-cli bookings get — Get one bookings by idproductive-pp-cli bookings list — List bookingscomments — Comments on tasks/deals/etc.
productive-pp-cli comments get — Get one comments by idproductive-pp-cli comments list — List commentscompanies — Client organizations
productive-pp-cli companies get — Get one companies by idproductive-pp-cli companies list — List companiescontact_entries — Contact data (email/phone/address)
productive-pp-cli contact-entries get — Get one contact entries by idproductive-pp-cli contact-entries list — List contact entriescustom_fields — User-defined fields
productive-pp-cli custom-fields get — Get one custom fields by idproductive-pp-cli custom-fields list — List custom fieldsdeal_statuses — Pipeline stages
productive-pp-cli deal-statuses get — Get one deal statuses by idproductive-pp-cli deal-statuses list — List deal statusesdeals — Sales deals and production budgets (filter --stage-type budget for budgets)
productive-pp-cli deals get — Get one deals by idproductive-pp-cli deals list — List dealsevents — Absence categories
productive-pp-cli events get — Get one events by idproductive-pp-cli events list — List eventsexpenses — Non-labor costs on a budget service
productive-pp-cli expenses get — Get one expenses by idproductive-pp-cli expenses list — List expensesfilters — Saved views/reports/widgets
productive-pp-cli filters get — Get one filters by idproductive-pp-cli filters list — List filtersfolders — Collections of task lists (boards) within a project
productive-pp-cli folders get — Get one folders by idproductive-pp-cli folders list — List foldersholiday_calendars — Holiday calendars per country/region
productive-pp-cli holiday-calendars get — Get one holiday calendars by idproductive-pp-cli holiday-calendars list — List holiday calendarsholidays — Non-working days within a holiday calendar
productive-pp-cli holidays get — Get one holidays by idproductive-pp-cli holidays list — List holidaysinvoice_attributions — Invoice<->budget attribution amounts
productive-pp-cli invoice-attributions get — Get one invoice attributions by idproductive-pp-cli invoice-attributions list — List invoice attributionsinvoices — Invoices and credit notes
productive-pp-cli invoices get — Get one invoices by idproductive-pp-cli invoices list — List invoicesline_items — Invoice line items (paginate by --invoice)
productive-pp-cli line-items get — Get one line items by idproductive-pp-cli line-items list — List line itemsmemberships — Access-sharing entries
productive-pp-cli memberships get — Get one memberships by idproductive-pp-cli memberships list — List membershipspages — Rich-text docs pages
productive-pp-cli pages get — Get one pages by idproductive-pp-cli pages list — List pagespayments — Payments and write-offs against invoices
productive-pp-cli payments get — Get one payments by idproductive-pp-cli payments list — List paymentspeople — Employees, contractors, contacts, placeholders
productive-pp-cli people get — Get one people by idproductive-pp-cli people list — List peoplepipelines — Sales/production pipelines
productive-pp-cli pipelines get — Get one pipelines by idproductive-pp-cli pipelines list — List pipelinesprojects — Project workspaces
productive-pp-cli projects get — Get one projects by idproductive-pp-cli projects list — List projectsproposals — Sales quotes for deals
productive-pp-cli proposals get — Get one proposals by idproductive-pp-cli proposals list — List proposalsreports — Aggregated report endpoints
productive-pp-cli reports booking — Scheduling/resourcing reportproductive-pp-cli reports budget — Budget-level tracking reportproductive-pp-cli reports deal — Deal/sales pipeline reportproductive-pp-cli reports expense — Expense reportproductive-pp-cli reports financial-item — Financial line-item report (revenue/cost/profit across sources)productive-pp-cli reports invoice — Invoice report (amounts, tax, payments, aging)productive-pp-cli reports line-item — Invoice line-item reportproductive-pp-cli reports payment — Invoice payments reportproductive-pp-cli reports project — Project portfolio reportproductive-pp-cli reports task — Task report (worked/estimated/remaining)productive-pp-cli reports time-entry — Time tracking report (hours, billable, cost)roles — Permission sets
productive-pp-cli roles get — Get one roles by idproductive-pp-cli roles list — List rolesservice_types — Work categories the org delivers
productive-pp-cli service-types get — Get one service types by idproductive-pp-cli service-types list — List service typesservices — Line items on a deal/budget
productive-pp-cli services get — Get one services by idproductive-pp-cli services list — List servicessubsidiaries — Legal entities within the organization
productive-pp-cli subsidiaries get — Get one subsidiaries by idproductive-pp-cli subsidiaries list — List subsidiariestask_lists — Task groupings (milestones/sprints) within a project
productive-pp-cli task-lists get — Get one task lists by idproductive-pp-cli task-lists list — List task liststasks — Work items in projects
productive-pp-cli tasks get — Get one tasks by idproductive-pp-cli tasks list — List taskstax_rates — Tax/VAT percentages per subsidiary
productive-pp-cli tax-rates get — Get one tax rates by idproductive-pp-cli tax-rates list — List tax ratesteams — Groups of people
productive-pp-cli teams get — Get one teams by idproductive-pp-cli teams list — List teamstime_entries — Logged work time entries
productive-pp-cli time-entries get — Get one time entries by idproductive-pp-cli time-entries list — List time entriestodos — Checklist items on tasks/deals
productive-pp-cli todos get — Get one todos by idproductive-pp-cli todos list — List todosworkflow_statuses — Stages in a task workflow
productive-pp-cli workflow-statuses get — Get one workflow statuses by idproductive-pp-cli workflow-statuses list — List workflow statusesworkflows — Task status groups
productive-pp-cli workflows get — Get one workflows by idproductive-pp-cli workflows list — List workflowsWhen you know what you want to do but not which command does it, ask the CLI directly:
productive-pp-cli which "<capability in your own words>"which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.
productive-pp-cli recognized-revenue --from 2026-01-01 --to 2026-06-30 --jsonThe primary input for revenue reconciliation: earned revenue grouped by budget × month.
productive-pp-cli reconcile --from 2026-01-01 --to 2026-06-30 --threshold 100 --jsonShows budgets where recognized and invoiced revenue diverge beyond the threshold.
productive-pp-cli export line_items --format jsonl --output line_items.jsonlAuto-paginated streaming pull of every line item; use line-items list --csv for CSV instead.
productive-pp-cli recognized-revenue --from 2026-01-01 --to 2026-06-30 --agent --select rows.budget_name,rows.date,rows.total_recognized_revenueUses --select dotted paths to keep only the fields an agent needs from a large report payload.
productive-pp-cli search "Acme" --jsonAfter 'sync' mirrors resources to local SQLite, search runs instant offline FTS (use 'sql' for arbitrary SELECTs).
Productive uses two headers: X-Auth-Token (secret API token) and X-Organization-Id (your org id, not secret). Set PRODUCTIVE_API_TOKEN and PRODUCTIVE_ORGANIZATION_ID. Get a token from Productive → Settings → API access. Run productive-pp-cli doctor to confirm both are set and the API is reachable.
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
Pipeable — JSON on stdout, errors on stderr
Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
productive-pp-cli activities list --agent --select id,name,statusPreviewable — --dry-run shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Writes are explicit — read/list/report commands never mutate; create, update, and delete do (JSON:API envelope, application/vnd.api+json). Preview any write with --dry-run
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.
Agents should treat the CLI's path resolver as part of the runtime contract:
Use --home <dir> for one invocation, or set PRODUCTIVE_HOME=<dir> to relocate all four path kinds under one root.
Use per-kind env vars only when a specific kind must diverge: PRODUCTIVE_CONFIG_DIR, PRODUCTIVE_DATA_DIR, PRODUCTIVE_STATE_DIR, PRODUCTIVE_CACHE_DIR.
Resolution order is per-kind env var, --home, PRODUCTIVE_HOME, XDG (XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME), then platform defaults.
config contains settings like config.toml and profiles. data contains credentials.toml, data.db, cookies, and auth sidecars. state contains persisted queries, jobs, and teach.log. cache contains regenerable HTTP/cache files.
Stored secrets live in credentials.toml under the data dir. Existing legacy config.toml secrets are read for compatibility and leave config.toml on the first auth write.
Run productive-pp-cli doctor --fail-on warn to surface path and credential-location warnings. agent-context exposes a schema v4 paths block for agents that need the resolved dirs.
For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags:
{
"mcpServers": {
"productive": {
"command": "productive-pp-mcp",
"env": {
"PRODUCTIVE_HOME": "/srv/productive"
}
}
}
}Fleet precedence: an inherited per-kind env var overrides an explicit --home for that kind. Use PRODUCTIVE_HOME or per-kind vars as durable fleet levers, and use --home only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing PRODUCTIVE_HOME, or doctor will not find credentials left under the former root.
When you (or the agent) notice something off about this CLI, record it:
productive-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
productive-pp-cli feedback --stdin < notes.txt
productive-pp-cli feedback list --json --limit 10Entries are stored locally as feedback.jsonl under the resolved data dir. They are never POSTed unless PRODUCTIVE_FEEDBACK_ENDPOINT is set AND either --send is passed or PRODUCTIVE_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
productive-pp-cli profile save briefing --json
productive-pp-cli --profile briefing activities list
productive-pp-cli profile list --json
productive-pp-cli profile show briefing
productive-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 4 | Authentication required |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
help, or --help → show productive-pp-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)go install github.com/mvanhorn/printing-press-library/library/productivity/productive/cmd/productive-pp-mcp@latestclaude mcp add productive-pp-mcp -- productive-pp-mcpclaude mcp listwhich productive-pp-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:productive-pp-cli <command> [subcommand] [args] --agentproductive-pp-cli <command> --help.© mvanhorn, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in cli-skills/pp-productive of mvanhorn/printing-press-library.
Open the folder on GitHubat commit 76de244
Pp Productive next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pp Productive this skillmvanhorn/printing-press-library | 2.1k | — | ~5.4k | Automated safety check: Notes | Apache-2.0 | |
| Statement Extract And ProveOneWave-AI/claude-skills | 328 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Remofirst Core Workflow Bjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Kiwi ReceiptsLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.2k | Automated safety check: Pass | MIT | |
| Remofirst Common Errorsjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Journalkazukinagata/shinkoku | 365 | — | ~2.3k | Automated safety check: Pass | MIT |
OneWave-AI/claude-skills
Converts bank, credit card and brokerage statement PDFs, invoices and vendor price lists into clean CSV or Excel, then proves the extraction is complete and correct - opening balance plus…
jeremylongshore/tons-of-skills-marketplace
Manage RemoFirst contractor onboarding from engagement choice through agreement, identity, tax, bank, timesheet, invoice, and first-payout readiness.
LeoYeAI/openclaw-master-skills
NZ tax assistant for sole traders. An agent skill from LeoYeAI/openclaw-master-skills.
jeremylongshore/tons-of-skills-marketplace
Debug RemoFirst contractor payment, invoice, timesheet, and access failures with evidence-safe decision paths.
kazukinagata/shinkoku
This skill should be used when the user wants to record bookkeeping entries (仕訳), import transaction data from CSV files, receipts, or invoices, or manage their general ledger.
LeoYeAI/openclaw-master-skills
Document intelligence: categorize, autofill forms, analyze contracts, scan receipts/invoices, analyze bank statements, parse resumes/CVs, scan IDs/passports (MRZ), summarize medical records, redact…
mvanhorn/printing-press-library
Desktop automation through the real Rust agent-desktop CLI, published in Printing Press through a small bridge.
mvanhorn/printing-press-library
Search, browse, and download Google Fonts from the terminal via the gfonts CLI.
mvanhorn/printing-press-library
The free, offline Trigger phrases: search 1688 for, find a factory on 1688 for, wholesale price on 1688 for, who is the cheapest supplier on 1688 for, compare 1688 suppliers for, use 1688, run 1688.
mvanhorn/printing-press-library
Inspect known Activity Japan plan IDs or URLs, compare dated prices and sessions, check language-sitemap coverage, and hand off to canonical booking pages.
mvanhorn/printing-press-library
Every Admin By Request portal action, plus a local SQLite mirror of audit, events, inventory and requests for ad-hoc...
mvanhorn/printing-press-library
macOS screen capture, window recording, GIF conversion, and agent evidence bundles from the terminal.
Categories
Full Productive.io v2 API client — list/get across ~48 resource types (projects, tasks, deals, people, bookings, time entries, invoices, and more), generic create/update/delete, 11 report types, and…. Pp Productive is an agent skill from mvanhorn/printing-press-library.io v2 API client — list/get across ~48 resource types (projects, tasks, deals, people, bookings, time entries, invoices, and more), generic create/update/delete, 11 report types, and a local sync/search/export/tail data layer, plus first-class revenue-recognition commands (recognized-revenue, invoiced, reconcile, aging).
Pp Productive fits situations like: phrases: list Productive tasks; productive projects/deals/people/bookings; query the Productive API; recognized revenue by budget.
Run `npx skills add mvanhorn/printing-press-library --skill pp-productive -a claude-code`. Or copy the skill folder (cli-skills/pp-productive in mvanhorn/printing-press-library) into .claude/skills/pp-productive in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mvanhorn/printing-press-library --skill pp-productive -a codex`. Or copy the skill folder (cli-skills/pp-productive in mvanhorn/printing-press-library) into .agents/skills/pp-productive in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvanhorn/printing-press-library --skill pp-productive -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pp-productive, .gemini/skills/pp-productive, .github/skills/pp-productive and .opencode/skills/pp-productive in your project.
Going by SKILL.md and its folder, Pp Productive needs the command-line tools its instructions call (go, claude and npx) and credentials named PRODUCTIVE_API_TOKEN. Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Bash.
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Pp Productive is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.4k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pp Productive: Statement Extract And Prove (OneWave-AI/claude-skills, 328 stars), Remofirst Core Workflow B (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Kiwi Receipts (LeoYeAI/openclaw-master-skills, 2.2k stars) and Remofirst Common Errors (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mvanhorn (a GitHub user) maintains it in mvanhorn/printing-press-library, which has 2,056 GitHub stars. The repository holds 506 skills in this directory. The repository was last updated on October 9, 2026.
Source: mvanhorn/printing-press-library on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.