Cassiiopeia/projectops / skills/pro-skill-creator
pro-skill-creator
VerifiedCreate, review or improve a standard skill. Classifies intent as create/review/improve, then runs the matching phases. Use for 'make a skill', 'review this skill', 'improve this skill'.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.8 KB |
| references/anti_patterns.md | markdown | 4.4 KB |
| references/meta_principles.md | markdown | 5.1 KB |
| references/phase0_brainstorming.md | markdown | 8.6 KB |
| references/phase1_slots.md | markdown | 3.4 KB |
| references/phase2_question_format.md | markdown | 1.8 KB |
| references/phase4_checklist.md | markdown | 3.1 KB |
| references/phase6_report_format.md | markdown | 2.2 KB |
| references/review_improve.md | markdown | 4.0 KB |
| references/trigger_optimization.md | markdown | 2.6 KB |
| templates/config.json.example | other | 495 B |
| templates/python_cli_script.py | script | 3.9 KB |
references/phase1_slots.md
View on GitHub# Phase 1 — The 6 slots and automatic inference rules
Used in CREATE mode Phase 1. Extract the information the user already gave and fill as many of the 6 slots below as you can.
## Slot definitions
| Slot | What it holds | Inference clues | May it be empty? |
|------|------------|-----------|-------------------|
| `purpose` | The skill's one-line purpose | Verb + noun in the user's words | ❌ required |
| `triggers` | Which user utterances invoke it | "use this when ~", examples of similar tasks | ❌ required |
| `inputs` | Information the user must provide (files, values, environment) | Everything the user provided | ⭕ some skills have no inputs |
| `outputs` | Shape of the result | "create a file", "run a command", "a report" | ❌ required |
| `auto_extract` | Inputs that can be extracted automatically | Values readable directly from attached material | ⭕ |
| `pain_points` | What was confusing when done by hand | "before, ~ was hard" | ⭕ OK to be empty |
> Exit condition: Phase 1 ends when the 3 required slots (purpose/triggers/outputs) have values and each of the 3 optional slots is settled as either "has value" or "OK to be empty".
## Automatic inference rules (enforces H2)
Never ask again for information the user already gave. Extract automatically from these clues:
| What the user gave | Automatically extracted values |
|----------------|------------------|
| `docker-compose.yml` content | `service_name`, `ports`, `volumes`, `environment`, `image` |
| URL (`https://...`) | domain, port, protocol, path structure |
| Screenshot | UI screen name, menu path, button position |
| Error log | failing API, error code, cause hints |
| File path (`C:/.../foo.json`) | operating system, file format, project structure |
| Natural language like "the port is 3000" | fill that slot immediately |
| Git/repo URL | project name, hosting service (GitHub/GitLab/Bitbucket) |
## How to talk with the user
Do not show the whole slot table — it is too much information and overwhelms the user. Instead:
1. Present **only a one-line summary of the intent**: "So this is a skill that does '{purpose}', is invoked in situations like '{one representative trigger}', and produces '{outputs}' — right?"
2. User says "yes" / "right" → Phase 1 ends
3. User corrects "no, X is Y" → update only that slot and confirm again
## Example
**User utterance:**
> "Make a skill that accesses GitLab and fetches MR info. Ours is the in-house gitlab.example.com, with repos like platform/git-cm and pf/api-server. When I give an MR URL, extract the changed files; when I give a branch name, it should also create the MR automatically."
**Automatically extracted slots:**
| Slot | Value |
|------|-----|
| purpose | Look up MR and branch info and create MRs on the in-house GitLab |
| triggers | "show me the MR changed files", "open an MR from this branch", pasting a gitlab.example.com URL |
| inputs | repo alias, MR URL or iid, source branch name |
| outputs | JSON (changed file list), MR creation response |
| auto_extract | MR URL → project+iid, branch name → title/target/Redmine issue number |
| pain_points | (the user did not mention any — do not ask, skip) |
**One-line summary to show the user:**
> "So this is a skill that does 'MR and branch lookups + automatic MR creation on gitlab.example.com', invoked by things like 'pasting an MR URL' or 'what branches does the repo have?' — right?"
If the answer is "yes", Phase 1 ends → go straight to Phase 3 (0 empty slots).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |