AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Operator Pass Call

skill-jmc-go-to-market-claude-operator-pass-operator-pass-call · by JMC-Go-to-market

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.

No reviews yet
0 installs
24 views
0.0% view→install

Install

$ agentstack add skill-jmc-go-to-market-claude-operator-pass-operator-pass-call

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access Used
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jmc-go-to-market-claude-operator-pass-operator-pass-call)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Operator Pass Call? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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 "
  • "Call evp-generator with "
  • "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//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 needs (, `). > What should I use?

4. Call the API

curl -sS -X POST "https://api.jaymountconsulting.com/v1/tools/" \
  -H "Authorization: Bearer $OPERATOR_PASS_API_KEY" \
  -H "Content-Type: application/json" \
  -d ''

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:

#  result

## Key findings

## Suggested next step
?">

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 ` — please provide." | | Rate-limited (429) | "Rate-limited. Retry in per the API." | | Unknown slug (404) | "Tool 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 (--raw flag style).

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.