repo-skill-creator git:20260224.5995a63A

Immutable. This exact content never changes and is served at /api/v1/blob/05198b4990c881c3.

---
name: repo-skill-creator
description: Create and maintain repository skills for adonis-skills. Use when users ask to scaffold a new skill under skills/, generate agents/openai.yaml, run skill validation, refresh web index data, or standardize the skill authoring workflow.
---

# Repo Skill Creator

Create and maintain repository skills with a triple workflow: creation mode, path-finalize mode, and auto-discover finalize mode.

## Trigger Rules

1. If the user provides a `skills/*` path and indicates the skill is already generated/copied, run path-finalize mode directly without additional confirmation.
2. If the user invokes this skill directly without providing a path, run auto-discover finalize mode (`skills:finalize:new`) first.
3. If no new skill can be discovered during auto-discover mode, fall back to creation mode (`skills:new`) and then continue finalize.

## Mode A: Create New Skill

Primary command (recommended):

```bash
pnpm skills:new
```

Manual creation commands:

```bash
pnpm skills:init <skill-name> --path skills --resources scripts,references
pnpm skills:finalize -- skills/<skill-name>
```

## Mode B: Finalize Existing Skill by Path

When the user pastes a path under `skills/*`, run:

```bash
pnpm skills:finalize -- <skill-path>
```

Examples:

```bash
pnpm skills:finalize -- skills/code-inspector-init
pnpm skills:finalize -- /Users/adonis/coding/adonis-skills2/skills/code-inspector-init/
```

Finalize pipeline is fixed and must run in order:

1. `pnpm skills:quick-validate skills/<skill-slug>`
2. `pnpm skills:validate`
3. `pnpm skills:index`

## Mode C: Auto Discover + Finalize + Stage

When user does not pass a `skills/*` path, run:

```bash
pnpm skills:finalize:new
```

Behavior contract:

1. Discover newly added skill candidates from `git status --short --untracked-files=all`:
   - include `A` (index-added) and `??` (untracked)
   - only accept slugs where `skills/<slug>/SKILL.md` itself is in `A` or `??`
2. Finalize each discovered slug in stable sorted order:
   - `pnpm skills:finalize -- skills/<slug>`
   - stop immediately on first failure
3. Stage only related files after all finalize runs succeed:
   - `git add skills/<slug>` for each processed slug
   - `git add apps/web/src/generated/skills-index.json` when changed
4. If no new skill is discovered:
   - auto-run `pnpm skills:new`
   - re-scan for newly added skills and continue this mode

## Scope Boundaries

- Do not auto-run `pnpm skills:openai-yaml` unless explicitly requested.
- Do not auto-run local install/sync (`skills:install:local`, `skills:test:local`) unless explicitly requested.
- Do not use `git add -A`; only stage skill-related files from this workflow.

## Output Contract

When executing this skill, always return:

1. Commands executed (or planned commands in dry-run).
2. Success/failure status.
3. Detected/processed skill slugs and staged file paths.
4. Next-step suggestion only when useful (for example, local agent testing via `pnpm skills:test:local`).

## Skill Rules

1. Use lowercase hyphen-case skill names.
2. Keep `SKILL.md` frontmatter valid with non-empty `name` and `description`.
3. `frontmatter.description` must be English-only (ASCII characters only), and should clearly include when to use the skill.
4. Add optional directories (`scripts/`, `references/`, `assets/`) only when needed.
5. Re-run validation and index generation after updates and before commit.