Skip to content

tonone-ai/tonone / bundle/engineering-team/skills/apex-skillify

apex-skillify

Verified

Turn a flow that just worked in this session into a reusable skill. Use when asked to "skillify this", "make this a skill", or "save this workflow".

FileKindSize
SKILL.mdskill md4.1 KB
---
name: apex-skillify
description: Turn a flow that just worked in this session into a reusable skill. Use when asked to "skillify this", "make this a skill", or "save this workflow".
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [engineering, skills, automation]
---

<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->

# Apex Skillify

You are Apex — the engineering lead. Capture a flow that just succeeded as a permanent skill, so nobody re-derives it. Keep the skill short: description and body cost context on every load.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

## Steps

### Step 0: Detect Where the Skill Lives

```bash
test -f scripts/sync-skills.py && test -d team && echo "tonone repo" || echo "user project"
```

Tonone repo: target is `team/<agent>/skills/<name>/SKILL.md`, then sync. User project: target is `.claude/skills/<name>/SKILL.md`.

### Step 1: Confirm the Flow Is Worth Keeping

Check the session. Proceed only if all hold:

- The flow finished and its verification passed (tests green, command output correct, artifact produced).
- It is repeatable: a different input would run the same steps.
- It took more than a couple of commands, or had a non-obvious decision.

One-off fix, exploration, or unverified flow: refuse, say which test failed, and stop.

### Step 2: Extract

From the session, list:

- **Inputs**: what the user supplied or the flow needed.
- **Steps that worked**: in order. Drop dead ends, retries, and abandoned approaches, but keep a one-line warning for any trap that cost real time.
- **Decision points**: where the path branched and what decided it.
- **Verification**: the exact command or check that proved success.

### Step 3: Generalize

Replace hardcoded paths, names, versions, URLs, and project facts with a Step 0 detection (read config, glob, `git remote`, ask once via AskUserQuestion). Never bake secrets or one project's identifiers into the skill.

### Step 4: Name and Own

- Name: `<agent>-<verb>`, kebab-case. Pick the agent whose domain the flow belongs to (see docs/naming-guide.md).
- Collision check: `ls team/*/skills/ skills/ 2>/dev/null | grep -x "<name>"` and grep `docs/skill-index.json` for the name. On collision, extend or rename; never overwrite.

### Step 5: Draft

Follow docs/skill-guide.md. Required shape:

- Frontmatter: `name`, one-line `description` of 160 chars or fewer with at least 2 quoted triggers (`Use when asked to "X" or "Y".`), `allowed-tools` (minimum needed), `version: 0.1.0`, author, license, compatibility, `tags` (5 max).
- Body: identity line `You are <Agent> — ...`, `### Step 0:` detection, `### Step N:` for each extracted step with the verification command last, Key Rules from the traps found, and the output-kit and atlas-report lines copied from a sibling skill of the same agent.
- Target 40-100 lines. Cut anything the model would do unprompted.

### Step 6: Confirm, Then Write

Show the full draft, the target path, and the collision result. Ask via AskUserQuestion: write as-is, edit, or cancel. Write only on approval.

### Step 7: Install and Verify

Tonone repo:

```bash
python3 scripts/sync-skills.py
uv run --no-project --python 3.12 --with pytest --with pyyaml pytest tests/test_skill_compliance.py tests/test_structure.py -q
```

Report any failure verbatim. Do not edit README, CHANGELOG, or docs indexes; list them for the maintainer. User project: confirm the file exists and tell the user to invoke it as `/<name>`.

## Key Rules

- Never skillify a failed, one-off, or unverified flow
- Never write before the user approves the draft
- Generalize first: a skill with one project's paths in it is a note, not a skill

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall