Spikard
Goldziher/spikard
Scaffold Spikard projects and generate code from OpenAPI, AsyncAPI, OpenRPC, GraphQL, and Protobuf schemas using the Spikard CLI or its MCP server.
Load this skill before using the execute tool. An agent skill from jeremyosih/pi-executor.
$ npx skills add jeremyosih/pi-executor --skill executor-usage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremyosih/pi-executor executor-usage --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/jeremyosih/pi-executor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/executor-usage .claude/skills/executor-usage && 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 "executor-usage" agent skill from https://github.com/jeremyosih/pi-executor/tree/main/skills/executor-usage into .claude/skills/executor-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executor-usage", 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/jeremyosih/pi-executor/tree/main/skills/executor-usageType 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 jeremyosih/pi-executor --skill executor-usage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremyosih/pi-executor executor-usage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremyosih/pi-executor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/executor-usage .agents/skills/executor-usage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "executor-usage" agent skill from https://github.com/jeremyosih/pi-executor/tree/main/skills/executor-usage into .agents/skills/executor-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executor-usage", 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 jeremyosih/pi-executor --skill executor-usage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremyosih/pi-executor executor-usage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremyosih/pi-executor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/executor-usage .cursor/skills/executor-usage && 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 "executor-usage" agent skill from https://github.com/jeremyosih/pi-executor/tree/main/skills/executor-usage into .cursor/skills/executor-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executor-usage", 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/jeremyosih/pi-executor.git --path skills/executor-usage--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 jeremyosih/pi-executor --skill executor-usage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremyosih/pi-executor executor-usage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremyosih/pi-executor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/executor-usage .gemini/skills/executor-usage && 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 "executor-usage" agent skill from https://github.com/jeremyosih/pi-executor/tree/main/skills/executor-usage into .gemini/skills/executor-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executor-usage", 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 jeremyosih/pi-executor executor-usageInstalls 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 jeremyosih/pi-executor --skill executor-usage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremyosih/pi-executor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/executor-usage .github/skills/executor-usage && 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 "executor-usage" agent skill from https://github.com/jeremyosih/pi-executor/tree/main/skills/executor-usage into .github/skills/executor-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executor-usage", 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 jeremyosih/pi-executor --skill executor-usage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremyosih/pi-executor executor-usage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremyosih/pi-executor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/executor-usage .opencode/skills/executor-usage && 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 "executor-usage" agent skill from https://github.com/jeremyosih/pi-executor/tree/main/skills/executor-usage into .opencode/skills/executor-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executor-usage", 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.
executor-usageLoad this skill before using the execute tool. An agent skill from jeremyosih/pi-executor.
Executor Usage is an agent skill from jeremyosih/pi-executor. Load this skill before using the execute tool. It teaches the Executor sandbox calling model: discover tools with tools.search({ query, limit }), inspect them with tools.describe.tool({ path }), inspect configured sources with tools.executor.sources.list({}), then call the real tool as tools.<namespace.<tool(args). Use when working with third-party services, SaaS APIs, MCP/OpenAPI/GraphQL tools, auth-managed actions, or remote data that should go through Executor instead of direct shell scripts or ad hoc HTTP code.
Its SKILL.md is about 1.4k 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 Backend & APIs, covering Shell scripting, OpenAPI specifications and GraphQL. It works with Model Context Protocol, OpenAPI and GraphQL. The repository describes itself as: Pi extension for executor. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit b744f0c. 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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
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.
Executor Usage loads about 1.4k tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 553 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 jeremyosih/pi-executor at commit b744f0c, republished under its MIT licence (© jeremyosih). 553 words, ~1,443 tokens.
.claude/skills/executor-usage/SKILL.md (or your agent's skills folder).Use this skill before any execute call.
This skill exists to prevent trial-and-error inside the Executor sandbox.
The runtime is a lazy proxy over Executor tools, not a normal JS object, so naive probing (Object.keys, globalThis, random namespace guesses, tools()) is misleading.
Before calling execute, read the execute tool definition in the current prompt/context.
That definition is the session-specific source of truth.
This skill summarizes the current Executor calling model exposed by the execute tool definition in your session.
Avoid baking in repository-specific file paths or local implementation details.
Inside execute:
tools object is a lazy proxy.tools.mcp_linear_app.list_issues({...})tools.linear(...)tools()tools.search({ query, namespace?, limit? })tools.describe.tool({ path })tools.executor.sources.list({ query?, limit? })Follow this order inside every execute snippet unless you already know the exact tool path with high confidence.
const matches = await tools.search({ query: "linear issues", limit: 5 });
const path = matches[0]?.path;
if (!path) return "No matching tools found.";
const details = await tools.describe.tool({ path });
console.log(details.inputTypeScript);
console.log(details.outputTypeScript);
const result = await tools.mcp_linear_app.list_issues({
project: "<project-id>",
limit: 5,
});
return result;Many MCP-backed tools return an MCP payload like:
{
content: [{ type: "text", text: "{...json...}" }],
structuredContent?: {...}
}Prefer structuredContent when present. Otherwise, parse the first text block if it looks like JSON.
const unwrap = (value: any) => {
if (value?.structuredContent) return value.structuredContent;
const text = value?.content?.find?.((item: any) => item?.type === "text")?.text;
if (typeof text !== "string") return value;
try {
return JSON.parse(text);
} catch {
return value;
}
};Use it like:
const raw = await tools.mcp_linear_app.list_projects({ query: "gitinspect", limit: 10 });
return unwrap(raw);tools.search({ ... }) for unknown integrations.tools.describe.tool({ path }) before invoking unfamiliar tools.tools.executor.sources.list({}) when you need source inventory or namespace confirmation.execute handle inline elicitation in Pi UI sessions.tools().Object.keys(tools) or rely on globalThis for discovery.tools.linear or tools.mcp.tools.search; pass an object.includeSchemas with tools.describe.tool(); that parameter is no longer accepted.fetch when Executor already has the integration you need.Use short intent phrases with key nouns:
linear issuesgithub pull requestscalendar eventslack channel messagesWhen you know the namespace, narrow it:
await tools.search({ namespace: "mcp_linear_app", query: "issues", limit: 10 });Use Executor when the task is mostly outside the repo:
Use Pi's native file tools when the task is mostly inside the repo:
In Pi UI sessions, let execute handle Executor interaction inline.
Do not call resume unless execute explicitly cannot finish inline and gives you an execution ID to resume.
If an execute snippet behaves strangely, check these first:
execute?tools.search({ ... }) instead of guessing?tools.describe.tool({ path }) before calling an unfamiliar tool?structuredContent / JSON text if the result looked nested?© jeremyosih, MIT. 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 skills/executor-usage of jeremyosih/pi-executor.
Open the folder on GitHubat commit b744f0c
Executor Usage 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 |
|---|---|---|---|---|---|---|
| Executor Usage this skilljeremyosih/pi-executor | 104 | — | ~1.4k | Automated safety check: Pass | MIT | |
| SpikardGoldziher/spikard | 123 | — | ~799 | Automated safety check: Pass | MIT | |
| Uxcholon-run/uxc | 115 | — | ~1.8k | Automated safety check: Pass | MIT | |
| API DesignerJeffallan/claude-skills | 12k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| AurlShawnPana/aurl | 167 | — | ~536 | Automated safety check: Pass | MIT | |
| Distilled SDKalchemy-run/distilled | 431 | — | ~6k | Automated safety check: Pass | Apache-2.0 |
Goldziher/spikard
Scaffold Spikard projects and generate code from OpenAPI, AsyncAPI, OpenRPC, GraphQL, and Protobuf schemas using the Spikard CLI or its MCP server.
holon-run/uxc
Discover and call remote schema-exposed interfaces with UXC.
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
ShawnPana/aurl
Turn any API into a CLI command. An agent skill from ShawnPana/aurl.
alchemy-run/distilled
Build or update a distilled SDK for an API provider — sourcing its OpenAPI/Smithy/GraphQL/discovery description, adding the spec mirror that feeds it, generating packages/<provider, listing it on…
yonatangross/orchestkit
API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs.
Works with
Categories
Load this skill before using the execute tool. An agent skill from jeremyosih/pi-executor. Executor Usage is an agent skill from jeremyosih/pi-executor. Load this skill before using the execute tool.
Executor Usage fits situations like: working with third-party services; MCP/OpenAPI/GraphQL tools; auth-managed actions; remote data that should go through Executor instead of direct shell scripts.
Run `npx skills add jeremyosih/pi-executor --skill executor-usage -a claude-code`. Or copy the skill folder (skills/executor-usage in jeremyosih/pi-executor) into .claude/skills/executor-usage in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremyosih/pi-executor --skill executor-usage -a codex`. Or copy the skill folder (skills/executor-usage in jeremyosih/pi-executor) into .agents/skills/executor-usage 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 jeremyosih/pi-executor --skill executor-usage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/executor-usage, .gemini/skills/executor-usage, .github/skills/executor-usage and .opencode/skills/executor-usage in your project.
SKILL.md names no scripts, command-line tools or credentials: Executor Usage is instructions for the agent only.
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.
Executor Usage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k 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 Executor Usage: Spikard (Goldziher/spikard, 123 stars), Uxc (holon-run/uxc, 115 stars), API Designer (Jeffallan/claude-skills, 12k stars) and Aurl (ShawnPana/aurl, 167 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jeremyosih (a GitHub user) maintains it in jeremyosih/pi-executor, which has 104 GitHub stars. The repository was last updated on June 21, 2026.
Source: jeremyosih/pi-executor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.