create-skill

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.

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.

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.

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.

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.

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.