use-cases/reusable-codex-skills.md Codex Docs, 2026-04-15 18:31 UTC → 2026-05-07 20:02 UTC

1# Save workflows as skills | Codex use cases1---

2 2name: Save workflows as skills

3Codex use cases3tagline: Create a skill Codex can keep on hand for work you repeat.

4 4summary: Turn a working Codex thread, review rules, test commands, release

5![](/assets/OpenAI-black-wordmark.svg)5 checklists, design conventions, writing examples, or repo-specific scripts

6 6 into a skill Codex can use in future threads.

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

8 8 - token: $skill-creator

9Codex use case9 url: https://github.com/openai/skills/tree/main/skills/.system/skill-creator

10 10 description: Gather information about the workflow, scaffold a skill, keep the

11# Save workflows as skills11 main instructions short, and validate the result.

12 12bestFor:

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.13 - Codified workflows you want Codex to use again.

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

25 15 thread.

26# Contents16starterPrompt:

27 17 title: Create a Skill From My Context

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

19 Use $skill-creator to create a Codex skill that [fixes failing Buildkite

20 checks on a GitHub PR / turns PR notes into inline review comments / writes

21 our release notes from merged PRs]

29 22 

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

31 23 

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.24 Use these sources when creating the skill:

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 25 

53| Skill | Why use it |26 - Working example: [say "use this thread," link a merged PR, or paste a good

54| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |27 Codex answer]

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 28 

57## Starter prompt29 - Source: [paste a Slack thread, PR review link, runbook URL, docs URL, or

30 ticket]

58 31 

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]32 - 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 33 

67Use $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]34 - Scripts or commands to reuse: [test command], [preview command],

68 Use these sources when creating the skill:35 [log-fetch script], [release command]

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

70- Source: [paste a Slack thread, PR review link, runbook URL, docs URL, or ticket]37 - Good output: [paste the Slack update, changelog entry, review comment,

71 - Repo: [repo path, if this skill depends on one repo]38 ticket, or final answer you want future threads to match]

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

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

41 url: /codex/skills

42---

74 43 

75## Create a skill Codex can keep on hand44## Create a skill Codex can keep on hand

76 45 

113 89 

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

115 91 

116- my-skill/

117 

118 - SKILL.md Required: instructions and metadata

119 - references/ Optional: longer docs

120 - scripts/ Optional: repeatable commands

121 - assets/ Optional: templates and starter files

122 

123## Skills you could create92## Skills you could create

124 93 

125Use 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:94Use 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:

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

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

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

132 

133## Related use cases

134 

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

136 

137### Create a CLI Codex can use

138 

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

140 

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

142 

143### Create browser-based games

144 

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

146 

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

148 

149### Iterate on difficult problems

150 

151Give Codex an evaluation system, such as scripts and reviewable artifacts, so it can keep...

152 

153Engineering Analysis](https://developers.openai.com/codex/use-cases/iterate-on-difficult-problems)