heady-skill-foundry

To package installable skill packs, you structure a skill directory containing SKILL.md, a machine-readable manifest, examples, and tests. The process automates manual packaging by enforcing manifest conventions, trigger schemas, and registry integration requirements.

A skill manifest is a machine-readable file defining the skill name, version, target surfaces, triggers, permissions, and dependencies. You define permissions by mapping specific actions to the permission model with clear justification for each required access level.

You register a skill pack in the skill registry by documenting its category, keywords, platform compatibility, and dependencies. This integration step ensures the packaged skill is discoverable and correctly wired into the system for installation.

Yes, you can build skill packs targeting Buddy, IDE, and Web surfaces. During the design phase, you articulate the target surfaces for your action packs, and the manifest validation ensures compatibility across the specified environments.

The best way to validate a skill pack is to verify its schema, tools, triggers, permissions, and end-to-end scenarios. This validation step prevents errors by checking that all manifest conventions and packaging structure requirements are satisfied.

You need to write step-by-step instructions to provide reusable, actionable guidance for agents executing the skill. These instructions are packaged within the skill directory to ensure consistent behavior across Buddy, IDE, and Web surfaces.