use-cases/reusable-codex-skills.md Codex Docs, 2026-03-25 18:24 UTC → 2026-04-23 00:46 UTC

1# Save workflows as skills | Codex use cases

2 

3Codex use cases

4 

5![](/assets/OpenAI-black-wordmark.svg)

6 

7![Codex](/assets/OAI_Codex-Lockup_Fallback_Black.svg)

8 

9Codex use case

10 

11# Save workflows as skills

12 

13Create a skill Codex can keep on hand for work you repeat.

14 

15Difficulty **Easy**

16 

17Time horizon **5m**

18 

19Turn a working Codex thread, review rules, test commands, release checklists, design conventions, writing examples, or repo-specific scripts into a skill Codex can use in future threads.

20 

21## Best for

22 

23 - Codified workflows you want Codex to use again.

24- Teams that want a reusable skill instead of a long prompt pasted into every thread.

25 

26# Contents

27 

28[← All use cases](https://developers.openai.com/codex/use-cases)

29 

30Copy page [Export as PDF](https://developers.openai.com/codex/use-cases/reusable-codex-skills/?export=pdf)

31 

32Turn a working Codex thread, review rules, test commands, release checklists, design conventions, writing examples, or repo-specific scripts into a skill Codex can use in future threads.

33 

34Easy

35 

365m

37 

38Related links

39 

40[Agent skills](https://developers.openai.com/codex/skills)

41 

42## Best for

43 

44 - Codified workflows you want Codex to use again.

45- Teams that want a reusable skill instead of a long prompt pasted into every thread.

46 

47## Skills & Plugins

48 

49- [Skill Creator](https://github.com/openai/skills/tree/main/skills/.system/skill-creator)

50 

51 Gather information about the workflow, scaffold a skill, keep the main instructions short, and validate the result.

52 

53| Skill | Why use it |

54| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

55| [Skill Creator](https://github.com/openai/skills/tree/main/skills/.system/skill-creator) | Gather information about the workflow, scaffold a skill, keep the main instructions short, and validate the result. |

56 

57## Starter prompt

58 

59Use $skill-creator to create a Codex skill that [fixes failing Buildkite checks on a GitHub PR / turns PR notes into inline review comments / writes our release notes from merged PRs]

60 Use these sources when creating the skill:

61- Working example: [say "use this thread," link a merged PR, or paste a good Codex answer]

62- Source: [paste a Slack thread, PR review link, runbook URL, docs URL, or ticket]

63 - Repo: [repo path, if this skill depends on one repo]

64- Scripts or commands to reuse: [test command], [preview command], [log-fetch script], [release command]

65- Good output: [paste the Slack update, changelog entry, review comment, ticket, or final answer you want future threads to match]

66 

67[Open in the Codex app](codex://new?prompt=Use+%24skill-creator+to+create+a+Codex+skill+that+%5Bfixes+failing+Buildkite+checks+on+a+GitHub+PR+%2F+turns+PR+notes+into+inline+review+comments+%2F+writes+our+release+notes+from+merged+PRs%5D%0A%0AUse+these+sources+when+creating+the+skill%3A%0A-+Working+example%3A+%5Bsay+%22use+this+thread%2C%22+link+a+merged+PR%2C+or+paste+a+good+Codex+answer%5D%0A-+Source%3A+%5Bpaste+a+Slack+thread%2C+PR+review+link%2C+runbook+URL%2C+docs+URL%2C+or+ticket%5D%0A-+Repo%3A+%5Brepo+path%2C+if+this+skill+depends+on+one+repo%5D%0A-+Scripts+or+commands+to+reuse%3A+%5Btest+command%5D%2C+%5Bpreview+command%5D%2C+%5Blog-fetch+script%5D%2C+%5Brelease+command%5D%0A-+Good+output%3A+%5Bpaste+the+Slack+update%2C+changelog+entry%2C+review+comment%2C+ticket%2C+or+final+answer+you+want+future+threads+to+match%5D "Open in the Codex app")

68 

69Use $skill-creator to create a Codex skill that [fixes failing Buildkite checks on a GitHub PR / turns PR notes into inline review comments / writes our release notes from merged PRs]

70 Use these sources when creating the skill:

71- Working example: [say "use this thread," link a merged PR, or paste a good Codex answer]

72- Source: [paste a Slack thread, PR review link, runbook URL, docs URL, or ticket]

73 - Repo: [repo path, if this skill depends on one repo]

74- Scripts or commands to reuse: [test command], [preview command], [log-fetch script], [release command]

75- Good output: [paste the Slack update, changelog entry, review comment, ticket, or final answer you want future threads to match]

76 

77## Create a skill Codex can keep on hand

78 

79Use skills to give Codex reusable instructions, resources, and scripts for work you repeat. A [skill](https://developers.openai.com/codex/skills) can preserve the thread, doc, command, or example that made Codex useful the first time.

80 

81Start with one working example: a Codex thread that cherry-picked a PR, a release checklist from Notion, a set of useful PR comments, or a Slack thread explaining a launch process.

82 

83## How to use

84 

851. Add the context you want Codex to use.

86 

87 Stay in the Codex thread you want to preserve, paste the Slack thread or docs link, and add the rule, command, or example Codex should remember.

882. Run the starter prompt.

89 

90 The prompt names the skill you want, then gives `$skill-creator` the thread, doc, PR, command, or output to preserve.

913. Let Codex create and validate the skill.

92 

93 The result should define the `$skill-name`, describe when it should trigger, and keep reusable instructions in the right place.

94 

95 Skills in `~/.codex/skills` are available from any repo. Skills in the current repo can be committed so teammates can use them too.

964. Use the skill, then update it from the thread.

97 

98 Invoke the new `$skill-name` on the next PR, alert, review, release note, or design task. If it uses the wrong test command, misses a review rule, skips a runbook step, or writes a draft you would not send, ask Codex to add that correction to the skill.

99 

100## Provide source material

101 

102Give `$skill-creator` the material that explains how the skill should work.

103 

104| What you have | What to add |

105| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

106| **A workflow from a Codex thread that you want to preserve** | Stay in that thread and say `use this thread`. Codex can use the conversation, commands, edits, and feedback from that thread as the starting point. |

107| **Docs or a runbook** | Paste the release checklist, link the incident-response runbook, attach the API PDF, or point Codex at the markdown guide in your repo. |

108| **Team conversation** | Paste the Slack thread where someone explained an alert, link the PR review with frontend rules, or attach the support conversation that explains the customer problem. |

109| **Scripts or commands the skill should reuse** | Add the test command, preview command, release script, log-fetch script, or local helper command you want future Codex threads to run. |

110| **A good result** | Add the merged PR, final changelog entry, accepted launch note, resolved ticket, before/after screenshot, or final Codex answer you want future threads to match. |

111 

112If the source is in Slack, Linear, GitHub, Notion, or Sentry, connect that tool in Codex with a [plugin](https://developers.openai.com/codex/plugins), mention it in the starter prompt, or paste the relevant part into the thread.

113 

114## What Codex creates

115 

116Most skills start as a `SKILL.md` file. `$skill-creator` can add longer references, scripts, or assets when the workflow needs them.

117 

118- my-skill/

119 

120 - SKILL.md Required: instructions and metadata

121 - references/ Optional: longer docs

122 - scripts/ Optional: repeatable commands

123 - assets/ Optional: templates and starter files

124 

125## Skills you could create

126 

127Use the same pattern when future threads should read the same runbook, run the same CLI, follow the same review rubric, write the same team update, or QA the same browser flow. For example:

128 

129- **`$buildkite-fix-ci`** downloads failed job logs, diagnoses the error, and proposes the smallest code fix.

130- **`$fix-merge-conflicts`** checks out a GitHub PR, updates it against the base branch, resolves conflicts, and returns the exact push command.

131- **`$frontend-skill`** keeps Codex close to your UI taste, existing components, screenshot QA loop, asset choices, and browser polish pass.

132- **`$pr-review-comments`** turns review notes into concise inline comments with the right tone and GitHub links.

133- **`$web-game-prototyper`** scopes the first playable loop, chooses assets, tunes game feel, captures screenshots, and polishes in the browser.

134 

135## Related use cases

136 

137[![](/images/codex/codex-wallpaper-2.webp)

138 

139### Create a CLI Codex can use

140 

141Ask Codex to create a composable CLI it can run from any folder, combine with repo scripts...

142 

143Engineering Code](https://developers.openai.com/codex/use-cases/agent-friendly-clis)[![](/images/codex/codex-wallpaper-1.webp)

144 

145### Create browser-based games

146 

147Use Codex to turn a game brief into first a well-defined plan, and then a real browser-based...

148 

149Engineering Code](https://developers.openai.com/codex/use-cases/browser-games)[![](/images/codex/codex-wallpaper-2.webp)

150 

151### Deploy an app or website

152 

153Use Codex with Build Web Apps and Vercel to turn a repo, screenshot, design, or rough app...

154 

155Front-end Integrations](https://developers.openai.com/codex/use-cases/deploy-app-or-website)