Memtrace Decision Memory
syncable-dev/memtrace-public
Use Cortex decision memory through the normal Memtrace MCP tools.
Start here for all API mocking in tests. An agent skill from stacklok/toolhive-studio.
$ npx skills add stacklok/toolhive-studio --skill testing-with-api-mocks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stacklok/toolhive-studio testing-with-api-mocks --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/stacklok/toolhive-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/testing-with-api-mocks .claude/skills/testing-with-api-mocks && 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-with-api-mocks" agent skill from https://github.com/stacklok/toolhive-studio/tree/main/.codex/skills/testing-with-api-mocks into .claude/skills/testing-with-api-mocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-api-mocks", 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/stacklok/toolhive-studio/tree/main/.codex/skills/testing-with-api-mocksType 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 stacklok/toolhive-studio --skill testing-with-api-mocks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stacklok/toolhive-studio testing-with-api-mocks --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stacklok/toolhive-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/testing-with-api-mocks .agents/skills/testing-with-api-mocks && 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-with-api-mocks" agent skill from https://github.com/stacklok/toolhive-studio/tree/main/.codex/skills/testing-with-api-mocks into .agents/skills/testing-with-api-mocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-api-mocks", 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 stacklok/toolhive-studio --skill testing-with-api-mocks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stacklok/toolhive-studio testing-with-api-mocks --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stacklok/toolhive-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/testing-with-api-mocks .cursor/skills/testing-with-api-mocks && 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-with-api-mocks" agent skill from https://github.com/stacklok/toolhive-studio/tree/main/.codex/skills/testing-with-api-mocks into .cursor/skills/testing-with-api-mocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-api-mocks", 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/stacklok/toolhive-studio.git --path .codex/skills/testing-with-api-mocks--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 stacklok/toolhive-studio --skill testing-with-api-mocks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stacklok/toolhive-studio testing-with-api-mocks --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stacklok/toolhive-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/testing-with-api-mocks .gemini/skills/testing-with-api-mocks && 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-with-api-mocks" agent skill from https://github.com/stacklok/toolhive-studio/tree/main/.codex/skills/testing-with-api-mocks into .gemini/skills/testing-with-api-mocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-api-mocks", 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 stacklok/toolhive-studio testing-with-api-mocksInstalls 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 stacklok/toolhive-studio --skill testing-with-api-mocks -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stacklok/toolhive-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/testing-with-api-mocks .github/skills/testing-with-api-mocks && 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-with-api-mocks" agent skill from https://github.com/stacklok/toolhive-studio/tree/main/.codex/skills/testing-with-api-mocks into .github/skills/testing-with-api-mocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-api-mocks", 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 stacklok/toolhive-studio --skill testing-with-api-mocks -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install stacklok/toolhive-studio testing-with-api-mocks --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stacklok/toolhive-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/testing-with-api-mocks .opencode/skills/testing-with-api-mocks && 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-with-api-mocks" agent skill from https://github.com/stacklok/toolhive-studio/tree/main/.codex/skills/testing-with-api-mocks into .opencode/skills/testing-with-api-mocks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-with-api-mocks", 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.
testing-with-api-mocksStart here for all API mocking in tests. An agent skill from stacklok/toolhive-studio.
Testing With API Mocks is an agent skill from stacklok/toolhive-studio. Start here for all API mocking in tests. Covers auto-generation, fixtures, and when to use other skills. Required reading before creating, refactoring, or modifying any test involving API calls.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering MCP servers and Refactoring. It works with Model Context Protocol. The repository describes itself as: ToolHive is an application that allows you to install, manage and run MCP servers and connect them to AI agents. The licence is Apache-2.0.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit fc76b24. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
pnpmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Testing With API Mocks loads about 1.5k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 343 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.
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.
The full file from stacklok/toolhive-studio at commit fc76b24, republished under its Apache-2.0 licence (© stacklok). 343 words, ~1,459 tokens.
.claude/skills/testing-with-api-mocks/SKILL.md (or your agent's skills folder).This is the starting point for all API mocking in tests. Read this skill first before working on any test that involves API calls.
This project uses MSW (Mock Service Worker) with auto-generated schema-based mocks. When writing tests for code that calls API endpoints, mocks are created automatically.
renderer/src/common/mocks/fixtures/<endpoint>/<method>.tsNo manual mock setup is required for basic tests.
Fixtures are organized by endpoint path and HTTP method:
renderer/src/common/mocks/fixtures/
├── groups/
│ ├── get.ts # GET /api/v1beta/groups
│ └── post.ts # POST /api/v1beta/groups
├── workloads/
│ └── get.ts # GET /api/v1beta/workloads
├── workloads_name/
│ └── get.ts # GET /api/v1beta/workloads/:name
└── ...Path parameters like :name become _name in the directory name.
Generated fixtures use the AutoAPIMock wrapper with types from the OpenAPI schema:
// renderer/src/common/mocks/fixtures/groups/get.ts
import type {
GetApiV1BetaGroupsResponse,
GetApiV1BetaGroupsData,
} from '@common/api/generated/types.gen'
import { AutoAPIMock } from '@mocks'
export const mockedGetApiV1BetaGroups = AutoAPIMock<
GetApiV1BetaGroupsResponse,
GetApiV1BetaGroupsData
>({
groups: [
{ name: 'default', registered_clients: ['client-a'] },
{ name: 'research', registered_clients: ['client-b'] },
],
})The second type parameter (*Data) provides typed access to request parameters (query, path, body) for conditional overrides.
Export names follow the pattern: mocked + HTTP method + endpoint path in PascalCase.
GET /api/v1beta/groups → mockedGetApiV1BetaGroupsPOST /api/v1beta/workloads → mockedPostApiV1BetaWorkloadsGET /api/v1beta/workloads/:name → mockedGetApiV1BetaWorkloadsByNameFor most tests, just render the component and the mock handles the rest:
import { render, screen, waitFor } from '@testing-library/react'
it('displays groups from the API', async () => {
render(<GroupsList />)
await waitFor(() => {
expect(screen.getByText('default')).toBeVisible()
})
})The auto-generated mock provides realistic fake data based on the OpenAPI schema.
If the auto-generated data doesn't suit your test, edit the fixture file directly:
// renderer/src/common/mocks/fixtures/groups/get.ts
export const mockedGetApiV1BetaGroups = AutoAPIMock<
GetApiV1BetaGroupsResponse,
GetApiV1BetaGroupsData
>({
groups: [
{ name: 'production', registered_clients: ['claude-code'] }, // Custom data
{ name: 'staging', registered_clients: [] },
],
})This becomes the new default for all tests using this endpoint.
To regenerate a fixture with fresh schema-based data:
rm renderer/src/common/mocks/fixtures/groups/get.ts
pnpm test -- --run <test-file>// Types for API responses and request parameters
import type {
GetApiV1BetaGroupsResponse,
GetApiV1BetaGroupsData,
} from '@common/api/generated/types.gen'
// AutoAPIMock wrapper
import { AutoAPIMock } from '@mocks'
// Fixture mocks (for test-scoped overrides, see: testing-api-overrides skill)
import { mockedGetApiV1BetaGroups } from '@mocks/fixtures/groups/get'For endpoints that return 204, create a minimal AutoAPIMock fixture and override the handler in each test:
// renderer/src/common/mocks/fixtures/health/get.ts
import type {
GetHealthResponse,
GetHealthData,
} from '@common/api/generated/types.gen'
import { AutoAPIMock } from '@mocks'
export const mockedGetHealth = AutoAPIMock<GetHealthResponse, GetHealthData>(
'' as unknown as GetHealthResponse
)Then in tests, use .overrideHandler() to return the appropriate response:
import { mockedGetHealth } from '@mocks/fixtures/health/get'
import { HttpResponse } from 'msw'
it('navigates on health check success', async () => {
mockedGetHealth.overrideHandler(() => new HttpResponse(null, { status: 204 }))
// ...
})
it('handles health check failure', async () => {
mockedGetHealth.overrideHandler(() => HttpResponse.error())
// ...
})Custom mocks are only needed for text/plain endpoints. The only current example is the logs endpoint:
// renderer/src/common/mocks/customHandlers/index.ts
export const customHandlers = [
http.get(mswEndpoint('/api/v1beta/workloads/:name/logs'), ({ params }) => {
const { name } = params
const logs = getMockLogs(name as string)
return new HttpResponse(logs, { status: 200 })
}),
]To override the logs response in tests, use the exported getMockLogs mock:
import { getMockLogs } from '@/common/mocks/customHandlers'
getMockLogs.mockReturnValueOnce('Custom log content for this test')© stacklok, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .codex/skills/testing-with-api-mocks of stacklok/toolhive-studio.
Open the folder on GitHubat commit fc76b24
Testing With API Mocks 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 With API Mocks this skillstacklok/toolhive-studio | 170 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Memtrace Decision Memorysyncable-dev/memtrace-public | 487 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Edt MCP Project Local FixDitriXNew/EDT-MCP | 295 | — | ~507 | Automated safety check: Pass | AGPL-3.0 | |
| Harness Engineering LifecycleArenukvern/mcp_flutter | 386 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Roslynkmrpmorris/Roslynk | 125 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Idea MCPdtprj/dongting | 208 | — | ~698 | Automated safety check: Pass | Apache-2.0 |
syncable-dev/memtrace-public
Use Cortex decision memory through the normal Memtrace MCP tools.
DitriXNew/EDT-MCP
Apply one bounded BSL correction through EDT-MCP with lost-update protection, targeted validation, and minimal diff.
Arenukvern/mcp_flutter
Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists.
mrpmorris/Roslynk
How to use the Roslynk MCP tools (mcproslynk) effectively for .NET work.
dtprj/dongting
IntelliJ IDEA MCP for Java code analysis, testing, refactoring, and project navigation.
adeze/raindrop-mcp
Refactoring MCP Tools for Better LLM Integration and Usability
stacklok/toolhive-studio
Deep links in ToolHive Studio. An agent skill from stacklok/toolhive-studio.
stacklok/toolhive-studio
Reproduce and fix bugs using TDD. An agent skill from stacklok/toolhive-studio.
stacklok/toolhive-studio
Spin up and interact with ToolHive Studio's containerized dev environment (Xvfb + noVNC + DinD).
stacklok/toolhive-studio
Remediate security vulnerabilities found by Grype or pnpm audit.
stacklok/toolhive-studio
Create new AI agent skills for Claude Code, Codex, and Cursor.
stacklok/toolhive-studio
Verify API requests in tests. An agent skill from stacklok/toolhive-studio.
Works with
Categories
Start here for all API mocking in tests. An agent skill from stacklok/toolhive-studio. Testing With API Mocks is an agent skill from stacklok/toolhive-studio. Start here for all API mocking in tests.
Testing With API Mocks fits situations like: tasks that involve MCP servers; tasks that involve Refactoring.
Run `npx skills add stacklok/toolhive-studio --skill testing-with-api-mocks -a claude-code`. Or copy the skill folder (.codex/skills/testing-with-api-mocks in stacklok/toolhive-studio) into .claude/skills/testing-with-api-mocks in your project. Claude Code loads it when a task matches its description.
Run `npx skills add stacklok/toolhive-studio --skill testing-with-api-mocks -a codex`. Or copy the skill folder (.codex/skills/testing-with-api-mocks in stacklok/toolhive-studio) into .agents/skills/testing-with-api-mocks in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add stacklok/toolhive-studio --skill testing-with-api-mocks -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-with-api-mocks, .gemini/skills/testing-with-api-mocks, .github/skills/testing-with-api-mocks and .opencode/skills/testing-with-api-mocks in your project.
Going by SKILL.md and its folder, Testing With API Mocks needs the command-line tools its instructions call (pnpm).
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.
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.
Testing With API Mocks is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Testing With API Mocks: Memtrace Decision Memory (syncable-dev/memtrace-public, 487 stars), Edt MCP Project Local Fix (DitriXNew/EDT-MCP, 295 stars), Harness Engineering Lifecycle (Arenukvern/mcp_flutter, 386 stars) and Roslynk (mrpmorris/Roslynk, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
stacklok (a GitHub organization) maintains it in stacklok/toolhive-studio, which has 170 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.
Source: stacklok/toolhive-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.