AgentSkillsHub Skill Finder
zhuyansen/agent-skills-hub
Searches a locally cached, security-graded catalog of agent skills and MCP servers, and returns install commands after checking each one's grade.
Set up the local dev environment, seed data, and API keys to test the staff-only managed migrations MCP tools (managed-migrations-support-list, managed-migrations-support-get) end to end.
Install Testing MCP Tools Locally
$ npx skills add PostHog/posthog --skill testing-mcp-tools-locally -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog testing-mcp-tools-locally --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/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/testing-mcp-tools-locally .claude/skills/testing-mcp-tools-locally && 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 "testing-mcp-tools-locally" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/testing-mcp-tools-locally into .claude/skills/testing-mcp-tools-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-mcp-tools-locally", 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/PostHog/posthog/tree/master/.agents/skills/testing-mcp-tools-locallyType 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 PostHog/posthog --skill testing-mcp-tools-locally -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog testing-mcp-tools-locally --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/testing-mcp-tools-locally .agents/skills/testing-mcp-tools-locally && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "testing-mcp-tools-locally" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/testing-mcp-tools-locally into .agents/skills/testing-mcp-tools-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-mcp-tools-locally", 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 PostHog/posthog --skill testing-mcp-tools-locally -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog testing-mcp-tools-locally --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/testing-mcp-tools-locally .cursor/skills/testing-mcp-tools-locally && 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 "testing-mcp-tools-locally" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/testing-mcp-tools-locally into .cursor/skills/testing-mcp-tools-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-mcp-tools-locally", 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/PostHog/posthog.git --path .agents/skills/testing-mcp-tools-locally--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 PostHog/posthog --skill testing-mcp-tools-locally -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog testing-mcp-tools-locally --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/testing-mcp-tools-locally .gemini/skills/testing-mcp-tools-locally && 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 "testing-mcp-tools-locally" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/testing-mcp-tools-locally into .gemini/skills/testing-mcp-tools-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-mcp-tools-locally", 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 PostHog/posthog testing-mcp-tools-locallyInstalls 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 PostHog/posthog --skill testing-mcp-tools-locally -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/testing-mcp-tools-locally .github/skills/testing-mcp-tools-locally && 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 "testing-mcp-tools-locally" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/testing-mcp-tools-locally into .github/skills/testing-mcp-tools-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-mcp-tools-locally", 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 PostHog/posthog --skill testing-mcp-tools-locally -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog testing-mcp-tools-locally --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/testing-mcp-tools-locally .opencode/skills/testing-mcp-tools-locally && 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 "testing-mcp-tools-locally" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/testing-mcp-tools-locally into .opencode/skills/testing-mcp-tools-locally/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-mcp-tools-locally", 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
testing-mcp-tools-locally- GitHub stars
- 40k
- Token cost
- ~2.3k tokens
- SKILL.md length
- 793 words
- Files
- 2 (incl. references)
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Set up the local dev environment, seed data, and API keys to test the staff-only managed migrations MCP tools (managed-migrations-support-list, managed-migrations-support-get) end to end.
- Works in 7 steps: Start the dev environment → Run Postgres migrations → Verify DB connectivity from the Django… → …
- Testing batch import support tooling
- SKILL.md covers Prerequisites, 1. Start the dev environment, 2. Run Postgres migrations and 3. Verify DB connectivity from…, plus 5 more sections
- Calls pnpm, curl and jq
What it does
Testing MCP Tools Locally is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Set up the local dev environment, seed data, and API keys to test the staff-only managed migrations MCP tools (managed-migrations-support-list, managed-migrations-support-get) end to end. Use when testing batch import support tooling, debugging MCP tool responses or discovery (tools not appearing), or verifying the support API before deploying. Covers the discovery gate: hidden scope, isstaff, user:read, and why wildcard keys and OAuth never work.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/seed-data.md`).
It sits in Agent Workflows, covering MCP servers and Test data and fixtures. It works with PostgreSQL. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…
When your agent uses it
- Testing batch import support tooling
- Debugging MCP tool responses
- Discovery (tools not appearing)
- Verifying the support API before deploying
Example prompts
- “/testing-mcp-tools-locally”
Requirements
- Python 3
- Node.js
- Docker
Workflow steps
7 steps, taken from the step headings in SKILL.md.
- Start the dev environment
- Run Postgres migrations
- Verify DB connectivity from the Django shell
- Seed batch import test data
- Make your user staff and mint test keys
- Test the API directly
- Test via MCP
What it can do on your machine
Read from SKILL.md and the folder at commit 812e5c6. 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
Shell commands in SKILL.md call:
pnpmcurljqnpxdocker
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, curl, npx and docker, 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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Testing MCP Tools Locally loads about 2.3k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 120 tokens; SKILL.md has 793 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 793 words (~2,312 tokens).
“The dev environment must be running with Docker services healthy. The batch import support API and MCP tools require:”
- name
- testing-mcp-tools-locally
Files
SKILL.md and 1 other file (references) in .agents/skills/testing-mcp-tools-locally of PostHog/posthog.
- SKILL.md
- references/seed-data.md
Open the folder on GitHubat commit 812e5c6
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Testing MCP Tools Locally 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 |
|---|---|---|---|---|---|---|
| Testing MCP Tools Locally this skillPostHog/posthog | 40k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| AgentSkillsHub Skill Finderzhuyansen/agent-skills-hub | 410 | — | ~1k | Automated safety check: Pass | MIT | |
| Ogham Researchogham-mcp/ogham-mcp | 115 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Lunoraanolilab/lunora | 282 | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Use Gfs MCPGuepard-Corp/gfs | 158 | — | ~4k | Automated safety check: Pass | MIT | |
| Ogham Maintainogham-mcp/ogham-mcp | 115 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Ogham Research
ogham-mcp/ogham-mcp
Structured memory capture for Ogham shared memory. An agent skill from ogham-mcp/ogham-mcp.
Lunora
anolilab/lunora
Routes general Lunora requests to the right Lunora skill and gives the shared mental model (codegen loop, generated api/internal references, review commands, add-on capabilities, the @lunora/mcp…
Use Gfs MCP
Guepard-Corp/gfs
GFS MCP Server for AI agent integration. An agent skill from Guepard-Corp/gfs.
Ogham Maintain
ogham-mcp/ogham-mcp
Admin and maintenance workflows for Ogham shared memory. An agent skill from ogham-mcp/ogham-mcp.
Session Ingest
dnotitia/akb
Ingest a coding session JSONL into AKB as structured notes — session report + parallel-drafted TIL / task / idea / decision sub-notes.
More from PostHog/posthog
All 252 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Works with
Questions about Testing MCP Tools Locally
What does Testing MCP Tools Locally do?
Set up the local dev environment, seed data, and API keys to test the staff-only managed migrations MCP tools (managed-migrations-support-list, managed-migrations-support-get) end to end. Testing MCP Tools Locally is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Set up the local dev environment, seed data, and API keys to test the staff-only managed migrations MCP tools (managed-migrations-support-list, managed-migrations-support-get) end to end.
When should I use Testing MCP Tools Locally?
Testing MCP Tools Locally fits situations like: testing batch import support tooling; debugging MCP tool responses; discovery (tools not appearing); verifying the support API before deploying.
How do I install Testing MCP Tools Locally in Claude Code?
Run `npx skills add PostHog/posthog --skill testing-mcp-tools-locally -a claude-code`. Or copy the skill folder (.agents/skills/testing-mcp-tools-locally in PostHog/posthog) into .claude/skills/testing-mcp-tools-locally in your project. Claude Code loads it when a task matches its description.
How do I install Testing MCP Tools Locally in Codex?
Run `npx skills add PostHog/posthog --skill testing-mcp-tools-locally -a codex`. Or copy the skill folder (.agents/skills/testing-mcp-tools-locally in PostHog/posthog) into .agents/skills/testing-mcp-tools-locally in your project. Codex loads it when a task matches its description.
Can I use Testing MCP Tools Locally 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 PostHog/posthog --skill testing-mcp-tools-locally -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-mcp-tools-locally, .gemini/skills/testing-mcp-tools-locally, .github/skills/testing-mcp-tools-locally and .opencode/skills/testing-mcp-tools-locally in your project.
What does Testing MCP Tools Locally need to run?
Going by SKILL.md and its folder, Testing MCP Tools Locally needs the command-line tools its instructions call (pnpm, curl, jq, npx and docker). Our summary lists: Python 3; Node.js; Docker.
Does Testing MCP Tools Locally access the network?
SKILL.md contains no URLs. Its commands use curl, npx and docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Testing MCP Tools Locally 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 Testing MCP Tools Locally use?
Testing MCP Tools Locally has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Testing MCP Tools Locally use?
About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Testing MCP Tools Locally?
Skills that share tags, products or a category with Testing MCP Tools Locally: AgentSkillsHub Skill Finder (zhuyansen/agent-skills-hub, 410 stars), Ogham Research (ogham-mcp/ogham-mcp, 115 stars), Lunora (anolilab/lunora, 282 stars) and Use Gfs MCP (Guepard-Corp/gfs, 158 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Testing MCP Tools Locally?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,200 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 2026.
Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.