Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
parcadei avatar

Skill Development

  • 468 installs
  • 3.9k repo stars
  • Updated January 26, 2026
  • parcadei/continuous-claude-v3

skill-development is a Claude Code skill that defines authoring rules for reusable agent skills in `.claude/skills/` for developers who maintain versioned skill libraries with MCP wrappers and trigger configuration.

About

skill-development is a meta-skill from parcadei/continuous-claude-v3 that standardizes how developers create, version, and expand Claude agent skills. It prescribes SKILL.md structure with a clear When to Use section, copy-paste bash commands, and references to scripts/ for MCP operations. Developers keep each SKILL.md under 200 lines, avoid duplicating content across skills, and register every skill with a corresponding trigger in skill-rules.json. MCP wrapper skills use minimal allowed-tools such as Bash and Read. Reach for skill-development when adding or refactoring skills in a continuous-claude workflow so agents load consistent, triggerable capabilities.

  • Enables systematic creation and refinement of agent skills
  • Supports versioning and cataloging of reusable capabilities
  • Integrates with Skillselion directory standards
  • Automates skill metadata tagging and JSON output
  • Works across the entire solo-builder journey

Skill Development by the numbers

  • 468 all-time installs (skills.sh)
  • +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #100 of 782 Skill Development skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill skill-development

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs468
repo stars3.9k
Last updatedJanuary 26, 2026
Repositoryparcadei/continuous-claude-v3

How do you standardize Claude agent skill authoring?

Continuously improve, version, and expand their library of reusable agent skills.

Who is it for?

Developers maintaining a `.claude/skills/` library who need repeatable structure, triggers, and MCP wrapper conventions.

Skip if: Developers implementing application features unrelated to agent skill authoring or one-off prompts without a skills directory.

When should I use this skill?

The agent is creating, editing, or reviewing files under `.claude/skills/` or configuring skill-rules.json triggers.

What you get

Consistent SKILL.md files, skill-rules.json triggers, and MCP wrapper skills with restricted allowed-tools.

  • SKILL.md
  • skill-rules.json trigger entries
  • MCP wrapper skill definitions

By the numbers

  • SKILL.md must stay under 200 lines

Files

SKILL.mdMarkdownGitHub ↗

Skill Development Rules

When working with files in .claude/skills/:

SKILL.md Structure

DO

  • Keep SKILL.md concise (< 200 lines)
  • Include clear "When to Use" section
  • Provide copy-paste bash commands
  • Reference scripts/ for MCP operations
  • Add triggers to skill-rules.json

DON'T

  • Include implementation details in SKILL.md
  • Duplicate content across skills
  • Create skills without corresponding trigger in skill-rules.json
  • Use allowed-tools that aren't needed

MCP Wrapper Skills

For skills that wrap MCP scripts:

  • Use allowed-tools: [Bash, Read] to restrict capabilities
  • Point to the script in scripts/ directory
  • Include parameter documentation

Related skills

How it compares

Use skill-development for meta-authoring conventions; use domain skills for implementing product features.

FAQ

What belongs in SKILL.md vs scripts/?

skill-development keeps SKILL.md concise with When to Use, triggers, and copy-paste bash commands while delegating MCP operations and implementation details to scripts/ and avoiding duplication across skills.

Do new skills need skill-rules.json entries?

skill-development requires a corresponding trigger in skill-rules.json for every skill; creating skills without triggers violates the rules and breaks agent discovery.

Skill Developmentagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.