Ca New Skill

by arbiterForge

Author a new codeArbiter skill: prove the gap is real, get the spec approved, then write it.

409 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

138

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/arbiterForge/codeArbiter --skill ca-new-skill

The instruction itself

5 sections, as written by the author

$ca-new-skill — author a skill

The only permitted entry to creating a skill. Nothing is written until the gap is proven uncovered — skills are not created speculatively. Name the skill in verb-noun form ("dependency-review"), not as a description ("the thing that checks packages").

Flow

Routes to the skill-author skill, which owns the work end to end through its five gated phases — gap

evidence, scope, authoring, self-review against the v2 house style, and routing integration (the

INDEX.md + routing-table entry that makes the new skill reachable). The phase definitions live in the

skill; this command does not restate them. Nothing is authored until an existing skill or agent is

proven not to cover the need; nothing ships until the new skill carries gated phases, hard rules, and

its routing entry.

Routes to

skill-author (${CLAUDE_PLUGIN_ROOT}/routines/skill-author/SKILL.md) — all five phases.

When NOT to use

A one-time action → $ca-feature or a command definition.
An existing skill nearly covers it → extend that skill via $ca-feature.
"Do we even need a skill here?" → $ca-btw.

Hard gate

MUST prove the gap is real in Phase 1 before writing any skill content. MUST get user approval on the

spec before authoring. MUST NOT create a skill that duplicates an existing skill's purpose — surface

the overlap instead. Skill files live only under ${CLAUDE_PLUGIN_ROOT}/routines/<name>/.

Other skills for the same job

different authors, same section of the catalogue

Skill Creator

by anthropics

vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Replace with description of the skill and when Claude should use it.

35 tokens

Dispatching Parallel Agents

by ZhanlinCui

×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take arbiterforge/ca-new-skill from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.