adding-a-skill

Guide adding, updating, validating, and publishing public skills in the BuilderIO repository.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/lapaixkemsdortshlee-svg/AyitiMarket --skill adding-a-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adding-a-skill
Source: https://github.com/lapaixkemsdortshlee-svg/AyitiMarket/tree/main/.agents/skills/adding-a-skill
Command: npx skills add https://github.com/lapaixkemsdortshlee-svg/AyitiMarket --skill adding-a-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a repo-specific checklist for creating, updating, documenting, validating, and publishing public skills without missing the steps that keep discovery, catalog visibility, and framework behavior aligned.

Core Features & Use Cases

  • Skill Lifecycle Guidance: Covers the normal workflow for adding or editing a public skill folder and keeping its entry point, documentation, and metadata in sync.
  • Discovery and Validation: Helps verify that the skill is discoverable through dynamic install paths and that validation checks are run before release.
  • Framework Awareness: Calls out when instruction blocks, plugin metadata, or special plan skill sync paths need attention.
  • Use Case: A maintainer is preparing a new public skill and uses this guidance to make sure the skill file, catalog page, and validation steps are all handled correctly.

Quick Start

Use this skill to review the repository checklist before adding, updating, validating, or publishing a public BuilderIO skill.

Frequently Asked Questions about adding-a-skill

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

FAQPage Schema
How do I publish a public skill in the BuilderIO repository?

To publish a public skill, you must follow a checklist ensuring correct SKILL.md frontmatter, validation checks, and dynamic install discovery verification before updating the framework. This keeps catalog visibility and framework behavior aligned.

What is the required metadata for adding a public BuilderIO skill?

Adding a public skill requires correct SKILL.md frontmatter to define metadata, entry points, and documentation. You must also ensure plugin metadata and optional managed instruction block workflows are properly configured.

How do I validate a skill before publishing it to the catalog?

Validating a skill requires running specific validation checks before release to verify that the skill file, catalog page, and dynamic install paths are all handled correctly and discoverable.

Does updating skill instructions require framework sync?

Yes, when instruction behavior or special plan skill sync paths are involved, updating a public skill requires framework updates to ensure the instruction blocks and plugin metadata stay aligned.

What is the best way to ensure skill discovery through dynamic install paths?

To ensure skill discovery, you must verify dynamic install paths during the publishing workflow. This process checks that the skill folder, catalog documentation, and validation steps are properly configured for discovery.