From cca13fb03a00d5b109ae396b2256c32a786339eb Mon Sep 17 00:00:00 2001 From: xl-openai Date: Mon, 9 Feb 2026 13:37:27 -0800 Subject: [PATCH] skill-creator: Remove invalid reference. (#10960) Remove references to two files that do not exist. --- .../src/skills/assets/samples/skill-creator/SKILL.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/codex-rs/core/src/skills/assets/samples/skill-creator/SKILL.md b/codex-rs/core/src/skills/assets/samples/skill-creator/SKILL.md index 4c0220dd4..72bc0b97e 100644 --- a/codex-rs/core/src/skills/assets/samples/skill-creator/SKILL.md +++ b/codex-rs/core/src/skills/assets/samples/skill-creator/SKILL.md @@ -318,15 +318,6 @@ Only include other optional interface fields when the user explicitly provides t When editing the (newly-generated or existing) skill, remember that the skill is being created for another instance of Codex to use. Include information that would be beneficial and non-obvious to Codex. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Codex instance execute these tasks more effectively. -#### Learn Proven Design Patterns - -Consult these helpful guides based on your skill's needs: - -- **Multi-step processes**: See references/workflows.md for sequential workflows and conditional logic -- **Specific output formats or quality standards**: See references/output-patterns.md for template and example patterns - -These files contain established best practices for effective skill design. - #### Start with Reusable Skill Contents To begin implementation, start with the reusable resources identified above: `scripts/`, `references/`, and `assets/` files. Note that this step may require user input. For example, when implementing a `brand-guidelines` skill, the user may need to provide brand assets or templates to store in `assets/`, or documentation to store in `references/`.