Agent skill

Ops Integrate

by Lifecycle-Innovations-Limited in Lifecycle-Innovations-Limited/claude-ops

OPS on-demand: This skill should be used when the user asks to "add an API", "integrate SaaS", or…

MITAuto-check: notes

Install Ops Integrate

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-integrate -a claude-code

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

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-integrate --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/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-ops/skills/ops-integrate .claude/skills/ops-integrate && 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/

Paste into Claude Code

Install the "ops-integrate" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-integrate into .claude/skills/ops-integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-integrate", 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

$skill-installer install https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-integrate

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

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-integrate -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-integrate --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-ops/skills/ops-integrate .agents/skills/ops-integrate && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ops-integrate" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-integrate into .agents/skills/ops-integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-integrate", 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.

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-integrate -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-integrate --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-ops/skills/ops-integrate .cursor/skills/ops-integrate && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ops-integrate" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-integrate into .cursor/skills/ops-integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-integrate", 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

$ gemini skills install https://github.com/Lifecycle-Innovations-Limited/claude-ops.git --path claude-ops/skills/ops-integrate

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-integrate -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-integrate --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-ops/skills/ops-integrate .gemini/skills/ops-integrate && rm -rf skills-src

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

Paste into Gemini CLI

Install the "ops-integrate" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-integrate into .gemini/skills/ops-integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-integrate", 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.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-integrate

Installs 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).

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-integrate -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-ops/skills/ops-integrate .github/skills/ops-integrate && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "ops-integrate" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-integrate into .github/skills/ops-integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-integrate", 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.

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-integrate -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-integrate --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-ops/skills/ops-integrate .opencode/skills/ops-integrate && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ops-integrate" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-integrate into .opencode/skills/ops-integrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-integrate", 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.

Facts

Skill name: ops-integrate
GitHub stars: 542
Token cost: ~1.1k tokens
SKILL.md length: 231 words
Files: 1
Skills in repo: 67
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

OPS on-demand: This skill should be used when the user asks to "add an API", "integrate SaaS", or…

Works in 5 steps: Discover API details → Confirm with user → Collect credential → …
Asks to add an API
SKILL.md covers Runtime Context, List registered integrations…, Onboarding flow (5 steps) and CLI/API Reference
Calls jq, curl and stripe; reaches api.hubapi.com and api.stripe.com

What it does

Ops Integrate is an agent skill from Lifecycle-Innovations-Limited/claude-ops. OPS on-demand: This skill should be used when the user asks to "add an API", "integrate SaaS", or…

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue… The licence is MIT.

When your agent uses it

Asks to add an API

Example prompts

“add an API”
“integrate SaaS”
“/ops-integrate”

Requirements

Pre-approved tools (allowed-tools): Bash, Read, Write, Edit, AskUserQuestion, WebSearch

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Discover API details
Confirm with user
Collect credential
Health check
Register in partner registry

What it can do on your machine

Read from SKILL.md and the folder at commit 1aa0928. 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:
- Bash
- Read
- Write
- Edit
- AskUserQuestion
- WebSearch
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- jq
- curl
- stripe
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- api.hubapi.com
- api.stripe.com
- api.sendgrid.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ops Integrate loads about 1.1k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 231 words of instructions outside code blocks.

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

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: Bash, Read, Write, Edit, AskUserQuestion, WebSearch

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 Lifecycle-Innovations-Limited/claude-ops at commit 1aa0928, republished under its MIT licence (© Lifecycle-Innovations-Limited). 231 words, ~1,132 tokens.

Download SKILL.mdSave it as .claude/skills/ops-integrate/SKILL.md (or your agent's skills folder).

name: ops-integrate
description: OPS on-demand: This skill should be used when the user asks to "add an API", "integrate SaaS", or…
allowed-tools: Bash, Read, Write, Edit, AskUserQuestion, WebSearch
argument-hint: <service-name> [--url <base-url>] [--auth bearer|api-key|basic|oauth2] [--list]
effort: low
maxTurns: 25

Runtime Context

bash

PREFS="${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json"
PARTNER_REGISTRY=$(jq '.partner_registry // {}' "$PREFS" 2>/dev/null || echo '{}')

Parse $ARGUMENTS:

Contains --list → run List registered integrations then exit
Otherwise → run Onboarding flow with the service name as first positional argument

OPS ► INTEGRATE

Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).

List registered integrations (`--list`)

bash

jq -r '.partner_registry // {} | to_entries[] | "\(.key): \(.value.base_url) [\(.value.auth_type)]"' "$PREFS" 2>/dev/null

Display as a table:

Registered integrations:
  hubspot       https://api.hubapi.com          [bearer]
  stripe        https://api.stripe.com          [bearer]
  sendgrid      https://api.sendgrid.com        [api-key]

If no integrations registered: No integrations registered yet. Run /ops:integrate <service-name> to add one.

Onboarding flow (5 steps)

Step 1 — Discover API details

If --url not provided, use WebSearch to find:

Official API docs URL
Base API URL
Authentication pattern (bearer token / api-key header / basic auth / oauth2)
API key generation URL (where the user gets credentials)
Health/test endpoint (e.g., /healthz, /v1/ping, /me)

Step 2 — Confirm with user

Present findings via AskUserQuestion (≤4 options):

Found: <service-name> API — Base URL: <url> — Auth: <auth-type>
[Looks correct — continue]  [Change base URL]  [Change auth type]  [Cancel]

If "Change base URL": AskUserQuestion with free-text input for the new URL. If "Change auth type": AskUserQuestion (≤4 options): [bearer] [api-key] [basic] [oauth2]

Step 3 — Collect credential

Paste your <service-name> <auth-type> credential (it will be stored locally only)
[Paste now]  [Configure later]

If "Paste now": collect credential via AskUserQuestion free-text. Derive key name: <lowercase_service_name>_api_key

Write to preferences.json via atomic tmpfile swap:

bash

tmp=$(mktemp)
jq --arg k "$KEY_NAME" --arg v "$CREDENTIAL" '.[$k] = $v' "$PREFS" > "$tmp" && mv "$tmp" "$PREFS"

Step 4 — Health check

Curl the health/test endpoint with the credential:

bash

# Bearer token
curl -sf -o /dev/null -w "%{http_code}" \
  -H "Authorization: Bearer ${CREDENTIAL}" \
  "${BASE_URL}${HEALTH_ENDPOINT}"

# API key header (X-Api-Key)
curl -sf -o /dev/null -w "%{http_code}" \
  -H "X-Api-Key: ${CREDENTIAL}" \
  "${BASE_URL}${HEALTH_ENDPOINT}"

# Basic auth
curl -sf -o /dev/null -w "%{http_code}" \
  -u "${CREDENTIAL}:" \
  "${BASE_URL}${HEALTH_ENDPOINT}"

Report: ✅ if HTTP 200-299, ⚠️ with status code otherwise. If credential not yet configured, skip health check and report ⬜ health check skipped — credential not configured.

Step 5 — Register in partner registry

bash

tmp=$(mktemp)
jq --arg name "${SERVICE_NAME}" \
   --arg url "${BASE_URL}" \
   --arg auth "${AUTH_TYPE}" \
   --arg key_name "${KEY_NAME}" \
   --arg health "${HEALTH_ENDPOINT}" \
   '.partner_registry[$name] = {base_url: $url, auth_type: $auth, credential_key: $key_name, health_endpoint: $health, added: (now | todate)}' \
   "$PREFS" > "$tmp" && mv "$tmp" "$PREFS"

Confirmation output:

✅ <service-name> registered in partner registry
   Auth: <auth-type>
   Health: <base-url><health-endpoint>
   Credential key: <key-name>

   Access via: jq '.partner_registry["<service-name>"]' $PREFS

CLI/API Reference

bash

# List all registered integrations
jq '.partner_registry' "${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json"

# Look up a specific integration
jq '.partner_registry["hubspot"]' "$PREFS"

# Read a credential for a registered integration
jq -r ".$KEY_NAME" "$PREFS"

# Remove an integration from the registry
jq 'del(.partner_registry["<service-name>"])' "$PREFS" > tmp && mv tmp "$PREFS"

Files

Just SKILL.md in claude-ops/skills/ops-integrate of Lifecycle-Innovations-Limited/claude-ops.

Open the folder on GitHubat commit 1aa0928

Compare with similar skills

Ops Integrate 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.

Ops Integrate compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ops Integrate this skillLifecycle-Innovations-Limited/claude-ops	542	—	~1.1k	Automated safety check: Notes	MIT	today
Ops Integratedavepoon/buildwithclaude	3.6k	—	~1.1k	Automated safety check: Notes	MIT	today
Integration Testingthedaviddias/Front-End-Checklist	74k	—	~514	Automated safety check: Pass	MIT	3 days ago
Messages Opsaffaan-m/ECC	276k	1 repos	~724	Automated safety check: Pass	MIT	4 days ago
API Integrationsickn33/agentic-awesome-skills	47k	1 repos	~1.3k	Automated safety check: Pass	MIT	today
Labarchive Integrationdavila7/claude-code-templates	32k	10 repos	~2.3k	Automated safety check: Pass	MIT	today

Similar skills

Ops Integrate
davepoon/buildwithclaude
Add any SaaS API as a first-class integration. An agent skill from davepoon/buildwithclaude.
3.6k GitHub stars~1.1k tokensUpdated today
Auto-check: notes
Integration Testing
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Write integration tests for key workflows.
74k GitHub stars~514 tokensUpdated 3 days ago
Testing & QAAuto-check passed
Messages Ops
affaan-m/ECC
Evidence-first live messaging workflow for ECC. An agent skill from affaan-m/ECC.
276k GitHub starsUsed in 1 repo~724 tokens
Productivity & AutomationAuto-check passed
API Integration
sickn33/agentic-awesome-skills
Designs event-driven architectures, webhook systems, API chaining flows, ETL pipelines, and integration patterns between services.
47k GitHub starsUsed in 1 repo~1.3k tokens
Backend & APIsAuto-check passed
Labarchive Integration
davila7/claude-code-templates
Electronic lab notebook API integration. An agent skill from davila7/claude-code-templates.
32k GitHub starsUsed in 10 repos~2.3k tokens
Backend & APIsAuto-check passed
Robius Matrix Integration
sickn33/agentic-awesome-skills
CRITICAL: Use for Matrix SDK integration with Makepad. An agent skill from sickn33/agentic-awesome-skills.
47k GitHub starsUsed in 2 repos~3.6k tokens
Backend & APIsAuto-check passed

Questions about Ops Integrate

What does Ops Integrate do?

OPS on-demand: This skill should be used when the user asks to "add an API", "integrate SaaS", or…. Ops Integrate is an agent skill from Lifecycle-Innovations-Limited/claude-ops.

When should I use Ops Integrate?

Ops Integrate fits situations like: asks to add an API.

How do I install Ops Integrate in Claude Code?

Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-integrate -a claude-code`. Or copy the skill folder (claude-ops/skills/ops-integrate in Lifecycle-Innovations-Limited/claude-ops) into .claude/skills/ops-integrate in your project. Claude Code loads it when a task matches its description.

How do I install Ops Integrate in Codex?

Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-integrate -a codex`. Or copy the skill folder (claude-ops/skills/ops-integrate in Lifecycle-Innovations-Limited/claude-ops) into .agents/skills/ops-integrate in your project. Codex loads it when a task matches its description.

Can I use Ops Integrate 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 Lifecycle-Innovations-Limited/claude-ops --skill ops-integrate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ops-integrate, .gemini/skills/ops-integrate, .github/skills/ops-integrate and .opencode/skills/ops-integrate in your project.

What does Ops Integrate need to run?

Going by SKILL.md and its folder, Ops Integrate needs the command-line tools its instructions call (jq, curl and stripe). Its frontmatter pre-approves these tools: Bash, Read, Write, Edit, AskUserQuestion, WebSearch.

Does Ops Integrate access the network?

SKILL.md names 3 domains. In commands or code: api.hubapi.com, api.stripe.com and api.sendgrid.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Ops Integrate 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 Ops Integrate use?

Ops Integrate is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ops Integrate use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Ops Integrate?

Skills that share tags, products or a category with Ops Integrate: Ops Integrate (davepoon/buildwithclaude, 3.6k stars), Integration Testing (thedaviddias/Front-End-Checklist, 74k stars), Messages Ops (affaan-m/ECC, 276k stars) and API Integration (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ops Integrate?

Lifecycle-Innovations-Limited (a GitHub organization) maintains it in Lifecycle-Innovations-Limited/claude-ops, which has 542 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on October 9, 2026.

Source: Lifecycle-Innovations-Limited/claude-ops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ops Integrate

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Runtime Context

OPS ► INTEGRATE

List registered integrations (--list)

Onboarding flow (5 steps)

Step 1 — Discover API details

Step 2 — Confirm with user

Step 3 — Collect credential

Step 4 — Health check

Step 5 — Register in partner registry

CLI/API Reference

Files

Compare with similar skills

Similar skills

More from Lifecycle-Innovations-Limited/claude-ops

Questions about Ops Integrate

List registered integrations (`--list`)