skill-author

Author v2-format codeArbiter skills after validating gaps against the existing index.

139|7|Updated May 8, 2026
One-click install
npx skills add https://github.com/arbiterForge/codeArbiter --skill skill-author-arbiterforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-author
Source: https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca/skills/skill-author
Command: npx skills add https://github.com/arbiterForge/codeArbiter --skill skill-author-arbiterforge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you author new codeArbiter skills without guessing. It forces proof that the gap is real, confirms the scope, and keeps the new skill aligned with the house style and routing rules.

Core Features & Use Cases

  • Gap validation: Checks the existing skill index before any writing begins so you do not duplicate coverage.
  • Scope confirmation: Distinguishes routed vs dispatched work and command-invoked vs internal skills before authoring starts.
  • House-style authoring: Produces v2-format skill files with gated phases, hard rules, and routing integration.
  • Use case: Create a new skill for a missing workflow, prove it is not already covered, and wire it into the plugin cleanly.

Quick Start

Ask skill-author to create a new skill for your verified gap and follow its gated phases through routing integration.

Frequently Asked Questions about skill-author

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prove a skill gap exists before authoring a new gated workflow?

Gap analysis proves a skill gap exists by checking the existing skill index before writing begins. This validation process ensures new gated skills do not duplicate workflow coverage already present in the system.

What is the process for authoring skills with gated phases and house style formatting?

Skill authoring with gated phases requires v2 house-style formatting, evidence-based scope confirmation, and self-review. The process forces proof of a real gap, formats the file to house style, and integrates routing before release.

How do I distinguish routed vs dispatched work when creating a command-invoked skill?

Routed vs dispatched work is distinguished during scope confirmation before authoring starts. Scope confirmation classifies whether the new skill is command-invoked or internal, ensuring correct routing integration for the gated workflow.

What's the best way to integrate routing rules into a newly authored skill?

Routing integration is completed as a final gated phase before release. The skill-author process requires wiring routing rules into the plugin cleanly, ensuring the new skill dispatches or routes correctly within the existing index.

Do I need to check the existing skill index if my new workflow seems completely unique?

Checking the existing skill index is required before any writing begins, even for seemingly unique workflows. The gap validation phase enforces evidence-based scope confirmation to prove the gap is real and prevent coverage duplication.

Why does my new gated skill require self-review before release?

Self-review is required before release to verify v2 house-style formatting and routing integration. This gated phase ensures the authored skill meets codeArbiter standards, confirming scope and formatting align with existing index rules.