Revenue Operations
cbrock84/headcount
Runs the mechanics of the revenue engine — lead lifecycle definitions, routing, CRM hygiene, forecasting process, pipeline reporting, and the marketing-to-sales handoff.
The Copper CRM command line no one else built: full CRUD plus a local database, weighted pipeline forecasting, stale-deal detection, and the bulk operations Copper's own API refuses to provide.
$ npx skills add mvanhorn/printing-press-library --skill pp-copper -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvanhorn/printing-press-library pp-copper --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-copper .claude/skills/pp-copper && 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-copper" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-copper into .claude/skills/pp-copper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-copper", 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-copperType 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-copper -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvanhorn/printing-press-library pp-copper --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-copper .agents/skills/pp-copper && 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-copper" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-copper into .agents/skills/pp-copper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-copper", 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-copper -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvanhorn/printing-press-library pp-copper --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-copper .cursor/skills/pp-copper && 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-copper" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-copper into .cursor/skills/pp-copper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-copper", 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-copper--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-copper -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvanhorn/printing-press-library pp-copper --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-copper .gemini/skills/pp-copper && 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-copper" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-copper into .gemini/skills/pp-copper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-copper", 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-copperInstalls 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-copper -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-copper .github/skills/pp-copper && 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-copper" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-copper into .github/skills/pp-copper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-copper", 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-copper -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-copper --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-copper .opencode/skills/pp-copper && 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-copper" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-copper into .opencode/skills/pp-copper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-copper", 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-copperThe Copper CRM command line no one else built: full CRUD plus a local database, weighted pipeline forecasting, stale-deal detection, and the bulk operations Copper's own API refuses to provide.
Pp Copper is an agent skill from mvanhorn/printing-press-library. The Copper CRM command line no one else built: full CRUD plus a local database, weighted pipeline forecasting, stale-deal detection, and the bulk operations Copper's own API refuses to provide. Trigger phrases: forecast my copper pipeline, find stale deals in copper, bulk update copper opportunities, log a call in copper, dedupe copper contacts, use copper, run copper.
Its SKILL.md is about 4.6k 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 Data & Analytics, covering Forecasting and time series. 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 0fdcc7a. 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:
COPPER_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pp Copper loads about 4.6k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 1,980 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 0fdcc7a, republished under its Apache-2.0 licence (© mvanhorn). 1,980 words, ~4,640 tokens.
.claude/skills/pp-copper/SKILL.md (or your agent's skills folder).<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/sales-and-crm/copper/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 copper-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 copper --cli-onlycopper-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/sales-and-crm/copper/cmd/copper-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.
Copper has no CLI, no Go client, and no agent-native tool. This turns a click-heavy web CRM into a scriptable, offline-queryable surface. It mirrors people, companies, leads, opportunities, projects, tasks, and activities into local SQLite, then adds the weighted forecast (forecast), cold-deal sweep (stale), and rate-limit-aware bulk editor (bulk) that the API and web UI leave out.
Use this CLI for scripted or agent-driven Copper work: weighted pipeline forecasting, finding and acting on stale deals, mass field updates across many opportunities, idempotent contact sync, and offline cross-entity queries. It is the right tool when the web UI would mean repetitive clicking or when a spreadsheet export would be stale on arrival.
Do not use this CLI for:
These capabilities aren't available in any other tool for this API.
forecast — Weighted expected-revenue roll-up: sums monetary_value x win_probability over open opportunities, grouped by stage, assignee, or close-month.
Reach for this instead of exporting CSV and pivoting by hand for any expected-revenue or commit/quota question.
copper-pp-cli forecast --pipeline 12345 --by stage --agentstale — Surfaces open opportunities with no interaction in N days, sorted by staleness x value, across all reps.
Use to find deals going cold before they die; pipe the output into bulk reassign.
copper-pp-cli stale --days 21 --by assignee --agentwho — Joins an opportunity to its company, people, and recent activities into one related-records view.
Use for one-call deal prep before nudging or logging a touch.
copper-pp-cli who opportunity:88 --agentbulk — Applies field updates (stage, owner, custom fields) across many opportunities with bounded concurrency and heuristic 429 backoff.
Use for mass updates to existing records; the safe way to avoid the rate-limit wall a naive loop hits.
copper-pp-cli bulk move --query stale.json --set pipeline_stage_id=9 --concurrency 4 --dry-runupsert — Match-then-create-or-update for people and leads; normalizes the people.emails[] vs leads.email shape difference.
Use to sync external rows without creating duplicates; not a blind create.
copper-pp-cli upsert person --match email --file contacts.json --dry-rundedupe — Local SQLite self-join surfacing people or leads that share an email, name, or company.
Run before or after a sync to catch duplicate contacts the API will not flag.
copper-pp-cli dedupe people --on email --agentlog — Creates an activity with the type resolved by name (bumps interaction_count); log fix deletes and recreates to edit an immutable activity.
Use to log or correct a single touch; for the same touch across many records use bulk.
copper-pp-cli log call --on opportunity:88 --note "Left voicemail"account — Account details
copper-pp-cli account — Fetch account detailsactivities — Manage activities (notes and logged interactions)
copper-pp-cli activities create — Create a new activitycopper-pp-cli activities delete — Delete an activitycopper-pp-cli activities get — Fetch an activity by idcopper-pp-cli activities search — List/search activitiesactivity-types — Activity types
copper-pp-cli activity-types — List all activity typescompanies — Manage companies
copper-pp-cli companies activities — List a company's activitiescopper-pp-cli companies create — Create a new companycopper-pp-cli companies delete — Delete a companycopper-pp-cli companies get — Fetch a company by idcopper-pp-cli companies search — List/search companiescopper-pp-cli companies update — Update a companycontact-types — Contact types
copper-pp-cli contact-types — List all contact typescustom-activity-types — Custom activity types
copper-pp-cli custom-activity-types create — Create a new custom activity typecopper-pp-cli custom-activity-types get — Fetch a custom activity type by idcopper-pp-cli custom-activity-types list — List all custom activity typescopper-pp-cli custom-activity-types update — Update a custom activity typecustom-field-definitions — Custom field definitions
copper-pp-cli custom-field-definitions create — Create a new custom field definitioncopper-pp-cli custom-field-definitions delete — Delete a custom field definitioncopper-pp-cli custom-field-definitions get — Fetch a custom field definition by idcopper-pp-cli custom-field-definitions list — List all custom field definitionscopper-pp-cli custom-field-definitions update — Update a custom field definitioncustomer-sources — Customer (lead) sources
copper-pp-cli customer-sources — List all customer sourceslead-statuses — Lead statuses
copper-pp-cli lead-statuses — List all lead statusesleads — Manage leads
copper-pp-cli leads activities — List a lead's activitiescopper-pp-cli leads convert — Convert a lead into a person/company/opportunitycopper-pp-cli leads create — Create a new leadcopper-pp-cli leads delete — Delete a leadcopper-pp-cli leads get — Fetch a lead by idcopper-pp-cli leads search — List/search leadscopper-pp-cli leads update — Update a leadcopper-pp-cli leads upsert — Create or update a lead, matched by email or a custom fieldloss-reasons — Opportunity loss reasons
copper-pp-cli loss-reasons — List all loss reasonsopportunities — Manage opportunities (deals)
copper-pp-cli opportunities create — Create a new opportunitycopper-pp-cli opportunities delete — Delete an opportunitycopper-pp-cli opportunities get — Fetch an opportunity by idcopper-pp-cli opportunities search — List/search opportunitiescopper-pp-cli opportunities update — Update an opportunitypeople — Manage people (contacts)
copper-pp-cli people activities — List a person's activitiescopper-pp-cli people create — Create a new personcopper-pp-cli people delete — Delete a personcopper-pp-cli people fetch-by-email — Fetch a person by email addresscopper-pp-cli people get — Fetch a person by idcopper-pp-cli people search — List/search peoplecopper-pp-cli people update — Update a personpipeline-stages — Pipeline stages
copper-pp-cli pipeline-stages — List all pipeline stagespipelines — Sales pipelines
copper-pp-cli pipelines list — List all pipelinescopper-pp-cli pipelines stages — List stages within a specific pipelineprojects — Manage projects
copper-pp-cli projects create — Create a new projectcopper-pp-cli projects delete — Delete a projectcopper-pp-cli projects get — Fetch a project by idcopper-pp-cli projects search — List/search projectscopper-pp-cli projects update — Update a projecttags — Tags used across records
copper-pp-cli tags — List all tagstasks — Manage tasks
copper-pp-cli tasks create — Create a new taskcopper-pp-cli tasks delete — Delete a taskcopper-pp-cli tasks get — Fetch a task by idcopper-pp-cli tasks search — List/search taskscopper-pp-cli tasks update — Update a taskusers — Users in the account
copper-pp-cli users get — Fetch a user by idcopper-pp-cli users search — List/search userswebhooks — Webhook subscriptions
copper-pp-cli webhooks create — Create a new webhook subscriptioncopper-pp-cli webhooks delete — Delete (unsubscribe) a webhook subscriptioncopper-pp-cli webhooks get — Fetch a webhook subscription by idcopper-pp-cli webhooks list — List all webhook subscriptionsWhen you know what you want to do but not which command does it, ask the CLI directly:
copper-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.
copper-pp-cli forecast --by assignee --agent --select assignee_name,weighted_value,open_valueCommit view per rep without a spreadsheet pivot.
copper-pp-cli stale --days 30 --by assignee --agentList cold deals grouped by owner. Save the JSON, then feed the ids into the bulk reassign command (with --set assignee_id=<id>) to mass-reassign — preview with --dry-run before applying.
copper-pp-cli upsert person --match email --file leads.json --dry-runCreate-or-update external rows without duplicating contacts.
copper-pp-cli who opportunity:88 --agent --select company.name,people.name,activities.detailsPull the deal's company, contacts, and recent touches in one narrowed view.
Copper uses a multi-header API key. Set COPPER_API_KEY (System Settings -> API Keys -> Create a Key) and COPPER_USER_EMAIL (the email of the key owner). Every request sends X-PW-AccessToken, X-PW-UserEmail, and X-PW-Application: developer_api.
Run copper-pp-cli doctor to verify setup.
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:
copper-pp-cli account --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
Explicit retries — use --idempotent only when an already-existing create should count as success, and --ignore-missing only when a missing delete target should count as success
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 COPPER_HOME=<dir> to relocate all four path kinds under one root.
Use per-kind env vars only when a specific kind must diverge: COPPER_CONFIG_DIR, COPPER_DATA_DIR, COPPER_STATE_DIR, COPPER_CACHE_DIR.
Resolution order is per-kind env var, --home, COPPER_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 copper-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": {
"copper": {
"command": "copper-pp-mcp",
"env": {
"COPPER_HOME": "/srv/copper"
}
}
}
}Fleet precedence: an inherited per-kind env var overrides an explicit --home for that kind. Use COPPER_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 COPPER_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:
copper-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
copper-pp-cli feedback --stdin < notes.txt
copper-pp-cli feedback list --json --limit 10Entries are stored locally as feedback.jsonl under the resolved data dir. They are never POSTed unless COPPER_FEEDBACK_ENDPOINT is set AND either --send is passed or COPPER_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.
copper-pp-cli profile save briefing --json
copper-pp-cli --profile briefing account
copper-pp-cli profile list --json
copper-pp-cli profile show briefing
copper-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 copper-pp-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)go install github.com/mvanhorn/printing-press-library/library/sales-and-crm/copper/cmd/copper-pp-mcp@latestclaude mcp add copper-pp-mcp -- copper-pp-mcpclaude mcp listwhich copper-pp-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:copper-pp-cli <command> [subcommand] [args] --agentcopper-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-copper of mvanhorn/printing-press-library.
Open the folder on GitHubat commit 0fdcc7a
Pp Copper 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 Copper this skillmvanhorn/printing-press-library | 2.1k | — | ~4.6k | Automated safety check: Notes | Apache-2.0 | |
| Revenue Operationscbrock84/headcount | 2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| ForecastTheCraigHewitt/skills | 157 | — | ~5.2k | Automated safety check: Pass | MIT | |
| Shopify Inventory Managementnexscope-ai/eCommerce-Skills | 1.1k | — | ~480 | Automated safety check: Pass | MIT | |
| TimesFM Forecastinggoogle-research/timesfm | 34k | — | ~4.7k | Automated safety check: Pass | Apache-2.0 | |
| Timesfm ForecastingzLanqing/codex-claude-academic-skills | 4.6k | 6 repos | ~7.5k | Automated safety check: Notes | Apache-2.0 |
cbrock84/headcount
Runs the mechanics of the revenue engine — lead lifecycle definitions, routing, CRM hygiene, forecasting process, pipeline reporting, and the marketing-to-sales handoff.
TheCraigHewitt/skills
When the user wants to forecast sales revenue, build a commit/upside/best-case forecast, calculate weighted pipeline, predict whether they'll hit their number, or run a forecast call.
nexscope-ai/eCommerce-Skills
Multi-location inventory — transfers, low stock alerts, demand forecasting, safety stock, ABC analysis
google-research/timesfm
Forecasts any univariate time series zero-shot with Google's TimesFM model, returning point forecasts and calibrated prediction intervals without training.
zLanqing/codex-claude-academic-skills
Zero-shot time series forecasting with Google's TimesFM foundation model.
zLanqing/codex-claude-academic-skills
Statistical models library for Python. An agent skill from zLanqing/codex-claude-academic-skills.
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
The Copper CRM command line no one else built: full CRUD plus a local database, weighted pipeline forecasting, stale-deal detection, and the bulk operations Copper's own API refuses to provide. Pp Copper is an agent skill from mvanhorn/printing-press-library. The Copper CRM command line no one else built: full CRUD plus a local database, weighted pipeline forecasting, stale-deal detection, and the bulk operations Copper's own API refuses to provide.
Pp Copper fits situations like: phrases: forecast my copper pipeline; find stale deals in copper; bulk update copper opportunities; log a call in copper.
Run `npx skills add mvanhorn/printing-press-library --skill pp-copper -a claude-code`. Or copy the skill folder (cli-skills/pp-copper in mvanhorn/printing-press-library) into .claude/skills/pp-copper in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mvanhorn/printing-press-library --skill pp-copper -a codex`. Or copy the skill folder (cli-skills/pp-copper in mvanhorn/printing-press-library) into .agents/skills/pp-copper 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-copper -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-copper, .gemini/skills/pp-copper, .github/skills/pp-copper and .opencode/skills/pp-copper in your project.
Going by SKILL.md and its folder, Pp Copper needs the command-line tools its instructions call (go, claude and npx) and credentials named COPPER_API_KEY. 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 Copper 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 4.6k tokens (SKILL.md is roughly 19k 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 Copper: Revenue Operations (cbrock84/headcount, 2k stars), Forecast (TheCraigHewitt/skills, 157 stars), Shopify Inventory Management (nexscope-ai/eCommerce-Skills, 1.1k stars) and TimesFM Forecasting (google-research/timesfm, 34k 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,053 GitHub stars. The repository holds 505 skills in this directory. The repository was last updated on October 7, 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.