Skip to content

Latest commit

 

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 

Repository files navigation

Codex Skills

Personal Codex skills and plugins for reusable agent workflows.

This repository is a public, repo-scoped Codex plugin marketplace. It collects installable Codex plugins and their bundled skills in one place, so the same agent workflows can be reused across local projects.

Catalog

Type Name Path Description
Plugin build-android-apps plugins/build-android-apps/ Android app development plugin for device mirroring, automation, previews, and debugging.

Install

First-time install from GitHub

Add this repository as a Codex plugin marketplace, then install the Android plugin from that marketplace:

codex plugin marketplace add peterchoee/codex-skills
codex plugin add build-android-apps@codex-skills

Open a new Codex session after installing so Codex loads the bundled skill.

Update an existing install

If you already installed build-android-apps@codex-skills, refresh the GitHub marketplace snapshot and reinstall the plugin so Codex uses the newest cached version:

codex plugin marketplace upgrade codex-skills
codex plugin remove build-android-apps@codex-skills
codex plugin add build-android-apps@codex-skills

Open a new Codex session after reinstalling. Existing sessions can keep the previous plugin skill list in memory.

Verify installation

Check that the plugin is installed, enabled, and using the expected version:

codex plugin list | rg -C 2 'build-android-apps@codex-skills'

The status should show installed, enabled. For this repository revision, build-android-apps should install as version 0.1.1 or newer.

You can also verify that a fresh Codex session sees the bundled skill:

codex -C /path/to/your/android/project debug prompt-input 'Reply OK' \
  | rg 'build-android-apps:android-emulator-browser'

Use the installed skill

In the Codex app, type / and choose Android Emulator Browser from the slash command list. Codex includes enabled skills in that list.

You can also invoke the skill directly in the composer:

$android-emulator-browser

In debug output or generated skill lists, plugin-installed skills may appear with their plugin namespace:

build-android-apps:android-emulator-browser

Local development install

For local development from a checked-out copy, add the local repository as the marketplace root instead:

codex plugin marketplace add /absolute/path/to/codex-skills
codex plugin add build-android-apps@codex-skills

For local development, reinstall after plugin changes and then open a new Codex session. If the local marketplace was already added, run codex plugin add build-android-apps@codex-skills again after changing the plugin.

Repository Layout

.
|-- .agents/
|   `-- plugins/
|       `-- marketplace.json
|-- plugins/
|   `-- build-android-apps/
|       |-- README.md
|       |-- .codex-plugin/
|       |   `-- plugin.json
|       `-- skills/
|           `-- android-emulator-browser/
|               |-- SKILL.md
|               |-- agents/
|               |-- references/
|               `-- scripts/
`-- README.md

Maintenance

Each plugin lives under plugins/<plugin-name>/ and includes a required .codex-plugin/plugin.json manifest. Bundled skills live under that plugin's skills/ directory, with one SKILL.md per skill. Skill UI metadata for the Codex app lives in skills/<skill-name>/agents/openai.yaml.

When adding a plugin:

  1. Create plugins/<plugin-name>/.codex-plugin/plugin.json.
  2. Add bundled skills under plugins/<plugin-name>/skills/<skill-name>/.
  3. Add agents/openai.yaml inside each skill that should have a friendly Codex app slash-list label and default prompt.
  4. Add or update the plugin entry in .agents/plugins/marketplace.json.
  5. Add plugins/<plugin-name>/README.md for plugin-specific documentation.
  6. Restart Codex and verify the plugin appears in the Codex Skills marketplace.

When adding a skill to an existing plugin:

  1. Create plugins/<plugin-name>/skills/<skill-name>/SKILL.md.
  2. Keep the frontmatter name and description clear enough for Codex to decide when to load it.
  3. Put long workflow details in the skill folder and keep executable helpers in scripts/ when they make the skill easier to maintain.

About

Codex skills, plugins, and workflow tools

Resources

Stars

0 stars

Watchers

0 watching

Forks

Contributors

Languages