Skip to content

Add Creative skill to experimental catalog #398

@frido22

Description

@frido22

Proposal

Add creative as an experimental Codex skill.

Suggested path:

skills/.experimental/creative/
  SKILL.md
  LICENSE.txt

Source repo:
https://github.com/frido22/creative_skill

Installable skill file:
https://github.com/frido22/creative_skill/blob/main/skills/creative/SKILL.md

What it does

Creative is a minimal procedural skill that pushes an LLM away from default answers while preserving usefulness, feasibility, and simplicity. It is intended for code, design, writing, naming, architecture, debugging, and strategy tasks where the obvious answer is likely to be generic or stuck.

Why include it

Most skill submissions are instructions only. This repo includes:

  • the installable skills/creative/SKILL.md
  • an automated benchmark suite
  • 80 default benchmark tasks
  • generated benchmark results
  • a README with a clear result table
  • GitHub Actions and tests

Benchmark headline from the current public run:

Judge question Creative won 95% CI
Which answer was better overall? 78.75% 68.6%-86.3%
Which answer is less default and brings a better non-obvious angle? 87.50% 78.5%-93.1%

The benchmark uses blind pairwise judging and stores hidden labels only for metric computation.

Proposed SKILL.md

---
name: creative
description: Use when the user wants a more original, non-default solution for code, design, writing, naming, architecture, debugging, or strategy, especially when progress is stuck or the obvious approach is failing.
---
# Creative
Refuse the first clean answer.
1. Generate the First Five internally.
2. Assume they are surface-level.
3. Create 5 better candidates using:
   invert, subtract, constrain, cross-domain borrow, failure-first.
4. Select or merge the strongest.
5. Ship the strongest version.
Rules:
- Weird is welcome.
- Default is failure.
- Beauty counts.
- The final idea must still work.
- Do not add complexity just to look creative.
- Before finalizing, compare the strongest idea against the obvious/default answer and only keep it if it is more useful, not just weirder.
End with:
`Creative move: <what made this less default>`

License

The source repo is MIT licensed. The proposed LICENSE.txt for the OpenAI skills catalog would use the same MIT license text from the repo.

Notes

I can follow up with a direct PR adding the files under skills/.experimental/creative/ if that is the preferred submission path.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions