create-skill

Create and synchronize agent skills across multiple repository roots.

2|Updated May 27, 2026
One-click install
npx skills add https://github.com/edlng/agents --skill create-skill-edlng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/edlng/agents/tree/main/skills/claude/create-skill
Command: npx skills add https://github.com/edlng/agents --skill create-skill-edlng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent skill development by providing a standardized workflow for creating, naming, and syncing new capabilities across multiple agent platforms.

Core Features & Use Cases

  • Unified Syncing: Automatically enforces the five-root sync convention to ensure skills are available across all agent environments.
  • Naming & Formatting Validation: Ensures new skills follow kebab-case naming and consistent documentation standards to maintain catalog quality.
  • Use Case: When you need to add a new custom tool to your agent library, this skill guides you through the creation process, checks for naming conflicts, and ensures the new skill is properly integrated into the shared repository structure.

Quick Start

Use the create-skill skill to initialize a new capability named data-validator following the standard repository conventions.

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I standardize AI agent skill creation across multiple repository roots?

To standardize AI agent skill creation across multiple repository roots, you can use an automated workflow that enforces the five-root sync convention, ensuring new capabilities are consistently structured and available across all agent environments.

What is the five-root sync protocol for modular agent development?

The five-root sync protocol is a repository management convention that automatically synchronizes newly created agent skills across multiple directory roots. It ensures structural integrity and consistent availability throughout your modular AI agent environments.

How do I enforce kebab-case naming conventions and documentation formatting for new agent skills?

Enforcing kebab-case naming conventions and documentation formatting for new agent skills requires an automated validation workflow. This process checks for naming conflicts and ensures structural integrity before integrating the capability into your shared repository.

Does this skill creation workflow require any specific dependencies or environments?

This skill creation workflow operates without external dependencies. It requires only adherence to the existing five-root sync protocol and your current documentation formatting standards to properly integrate new capabilities into the shared repository structure.

What's the best way to add a custom tool to an AI agent library without naming conflicts?

The best way to add a custom tool to an AI agent library without naming conflicts is to use an automated creation workflow that validates kebab-case naming conventions and checks for existing conflicts before synchronizing the new skill across all roots.

When should I avoid using an automated workflow for agent skill standardization?

You should avoid automated agent skill standardization workflows if your project does not follow a multi-root repository structure or if you cannot adhere to the required five-root sync protocol and existing documentation formatting standards.