skill-creator (O_Ψ Verification Layer)
Purpose
Bootstrap, design, and package new skills.
Use When
- Capturing user intent for a brand new skill from conversation history.
- Conducting interviews to identify edge cases, input/output requirements, and dependencies for a new skill.
- Drafting the initial structure, frontmatter, and instructions for a new
SKILL.md file.
- Packaging finished skill folders into
.skill distributables.
Do Not Use When
- Auditing the active skill portfolio for collisions or stale documentation (use
arifos-recursive-audit instead).
- Running quantitative benchmarks or evaluating prompt traces (use
arifos-evals instead).
- Linting trigger names or checking vague verb usage (use
skill-trigger-linter instead).
Inputs
- User Concept: The high-level intent or workflow specified by the user.
- System Target: The proposed skill workspace directory.
Procedure
- Capture Intent: Analyze the user request and extract target tools, sequence steps, and expected outputs.
- Define Trigger Boundaries: Design preliminary "Use when" and "Do not use when" rules.
- Draft SKILL.md: Compose the frontmatter, purpose, triggers, inputs, procedure, postconditions, failure modes, and telemetry structure.
- Verification Setup: Propose 2-3 realistic test prompts for verification.
- Package Skill: Run
scripts/package_skill.py to compile the folder structure into a distributable package.
Postconditions
- A valid skill structure (including
SKILL.md) is successfully staged in the target folder.
- The skill complies with the baseline structural layout standards.
- The package is compiled without system compile errors.
Failure Modes & Escalation
- Intent Ambiguity: The user request is too vague to extract structured boundaries. Action: Pause generation and present clarifying questions regarding concrete tools and expected formats.
Telemetry per Run
{
"skill_name": "skill-creator",
"version": "1.0.0",
"trigger_phrase": "{{trigger_phrase}}",
"selected_reason": "{{selected_reason}}",
"latency_ms": 0,
"token_in": 0,
"token_out": 0,
"commands_run": 0,
"artifacts_written": 1,
"postcondition_pass": false,
"human_approval_required": false,
"hold_code": "{{hold_code}}"
}
Recursive Scorecard
- Activation Precision: [0.0 - 1.0] (Target: >0.95)
- Task Completion Rate: [0.0 - 1.0] (Target: >0.95)
- Rollback Safety: [0.0 - 1.0] (Target: 1.00)
- Context Efficiency: [0.0 - 1.0] (Target: >0.90)
- Doc Freshness: [0.0 - 1.0] (Target: 1.00)
- Cross-Skill Collision Rate: [0.0 - 1.0] (Target: 0.00)
- Human Trust Score: [0.0 - 1.0] (Target: >0.98)
1---2name: skill-creator-23description: Bootstrap, design, and package new skills. Load when capturing user intent for a new skill or drafting its initial instruction framework.4---5# skill-creator (O_Ψ Verification Layer)67## Purpose8Bootstrap, design, and package new skills.910## Use When111. Capturing user intent for a brand new skill from conversation history.122. Conducting interviews to identify edge cases, input/output requirements, and dependencies for a new skill.133. Drafting the initial structure, frontmatter, and instructions for a new `SKILL.md` file.144. Packaging finished skill folders into `.skill` distributables.1516## Do Not Use When171. Auditing the active skill portfolio for collisions or stale documentation (use `arifos-recursive-audit` instead).182. Running quantitative benchmarks or evaluating prompt traces (use `arifos-evals` instead).193. Linting trigger names or checking vague verb usage (use `skill-trigger-linter` instead).2021## Inputs22* **User Concept:** The high-level intent or workflow specified by the user.23* **System Target:** The proposed skill workspace directory.2425## Procedure261. **Capture Intent:** Analyze the user request and extract target tools, sequence steps, and expected outputs.272. **Define Trigger Boundaries:** Design preliminary "Use when" and "Do not use when" rules.283. **Draft SKILL.md:** Compose the frontmatter, purpose, triggers, inputs, procedure, postconditions, failure modes, and telemetry structure.294. **Verification Setup:** Propose 2-3 realistic test prompts for verification.305. **Package Skill:** Run `scripts/package_skill.py` to compile the folder structure into a distributable package.3132## Postconditions331. A valid skill structure (including `SKILL.md`) is successfully staged in the target folder.342. The skill complies with the baseline structural layout standards.353. The package is compiled without system compile errors.3637## Failure Modes & Escalation38* **Intent Ambiguity:** The user request is too vague to extract structured boundaries. *Action:* Pause generation and present clarifying questions regarding concrete tools and expected formats.3940## Telemetry per Run41```json42{43 "skill_name": "skill-creator",44 "version": "1.0.0",45 "trigger_phrase": "{{trigger_phrase}}",46 "selected_reason": "{{selected_reason}}",47 "latency_ms": 0,48 "token_in": 0,49 "token_out": 0,50 "commands_run": 0,51 "artifacts_written": 1,52 "postcondition_pass": false,53 "human_approval_required": false,54 "hold_code": "{{hold_code}}"55}56```5758## Recursive Scorecard59* **Activation Precision:** [0.0 - 1.0] (Target: >0.95)60* **Task Completion Rate:** [0.0 - 1.0] (Target: >0.95)61* **Rollback Safety:** [0.0 - 1.0] (Target: 1.00)62* **Context Efficiency:** [0.0 - 1.0] (Target: >0.90)63* **Doc Freshness:** [0.0 - 1.0] (Target: 1.00)64* **Cross-Skill Collision Rate:** [0.0 - 1.0] (Target: 0.00)65* **Human Trust Score:** [0.0 - 1.0] (Target: >0.98)