Agent skill

Pp Copper

by mvanhorn in 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.

Apache-2.0Auto-check: notesData & Analytics

Install Pp Copper

skills CLI
$ npx skills add mvanhorn/printing-press-library --skill pp-copper -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mvanhorn/printing-press-library pp-copper --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
pp-copper
GitHub stars
2.1k
Token cost
~4.6k tokens
SKILL.md length
1,980 words
Files
1
Skills in repo
505
Repo updated
First seen
Licence
Apache-2.0

At a glance

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.

  • Works in 3 steps: Install via the Printing Press… → Verify: copper-pp-cli --version → Ensure the reported install directory is…
  • Phrases: forecast my copper pipeline
  • SKILL.md covers Prerequisites: Install the CLI, When to Use This CLI, Anti-triggers and Unique Capabilities, plus 12 more sections
  • Calls go, claude and npx; needs COPPER_API_KEY

What it does

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.

When your agent uses it

  • Phrases: forecast my copper pipeline
  • Find stale deals in copper
  • Bulk update copper opportunities
  • Log a call in copper

Example prompts

  • “/pp-copper”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): Read, Bash

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and…
  2. Verify: copper-pp-cli --version
  3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

What it can do on your machine

Read from SKILL.md and the folder at commit 0fdcc7a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • go
    • claude
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    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.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • COPPER_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k

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.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash

Automated 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.

SKILL.md

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.

Download SKILL.mdSave it as .claude/skills/pp-copper/SKILL.md (or your agent's skills folder).
name
pp-copper
description
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`.
allowed-tools
Read, Bash
author
Kerry Morrison
license
Apache-2.0
argument-hint
<command> [args] | install cli|mcp
<!-- 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/". -->

Copper — Printing Press CLI

Prerequisites: Install the CLI

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:

  1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:
    bash
    npx -y @mvanhorn/printing-press-library install copper --cli-only
  2. Verify: copper-pp-cli --version
  3. Ensure the reported install directory is on $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:

bash
go install github.com/mvanhorn/printing-press-library/library/sales-and-crm/copper/cmd/copper-pp-cli@latest

If --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.

When to Use This CLI

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.

Anti-triggers

Do not use this CLI for:

  • Configuring Copper account settings, billing, or user provisioning (use the web app)
  • Editing a logged activity in place (Copper activities are immutable; use log fix to delete+recreate)
  • OAuth-based multi-tenant distribution to other Copper orgs (partner-gated; this CLI uses personal API-key auth)

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Pipeline intelligence
  • 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.

    bash
    copper-pp-cli forecast --pipeline 12345 --by stage --agent
  • stale — 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.

    bash
    copper-pp-cli stale --days 21 --by assignee --agent
  • who — 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.

    bash
    copper-pp-cli who opportunity:88 --agent
Operations Copper's API refuses to provide
  • bulk — 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.

    bash
    copper-pp-cli bulk move --query stale.json --set pipeline_stage_id=9 --concurrency 4 --dry-run
  • upsert — 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.

    bash
    copper-pp-cli upsert person --match email --file contacts.json --dry-run
  • dedupe — 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.

    bash
    copper-pp-cli dedupe people --on email --agent
CRM hygiene
  • log — 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.

    bash
    copper-pp-cli log call --on opportunity:88 --note "Left voicemail"

Command Reference

account — Account details

  • copper-pp-cli account — Fetch account details

activities — Manage activities (notes and logged interactions)

  • copper-pp-cli activities create — Create a new activity
  • copper-pp-cli activities delete — Delete an activity
  • copper-pp-cli activities get — Fetch an activity by id
  • copper-pp-cli activities search — List/search activities

activity-types — Activity types

  • copper-pp-cli activity-types — List all activity types

companies — Manage companies

  • copper-pp-cli companies activities — List a company's activities
  • copper-pp-cli companies create — Create a new company
  • copper-pp-cli companies delete — Delete a company
  • copper-pp-cli companies get — Fetch a company by id
  • copper-pp-cli companies search — List/search companies
  • copper-pp-cli companies update — Update a company

contact-types — Contact types

  • copper-pp-cli contact-types — List all contact types

custom-activity-types — Custom activity types

  • copper-pp-cli custom-activity-types create — Create a new custom activity type
  • copper-pp-cli custom-activity-types get — Fetch a custom activity type by id
  • copper-pp-cli custom-activity-types list — List all custom activity types
  • copper-pp-cli custom-activity-types update — Update a custom activity type

custom-field-definitions — Custom field definitions

  • copper-pp-cli custom-field-definitions create — Create a new custom field definition
  • copper-pp-cli custom-field-definitions delete — Delete a custom field definition
  • copper-pp-cli custom-field-definitions get — Fetch a custom field definition by id
  • copper-pp-cli custom-field-definitions list — List all custom field definitions
  • copper-pp-cli custom-field-definitions update — Update a custom field definition

customer-sources — Customer (lead) sources

  • copper-pp-cli customer-sources — List all customer sources

lead-statuses — Lead statuses

  • copper-pp-cli lead-statuses — List all lead statuses

leads — Manage leads

  • copper-pp-cli leads activities — List a lead's activities
  • copper-pp-cli leads convert — Convert a lead into a person/company/opportunity
  • copper-pp-cli leads create — Create a new lead
  • copper-pp-cli leads delete — Delete a lead
  • copper-pp-cli leads get — Fetch a lead by id
  • copper-pp-cli leads search — List/search leads
  • copper-pp-cli leads update — Update a lead
  • copper-pp-cli leads upsert — Create or update a lead, matched by email or a custom field

loss-reasons — Opportunity loss reasons

  • copper-pp-cli loss-reasons — List all loss reasons

opportunities — Manage opportunities (deals)

  • copper-pp-cli opportunities create — Create a new opportunity
  • copper-pp-cli opportunities delete — Delete an opportunity
  • copper-pp-cli opportunities get — Fetch an opportunity by id
  • copper-pp-cli opportunities search — List/search opportunities
  • copper-pp-cli opportunities update — Update an opportunity

people — Manage people (contacts)

  • copper-pp-cli people activities — List a person's activities
  • copper-pp-cli people create — Create a new person
  • copper-pp-cli people delete — Delete a person
  • copper-pp-cli people fetch-by-email — Fetch a person by email address
  • copper-pp-cli people get — Fetch a person by id
  • copper-pp-cli people search — List/search people
  • copper-pp-cli people update — Update a person

pipeline-stages — Pipeline stages

  • copper-pp-cli pipeline-stages — List all pipeline stages

pipelines — Sales pipelines

  • copper-pp-cli pipelines list — List all pipelines
  • copper-pp-cli pipelines stages — List stages within a specific pipeline

projects — Manage projects

  • copper-pp-cli projects create — Create a new project
  • copper-pp-cli projects delete — Delete a project
  • copper-pp-cli projects get — Fetch a project by id
  • copper-pp-cli projects search — List/search projects
  • copper-pp-cli projects update — Update a project

tags — Tags used across records

  • copper-pp-cli tags — List all tags

tasks — Manage tasks

  • copper-pp-cli tasks create — Create a new task
  • copper-pp-cli tasks delete — Delete a task
  • copper-pp-cli tasks get — Fetch a task by id
  • copper-pp-cli tasks search — List/search tasks
  • copper-pp-cli tasks update — Update a task

users — Users in the account

  • copper-pp-cli users get — Fetch a user by id
  • copper-pp-cli users search — List/search users

webhooks — Webhook subscriptions

  • copper-pp-cli webhooks create — Create a new webhook subscription
  • copper-pp-cli webhooks delete — Delete (unsubscribe) a webhook subscription
  • copper-pp-cli webhooks get — Fetch a webhook subscription by id
  • copper-pp-cli webhooks list — List all webhook subscriptions
Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

bash
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.

Recipes

Monday weighted forecast by rep
bash
copper-pp-cli forecast --by assignee --agent --select assignee_name,weighted_value,open_value

Commit view per rep without a spreadsheet pivot.

Show full SKILL.md (856 more words)Show less
Sweep then bulk-reassign cold deals
bash
copper-pp-cli stale --days 30 --by assignee --agent

List 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.

Idempotent contact import
bash
copper-pp-cli upsert person --match email --file leads.json --dry-run

Create-or-update external rows without duplicating contacts.

One-call deal prep
bash
copper-pp-cli who opportunity:88 --agent --select company.name,people.name,activities.details

Pull the deal's company, contacts, and recent touches in one narrowed view.

Auth Setup

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.

Agent Mode

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:

    bash
    copper-pp-cli account --agent --select id,name,status
  • Previewable — --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

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

json
{
  "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.

Paths and state

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:

    json
    {
      "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.

Agent Feedback

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 10

Entries 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.

Output Delivery

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:

SinkEffect
stdoutDefault; 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.

Named Profiles

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 --yes

Explicit 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.

Exit Codes

CodeMeaning
0Success
2Usage error (wrong arguments)
3Resource not found
4Authentication required
5API error (upstream issue)
7Rate limited (wait and retry)
10Config error

Argument Parsing

Parse $ARGUMENTS:

  1. Empty, help, or --help → show copper-pp-cli --help output
  2. Starts with install → ends with mcp → MCP installation; otherwise → see Prerequisites above
  3. Anything else → Direct Use (execute as CLI command with --agent)

MCP Server Installation

  1. Install the MCP server:
    bash
    go install github.com/mvanhorn/printing-press-library/library/sales-and-crm/copper/cmd/copper-pp-mcp@latest
  2. Register with Claude Code:
    bash
    claude mcp add copper-pp-mcp -- copper-pp-mcp
  3. Verify: claude mcp list

Direct Use

  1. Check if installed: which copper-pp-cli If not found, offer to install (see Prerequisites at the top of this skill).
  2. Match the user query to the best command from the Unique Capabilities and Command Reference above.
  3. Execute with the --agent flag:
    bash
    copper-pp-cli <command> [subcommand] [args] --agent
  4. If ambiguous, drill into subcommand help: copper-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

Files

Just SKILL.md in cli-skills/pp-copper of mvanhorn/printing-press-library.

Open the folder on GitHubat commit 0fdcc7a

Compare with similar skills

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.

Pp Copper compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pp Copper this skillmvanhorn/printing-press-library2.1k—~4.6kAutomated safety check: NotesApache-2.0
Revenue Operationscbrock84/headcount2k—~1.2kAutomated safety check: PassMIT
ForecastTheCraigHewitt/skills157—~5.2kAutomated safety check: PassMIT
Shopify Inventory Managementnexscope-ai/eCommerce-Skills1.1k—~480Automated safety check: PassMIT
TimesFM Forecastinggoogle-research/timesfm34k—~4.7kAutomated safety check: PassApache-2.0
Timesfm ForecastingzLanqing/codex-claude-academic-skills4.6k6 repos~7.5kAutomated safety check: NotesApache-2.0

Similar skills

  • 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.

    2k GitHub stars~1.2k tokensUpdated 20 days ago
    Data & AnalyticsAuto-check passed
  • Forecast

    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.

    157 GitHub stars~5.2k tokensUpdated 4 mo ago
    Data & AnalyticsAuto-check passed
  • Shopify Inventory Management

    nexscope-ai/eCommerce-Skills

    Multi-location inventory — transfers, low stock alerts, demand forecasting, safety stock, ABC analysis

    1.1k GitHub stars~480 tokensUpdated 1 mo ago
    Data & AnalyticsAuto-check passed
  • TimesFM Forecasting

    google-research/timesfm

    Forecasts any univariate time series zero-shot with Google's TimesFM model, returning point forecasts and calibrated prediction intervals without training.

    34k GitHub stars~4.7k tokensUpdated 8 days ago
    Data & AnalyticsAuto-check passed
  • Timesfm Forecasting

    zLanqing/codex-claude-academic-skills

    Zero-shot time series forecasting with Google's TimesFM foundation model.

    4.6k GitHub starsUsed in 6 repos~7.5k tokens
    Data & AnalyticsAuto-check: notes
  • Statsmodels

    zLanqing/codex-claude-academic-skills

    Statistical models library for Python. An agent skill from zLanqing/codex-claude-academic-skills.

    4.6k GitHub starsUsed in 16 repos~4.9k tokens
    Data & AnalyticsAuto-check passed

More from mvanhorn/printing-press-library

All 505 skills in this repo
  • Agent Desktop

    mvanhorn/printing-press-library

    Desktop automation through the real Rust agent-desktop CLI, published in Printing Press through a small bridge.

    2.1k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check: notes
  • Gfonts

    mvanhorn/printing-press-library

    Search, browse, and download Google Fonts from the terminal via the gfonts CLI.

    2.1k GitHub stars~574 tokensUpdated yesterday
    Auto-check passed
  • Pp 1688

    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.

    2.1k GitHub stars~3k tokensUpdated yesterday
    Auto-check: notes
  • Pp Activity Japan

    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.

    2.1k GitHub stars~2k tokensUpdated yesterday
    Auto-check: notes
  • Pp Adminbyrequest

    mvanhorn/printing-press-library

    Every Admin By Request portal action, plus a local SQLite mirror of audit, events, inventory and requests for ad-hoc...

    2.1k GitHub stars~3.3k tokensUpdated yesterday
    Auto-check: notes
  • Pp Agent Capture

    mvanhorn/printing-press-library

    macOS screen capture, window recording, GIF conversion, and agent evidence bundles from the terminal.

    2.1k GitHub stars~1.6k tokensUpdated yesterday
    Auto-check: notes

Questions about Pp Copper

What does Pp Copper do?

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.

When should I use Pp Copper?

Pp Copper fits situations like: phrases: forecast my copper pipeline; find stale deals in copper; bulk update copper opportunities; log a call in copper.

How do I install Pp Copper in Claude Code?

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.

How do I install Pp Copper in Codex?

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.

Can I use Pp Copper in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Pp Copper need to run?

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.

Does Pp Copper access the network?

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.

Is Pp Copper safe to install?

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.

What licence does Pp Copper use?

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.

How many tokens does Pp Copper use?

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.

What are the alternatives to Pp Copper?

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.

Who maintains Pp Copper?

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.