# Skill Creator

Create, revise, evaluate, publish, and improve Open-Science Skills through the native...

- Repository: https://github.com/aipoch/open-science (5414 stars)
- Category: Testing
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add aipoch/open-science --skill skill-creator -g -a claude-code -y`
Codex: `npx skills add aipoch/open-science --skill skill-creator -g -a codex -y`
Cursor: `npx skills add aipoch/open-science --skill skill-creator -g -a cursor -y`
Gemini CLI: `npx skills add aipoch/open-science --skill skill-creator -g -a gemini-cli -y`

## Description

Create, revise, evaluate, publish, and improve Open-Science Skills through the native JavaScript host.skills composer. Use when the user wants a reusable workflow, an existing Skill changed, test cases or benchmarks for a Skill, or better Skill triggering.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Skill Creator

Create one focused, reusable Skill package. Skills are application-managed packages, not Artifacts.
Use the JavaScript control-plane REPL and the native `host.skills` composer for lifecycle operations.

## Native composer

```javascript
await host.skills.list()
await host.skills.read(name)
await host.skills.read(name, path)
await host.skills.validate(name)
await host.skills.edit(name, path, content)
await host.skills.edit(name, path, replacement, oldString)
await host.skills.publish(name)
await host.skills.publish(name, true)
await host.skills.delete(stableId)
```

Without `oldString`, `edit` creates a file and fails if it exists. With `oldString`, the old text
must occur exactly once. Never silently overwrite an existing draft file. `publish` promotes the
complete draft into Personal Skills. `delete` is privileged and always uses app approval. When a
published Skill and its draft coexist, delete only by the exact `draft-<name>` or `personal-<name>`
id returned from `list()`; never guess from the shared display name.

## Choose the current stage

Infer where the user is in the workflow and start there:

1. Capture intent and examples.
2. Draft or revise the Skill.
3. Review the package with the user.
4. Optionally evaluate realistic prompts.
5. Improve from evidence and repeat.
6. Publish only after the user accepts the draft.

Do not force evaluation. Objectively verifiable workflows benefit from test cases; subjective writing
or exploratory Skills may be better reviewed directly in conversation.

## Capture intent

Extract what is already known from the conversation before asking questions. Confirm only gaps that
materially change behavior:

The rest: https://github.com/aipoch/open-science/blob/HEAD/resources/skills/skill-creator/SKILL.md