Ca Create Context Agent Skill

by arbiterForge

Brownfield back-fill — scout an existing codebase and populate .codearbiter/, then lock it initialized.

437 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-create-context

The instruction itself

4 sections, as written by the author

$ca-create-context — brownfield populate

Wraps an existing codebase in project state without guessing. Dispatches parallel scouts to read the repository, synthesizes their findings into the surviving .codearbiter/ doc set, resolves gaps via a targeted interview, and locks the project initialized. No arguments — the skill reads the repo and asks only what it cannot determine.

The only permitted path to populate .codearbiter/ when meaningful source code already exists. For a greenfield project with no source, use $ca-decompose.

Routes to

The context-creation skill (${CLAUDE_PLUGIN_ROOT}/routines/context-creation/SKILL.md) — six gated

phases: pre-flight, scout dispatch, synthesis, gap interview, write, lock. Scouts return paths, line

numbers, and named values only — never raw source or secret values. The skill is canonical for the

phases and their gates.

When NOT to use

Project already initialized ( in CONTEXT.md) → $ca-status.
Greenfield project, no source → $ca-decompose.
.codearbiter/ not yet scaffolded → $ca-init first.
Update one doc → edit <project-root>/.codearbiter/ directly or use $ca-feature.

Hard gate

BLOCK if  is already present in CONTEXT.md. BLOCK if no meaningful source exists

(route to $ca-decompose). BLOCK if any scout fails to return before synthesis. BLOCK if any

[CONFIRM-NN] exits the gap interview unresolved and undeferred. MUST NOT write 

until every gap is resolved or deferred to open-questions.md.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take arbiterforge/ca-create-context 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.