skill-writer

Enforce the Arsenal-first workflow for editing and syncing Claude skills.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cncorp/arsenal --skill skill-writer-cncorp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-writer
Source: https://github.com/cncorp/arsenal/tree/main/dot-claude/skills/skill-writer
Command: npx skills add https://github.com/cncorp/arsenal --skill skill-writer-cncorp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill explains how to create and edit Claude Code skills, ensuring changes flow through the Arsenal-first workflow.

Core Features & Use Cases

  • Arsenal-first workflow: edit in arsenal, sync with .claude/ via install.sh.
  • Documentation discipline: maintain SKILL.md structure and CLAUDE registry.

Quick Start

Edit a new skill in arsenal, then run install.sh to sync to .claude/.

Frequently Asked Questions about skill-writer

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

FAQPage Schema
How do I create a new Claude skill using the Arsenal-first workflow?

Create and edit your skill in the arsenal/dot-claude/skills directory, maintaining the prescribed skill structure and SKILL.md documentation. Run install.sh to sync changes to .claude/, ensuring the Arsenal repository remains your single source of truth for all skill definitions.

What is the Arsenal-first workflow and why does it matter for skill development?

The Arsenal-first workflow enforces edits in arsenal/dot-claude as the authoritative source, with install.sh propagating changes to .claude/. This prevents drift from direct edits and ensures skill structure, frontmatter, and validation stay consistent across your skill registry.

How do I sync my skill changes from Arsenal to the Claude directory?

After editing your skill in arsenal/dot-claude/skills and updating SKILL.md, run install.sh to propagate changes to .claude/. This step validates skill readiness before testing and maintains alignment between your Arsenal source and live skill definitions.

What documentation structure does a Claude skill require?

Each skill must include SKILL.md with proper frontmatter and registry updates in the CLAUDE file. Optional PRESSURE_TESTS.md documents edge cases and validation criteria; the Arsenal-first workflow enforces this structure to ensure consistent, testable skill definitions.

Can I edit skills directly in the .claude directory, or must I use Arsenal?

The Arsenal-first workflow mandates that edits originate in arsenal/dot-claude as the source of truth. Direct edits to .claude/ cause drift and are overwritten when you run install.sh, so always edit in Arsenal and sync via install.sh to maintain consistency.