Agent skill
operator-pass-call
Invoke a specific JMC API tool by slug.
From JMC-Go-to-market/claude-operator-pass · 5 skills · 3 · pushed 2026-09-09
What it does when it runs
Invoke a specific JMC API tool by slug. Validates the API key, fetches the per-tool input schema, validates the user's inputs, makes the POST call, and pretty-prints the structured response. Loaded by the main operator-pass skill when the user knows which tool they want.
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- OPERATOR_PASS_API_KEY
- Hosts it reaches
- api.jaymountconsulting.com
- jaymountconsulting.com
- Tool permissions it declares
- Read
- Bash
- WebFetch
- -
- Write
- Actions present in the files
- shellnetwork
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/JMC-Go-to-market/claude-operator-pass.git /tmp/claude-operator-pass git -C /tmp/claude-operator-pass sparse-checkout set "skills/operator-pass-call" mkdir -p ~/.claude/skills/operator-pass-call cp -R "/tmp/claude-operator-pass/skills/operator-pass-call/." ~/.claude/skills/operator-pass-call/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 5 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add JMC-Go-to-market/claude-operator-pass /plugin
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
Before you install: this skill will not complete its job on a bare agent. It needs OPERATOR_PASS_API_KEY, which you have to obtain separately.
The skill
Source on GitHub ↗Reproduced in full from JMC-Go-to-market/claude-operator-pass/blob/60cb540b20986fb5b640c58573377fc6bddbb7d9/skills/operator-pass-call/SKILL.md, which is licensed MIT (skill frontmatter). 491 words, 14 headings.
Operator Pass Call — sub-skill
Invokes a specific JMC API tool by slug.
Activation
Loaded by operator-pass when intent is clear:
- "Run the cold-email-linter on <draft>"
- "Call evp-generator with <inputs>"
- "Use the pipeline calculator"
Workflow
1. Validate the API key
if [ -z "${OPERATOR_PASS_API_KEY:-}" ]; then
echo "OPERATOR_PASS_API_KEY env var is not set."
echo "Get a key at https://jaymountconsulting.com/operator-pass"
exit 1
fi
Or via WebFetch validation:
GET https://api.jaymountconsulting.com/v1/me
Headers: Authorization: Bearer $OPERATOR_PASS_API_KEY
Expect 200 with { "user_id", "plan", "rate_limit_remaining" }.
If 401/403, exit with the subscribe link.
2. Fetch the tool's input schema
GET https://api.jaymountconsulting.com/v1/tools/<slug>/schema
Returns a JSON Schema describing required inputs. Parse it, compare to what the user supplied, and ask for any missing required fields.
3. Validate inputs against the schema
Walk the schema's required array; ensure each is present in the
user's input. Validate types where the schema is strict.
If any required input is missing, ask:
The
<tool-slug>tool needs<field>(<type>,<description>). What should I use?
4. Call the API
curl -sS -X POST "https://api.jaymountconsulting.com/v1/tools/<slug>" \
-H "Authorization: Bearer $OPERATOR_PASS_API_KEY" \
-H "Content-Type: application/json" \
-d '<inputs JSON>'
5. Handle the response
| Status | Meaning | Action |
|---|---|---|
| 200 | Success | Pretty-print the JSON result + offer next step |
| 400 | Bad input | Surface the validation error + retry with corrected input |
| 401 | Invalid key | Tell user to renew via /operator-pass |
| 402 | Subscription expired | Tell user to renew |
| 429 | Rate-limited | Surface the retry-after header value |
| 5xx | API error | Surface the message; suggest retry |
6. Pretty-print + offer next step
Don't dump raw JSON unless asked. Convert to a human-readable summary:
# <Tool name> result
<one-paragraph summary of what was returned>
## Key findings
<bulleted list>
## Suggested next step
<one specific action — e.g., "Want me to draft the fix?" or "Want to
run the same call with <variation>?">
Common errors + their handling
| Error | User-facing message |
|---|---|
| Missing env var | "Set OPERATOR_PASS_API_KEY. Get a key at /operator-pass." |
| Key invalid (401) | "API key invalid or expired. Renew at /operator-pass." |
| Sub expired (402) | "Operator Pass subscription expired. Renew at /operator-pass." |
| Schema mismatch (400) | "Missing field <x> — please provide." |
| Rate-limited (429) | "Rate-limited. Retry in <X seconds> per the API." |
| Unknown slug (404) | "Tool <slug> doesn't exist. Run /operator-pass list." |
Discipline
- Never invent tool results. If the API call fails, say so.
- Never call the API anonymously — always require a key.
- Never retry on 401/402 — those need user action.
- Always show the raw JSON if the user asks (
--rawflag style).
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- call-analysis by Salesably · 50
- cold-call-scripts by Salesably · 50
- 25-cold-call-script-builder by SimonTheSalesBooster · 39
- analyse-call by himanshusaleria · 18
- first-call-rampup by zime-ai · 14
- call-analyzer by octavehq · 11
- forecast-call-prep by elijeangilles · 9
- cold-call-scripts by Frontal-so · 5
Need help setting it up?
This page tells you what operator-pass-call does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.