IonBin
All pages
Search

Package your best prompts as reusable agent skills

SOPs · BuildChecked 2026-10-18

Stop re-pasting long instructions; let agents load the right playbook automatically.

  1. 01You
  2. 02Claude
  3. 03Codex
  4. 04You
  5. 05You
Recipe context

Agent Skills are folders with instructions and resources that Claude and Codex load when relevant. Turn a process you repeat into a skill, test it, and share it with your team.

Independent review. Unpaid; no partnership with the tools on this page. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.

Editorial shortlist

Compare your options.

For maintaining reusable agent instructions and tests.

Verify the target harness; skill files are not automatically portable. Choose one for implementing and reviewing code changes; switching may need setup changes.

Used by Ion · separate from rank.

Unpaid picks. No partnership with OpenAI Codex, Cursor, Google Antigravity.

  1. 1 · Primary / high

    OpenAI Codex

    Used by Ion — Used by Ion for its own work. This is separate from recommendation rank and is not a claim that every feature was tested.

    Why it fits: A coding workspace supports edits, tests and reviewable repository changes.

    Tradeoff: A development environment and capable reviewer remain necessary.

    Choose it when the result should be a small patch with test evidence.

    Evidence for OpenAI Codex

    The linked IonBin review records capabilities, access limits and source links. Review date: 2026-10-18. Primary product reference ↗

  2. 2 · Secondary / medium

    Cursor

    Why it fits: An AI code editor keeps implementation close to interactive developer review.

    Tradeoff: The team must work with code; model availability depends on the plan.

    Prefer it when a developer wants to steer changes while navigating the editor.

    Evidence for Cursor

    The linked IonBin review records capabilities, access limits and source links. Review date: 2026-10-21. Primary product reference ↗

  3. 3 · Third / lower

    Google Antigravity

    Why it fits: Development-agent surfaces offer another route for code and tool-assisted implementation.

    Tradeoff: Capabilities differ across desktop, CLI and other surfaces.

    Prefer it when the team already uses its environment and can validate the needed tools.

    Evidence for Google Antigravity

    The linked IonBin review records capabilities, access limits and source links. Review date: 2026-10-18. Primary product reference ↗

How this shortlist was chosen

Editorial judgment, not a personal-use endorsement or performance score. These are alternatives for the named role, not three required stack components. Vendors did not pay for, request or approve these positions.

Inspectable file changes come before editor convenience. A lower-ranked option may fit your constraints better; compare the conditions stated on each card before choosing.

Setup and portability: Use scoped repositories, tests and human review. Switching agents does not migrate settings, credentials or model access.

Reviewed 2026-10-21. This page applies a shared comparison for “implementing and reviewing code changes” to the stated task and constraints. It is documentation-based editorial guidance, not three new hands-on tests. We weigh value for the job, distinct capabilities, replacement limits, technical effort and interoperability. Check current plan terms before adopting or switching.

See our review method, MCP connections and portability and switching costs.

Steps

  1. You

    Pick a repeatable process and write the steps, examples and any scripts into a SKILL.md folder

    Human stepConfirmed
  2. Claude

    Loads the skill when relevant, from ~/.claude/skills or a project’s .claude/skills in Claude Code

    AI platformConfirmed
  3. Codex

    Loads skills in the same SKILL.md format from .agents/skills in the repository

    AI platformConfirmed
  4. You

    Version the skills library in GitHub and review changes through pull requests

    Human stepConfirmedGitHub
  5. You

    Review skill outputs and update the skill, not just the output

    Human stepConfirmed

Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.

Human approval

You review outputs and own the skill contents.

Watch out for

A skill that encodes a weak process scales the weakness. Test it on three real tasks before you share it, and keep the master copy in GitHub, not in a chat.

Starter prompt

Here is a process I repeat: [describe it]. Draft a SKILL.md folder for it: a short description of when to use it, the steps, two worked examples and any script it needs. Keep it tool-neutral where you can. I will review the skill, test it on a real task and commit it to our skills repository through a pull request.

Written for this workflow. Paste it into your AI platform and adjust it to your situation.

Tools in this workflow

ToolRoleOfficial site
ClaudeAI platform claude.ai ↗
OpenAI CodexAI platform developers.openai.com ↗
GitHubHuman step github.com ↗

Which AI platforms can run it

PlatformStatusWhy
Claude (incl. Claude Code) Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
OpenAI Codex Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
Google Antigravity Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
ChatGPT Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
Gemini Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
Perplexity Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
What the platform statuses mean

Confirmed: documented access meets the recorded requirements. Inferred: a reviewed note describes a plausible, untested pairing. To verify: a connection or step is unresolved. MCP and API pairings need route-specific evidence; a plugin, CLI or API alone does not prove compatible access, credentials or permissions. These are documentation assessments, not IonBin runtime tests.

What we checked (2026-10-18)

  • The format. A skill is a folder with a SKILL.md file that has at least a name and a description, plus optional scripts and reference files. Agent Skills is published as an open format at agentskills.io.
  • Claude. Custom skills work in Claude Code (~/.claude/skills/ for personal skills, .claude/skills/ for a project), in claude.ai settings and through the Claude API. Claude Code’s current guide documents one-way downloads of enabled claude.ai account skills for supported signed-in sessions. Local-only skills do not automatically reach Cowork or cloud routines, and API uploads remain separate. Check the surface and sign-in method rather than assuming all copies sync. It also says to use skills only from sources you trust, because a skill can contain code.
  • Codex. Codex reads skills from .agents/skills folders, from your working directory up to the repository root, as well as user and admin locations. It loads a skill’s full instructions only when it picks the skill. In Codex CLI and the IDE extension, you can call one with $ or /skills; ChatGPT uses @. Plugins are the documented distribution route for reusable skills across ChatGPT and Codex.
  • Portability. Both use SKILL.md, but the folder locations differ. Keep one authoritative source and deliberately install or distribute it to each supported surface. Test scripts, dependencies, permissions and vendor-specific fields in each client.

Set it up

  1. Choose a task you’ve explained more than three times.
  2. Write the steps, one good example and the common mistakes.
  3. Test it on a real task in each agent.
  4. Store the library in a GitHub repository, so changes get reviewed.

Verification limits and implementation checks

The page is documentation-reviewed; the complete workflow has not been run by IonBin.

  • Verify the skill on each target client; sharing SKILL.md does not guarantee identical tools or behavior.

Check a skill before you install it

Sentry’s Skill Scanner reviews a third-party skill for injection, risky scripts, broad permissions and outside links before you add it. It runs its own script and asks for Bash, so use it in a disposable environment, and still read any scripts yourself. IonBin reviewed it from source only.

Sources

Related workflows

No affiliate links on this page. No paid placements in workflows. How IonBin makes money.