create-skill

Create portable AI agent skills with clear organization and placement rules.

1|Updated Jul 7, 2022

Search Tags:#AI agent #skill creation #code structure #portability #skill organization

Ready to run

npx skills add https://github.com/chiubaka/circleci-orb --skill create-skill-chiubaka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/chiubaka/circleci-orb/tree/main/org/agents/skills/create-skill
Command: npx skills add https://github.com/chiubaka/circleci-orb --skill create-skill-chiubaka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a clear, structured approach to creating AI agent skills, ensuring they are portable, maintainable, and scoped appropriately.

Core Features & Use Cases

Scope Decision: Guides on whether a skill should be org-level or repo-level, based on reusability and dependency considerations.
Skill Creation Guide: Provides detailed instructions on where to create the skill, naming conventions, and self-containment rules.
Portability Rules: Ensures org-level skills do not depend on a single repository, promoting portability and reusability.
Example Patterns: Offers illustrative examples for deciding skill level based on specific scenarios.

Quick Start

Create a new org-level skill by placing SKILL.md in org/agents/skills/<skill-name>/ and ensure it is self-contained and avoids repo-specific dependencies.

Frequently Asked Questions about create-skill

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

FAQPage Schema

How do I create AI agent skills that are portable across multiple repositories?▼

To create portable AI agent skills, place your `SKILL.md` in `org/agents/skills/<skill-name>/` and ensure it is self-contained with no repo-specific dependencies. This organization keeps skills reusable across different repositories.

When should an AI agent skill be org-level versus repo-level?▼

An AI agent skill should be org-level when it requires high reusability across multiple repositories, and repo-level when it has dependencies specific to a single repository. Scope decisions depend on reusability and dependency factors.

What's the best way to organize AI agent skill code structure for maintainability?▼

The best way to organize AI agent skill code structure is to follow self-containment rules and clear naming conventions. Place files in designated directories like `org/agents/skills/` to ensure maintainability and portability across teams.

Does an org-level AI agent skill depend on a single repository?▼

No, an org-level AI agent skill does not depend on a single repository. Portability rules require org-level skills to be self-contained, ensuring they can be reused across multiple repositories without dependency conflicts.

How do I start creating a new AI agent skill with clear placement rules?▼

Start creating a new AI agent skill by placing a `SKILL.md` file in `org/agents/skills/<skill-name>/`. Follow the provided naming conventions and ensure the skill is self-contained to adhere to placement and portability rules.

Can I use existing example patterns to decide the scope of my AI agent skill?▼

Yes, you can use illustrative example patterns to decide the scope of your AI agent skill. These examples guide whether a skill should be org-level or repo-level based on specific scenarios and dependency considerations.