Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
Connect external tracing providers to Overmind, inspect connector health, review capability-boundary mappings and verify imported traces.
Install Overmind Integrations
$ npx skills add overmind-core/overmind --skill overmind-integrations -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install overmind-core/overmind overmind-integrations --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/overmind-core/overmind.git skills-src && mkdir -p .claude/skills && cp -r skills-src/overmind/skills/overmind-integrations .claude/skills/overmind-integrations && 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 "overmind-integrations" agent skill from https://github.com/overmind-core/overmind/tree/main/overmind/skills/overmind-integrations into .claude/skills/overmind-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overmind-integrations", 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/overmind-core/overmind/tree/main/overmind/skills/overmind-integrationsType 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 overmind-core/overmind --skill overmind-integrations -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install overmind-core/overmind overmind-integrations --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/overmind-core/overmind.git skills-src && mkdir -p .agents/skills && cp -r skills-src/overmind/skills/overmind-integrations .agents/skills/overmind-integrations && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "overmind-integrations" agent skill from https://github.com/overmind-core/overmind/tree/main/overmind/skills/overmind-integrations into .agents/skills/overmind-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overmind-integrations", 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 overmind-core/overmind --skill overmind-integrations -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install overmind-core/overmind overmind-integrations --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/overmind-core/overmind.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/overmind/skills/overmind-integrations .cursor/skills/overmind-integrations && 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 "overmind-integrations" agent skill from https://github.com/overmind-core/overmind/tree/main/overmind/skills/overmind-integrations into .cursor/skills/overmind-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overmind-integrations", 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/overmind-core/overmind.git --path overmind/skills/overmind-integrations--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 overmind-core/overmind --skill overmind-integrations -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install overmind-core/overmind overmind-integrations --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/overmind-core/overmind.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/overmind/skills/overmind-integrations .gemini/skills/overmind-integrations && 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 "overmind-integrations" agent skill from https://github.com/overmind-core/overmind/tree/main/overmind/skills/overmind-integrations into .gemini/skills/overmind-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overmind-integrations", 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 overmind-core/overmind overmind-integrationsInstalls 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 overmind-core/overmind --skill overmind-integrations -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/overmind-core/overmind.git skills-src && mkdir -p .github/skills && cp -r skills-src/overmind/skills/overmind-integrations .github/skills/overmind-integrations && 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 "overmind-integrations" agent skill from https://github.com/overmind-core/overmind/tree/main/overmind/skills/overmind-integrations into .github/skills/overmind-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overmind-integrations", 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 overmind-core/overmind --skill overmind-integrations -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install overmind-core/overmind overmind-integrations --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/overmind-core/overmind.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/overmind/skills/overmind-integrations .opencode/skills/overmind-integrations && 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 "overmind-integrations" agent skill from https://github.com/overmind-core/overmind/tree/main/overmind/skills/overmind-integrations into .opencode/skills/overmind-integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overmind-integrations", 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
overmind-integrations- GitHub stars
- 597
- Token cost
- ~772 tokens
- SKILL.md length
- 362 words
- Files
- 3 (incl. assets)
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Connect external tracing providers to Overmind, inspect connector health, review capability-boundary mappings and verify imported traces.
- The Integrations surface
- SKILL.md covers Inspect and authenticate, Review the mapping and Sync and verify
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Repository SDK instrumentation belongs to Observability
What it does
Overmind Integrations is an agent skill from overmind-core/overmind. Connect external tracing providers to Overmind, inspect connector health, review capability-boundary mappings and verify imported traces. Use for the Integrations surface; repository SDK instrumentation belongs to Observability.
Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including assets (for example `agents/openai.yaml`).
It sits in DevOps & Cloud, covering Observability. The repository describes itself as: The platform for continuously improving AI agents. The licence is AGPL-3.0.
When your agent uses it
- The Integrations surface
- Repository SDK instrumentation belongs to Observability
Example prompts
- “/overmind-integrations”
What it can do on your machine
Read from SKILL.md and the folder at commit 3dec73c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Overmind Integrations loads about 772 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 362 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.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
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 overmind-core/overmind at commit 3dec73c, republished under its AGPL-3.0 licence (© overmind-core). 362 words, ~772 tokens.
Download SKILL.mdSave it as
.claude/skills/overmind-integrations/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- overmind-integrations
- description
- Connect external tracing providers to Overmind, inspect connector health, review capability-boundary mappings and verify imported traces. Use for the Integrations surface; repository SDK instrumentation belongs to Observability.
Overmind Integrations
Start with list_projects and choose the intended accessible project. For an
account connection, pass its project_id on every project tool and resource
URI query; follow returned links. Project API keys retain their narrower access.
Bring external traces into the correct project with explicit boundary mapping.
Use the configured Overmind MCP connection and read overmind://project/current?project_id=ID.
The provider's source project and the Overmind destination are different identities.
Inspect and authenticate
Start with inspect_connectors. For a supported provider, prefer the native
connect-traces prompt. Use the server's available provider list and setup
commands rather than assuming that a named service is supported.
Credentials are not MCP arguments. If inspection returns
connector_setup_required, show its CLI command and let the human enter the
provider credential in their terminal. Do not ask for a key in chat, export it,
or run an interactive credential flow in a non-TTY sandbox. Read
overmind://connector-setup for the current handoff. Continue after the human
confirms completion or supplies the non-secret connector ID.
Review the mapping
Inspect the connector with include_source_projects=true. Resolve the chosen
source project and lookback. Examine observation_shapes, suggested_boundaries,
alternatives, unmapped_roots and mapping_options.
mapping.names declares capability boundaries that become Overmind trace roots.
Default to the suggested parent observation names so children remain nested.
An alternative can replace that parent when chosen; do not include both it and
its ancestor. Tool/LLM spans and other nested names are not independent roots
unless the human chooses that boundary.
Show full SKILL.md (126 more words)Show less
Use configure_connector to propose the selected source, lookback and mapping
without confirm_mapping. Present the concrete mapping and the import-unmapped
option, then wait for its review. After approval, confirm that same mapping with
confirm_mapping=true. Do not silently broaden the import window or destination.
Sync and verify
Run the authorized sync_connector, poll with
get_job(kind=connector_sync, id=...), then query the imported traces. Report imported/skipped counts, failed work and remaining
unmapped roots from the actual result. A stored credential or confirmed mapping
is not proof that traces arrived.
For inspection-only work, read overmind://connectors/{connector} and status
without starting another sync. There are no MCP deletion or credential-rotation
tools to invent.
Return the source/destination identities, mapping decision, sync outcome and
console_traces_url. For configuration, open observability/integrations under
the project's Console base with its projectId.
© overmind-core, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (assets) in overmind/skills/overmind-integrations of overmind-core/overmind.
- SKILL.md
- agents/openai.yaml
- assets/icon.png
Open the folder on GitHubat commit 3dec73c
Compare with similar skills
Overmind Integrations 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 |
|---|---|---|---|---|---|---|
| Overmind Integrations this skillovermind-core/overmind | 597 | — | ~772 | Automated safety check: Pass | AGPL-3.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 9 repos | ~4.3k | Automated safety check: Pass | None | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| Kubeshark KFL2 Filter Referencekubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
Kubernetes Network Root Cause Analysis
kubeshark/kubeshark
Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.
Caveman Gateway Setup
JuliusBrussee/caveman
Routes every LLM call in a repository through the Caveman Cloud gateway in record mode, so requests and costs are measured without changing behavior.
More from overmind-core/overmind
All 20 skills in this repoAPI Endpoints
overmind-core/overmind
End-to-end workflow for adding or changing a backend API endpoint — which module the serializer and view belong in, URL registration, OpenAPI client regeneration, and typed consumption from the…
Finetuning Model Onboarding
overmind-core/overmind
Rules for adding a new model or model family to the finetuning pipeline, or changing finetuning behavior for an existing one — engine-agnostic customization via family hooks instead of if/else in…
Frontend Design
overmind-core/overmind
Overmind Console design system — semantic tokens, shared primitives, geometry and icons, the border-contrast floor, the duplicated table implementations, and the verification scripts.
MCP
overmind-core/overmind
End-to-end workflow for adding or changing Overmind MCP tools, resources, prompts, authentication, or result contracts — server layers, catalog registration, MCP-impact classification, and required…
PR Etiquette
overmind-core/overmind
How to open a complete pull request on overmind-core/overmind — the CI gates, the cross-cutting surfaces a change must carry with it (MCP, blast radius, the docs repo), gh pr edit being broken here…
Seed Demo Data
overmind-core/overmind
Run or modify the seeddemo management command (the one-project Support Copilot demo) without breaking the beat-safety invariants that keep celery workers from re-driving seeded rows.
Related
Categories
Questions about Overmind Integrations
What does Overmind Integrations do?
Connect external tracing providers to Overmind, inspect connector health, review capability-boundary mappings and verify imported traces. Overmind Integrations is an agent skill from overmind-core/overmind. Connect external tracing providers to Overmind, inspect connector health, review capability-boundary mappings and verify imported traces.
When should I use Overmind Integrations?
Overmind Integrations fits situations like: the Integrations surface; repository SDK instrumentation belongs to Observability.
How do I install Overmind Integrations in Claude Code?
Run `npx skills add overmind-core/overmind --skill overmind-integrations -a claude-code`. Or copy the skill folder (overmind/skills/overmind-integrations in overmind-core/overmind) into .claude/skills/overmind-integrations in your project. Claude Code loads it when a task matches its description.
How do I install Overmind Integrations in Codex?
Run `npx skills add overmind-core/overmind --skill overmind-integrations -a codex`. Or copy the skill folder (overmind/skills/overmind-integrations in overmind-core/overmind) into .agents/skills/overmind-integrations in your project. Codex loads it when a task matches its description.
Can I use Overmind Integrations 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 overmind-core/overmind --skill overmind-integrations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/overmind-integrations, .gemini/skills/overmind-integrations, .github/skills/overmind-integrations and .opencode/skills/overmind-integrations in your project.
What does Overmind Integrations need to run?
SKILL.md names no scripts, command-line tools or credentials: Overmind Integrations is instructions for the agent only.
Does Overmind Integrations access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Overmind Integrations safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Overmind Integrations use?
Overmind Integrations is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Overmind Integrations use?
About 772 tokens (SKILL.md is roughly 3.1k 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 Overmind Integrations?
Skills that share tags, products or a category with Overmind Integrations: Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars), Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars) and KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Overmind Integrations?
overmind-core (a GitHub organization) maintains it in overmind-core/overmind, which has 597 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.
Source: overmind-core/overmind on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.