kata-skill-package

Package skill source directories into deterministic .skill bundles with SHA-256 manifests.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-skill-package
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kata-skill-package
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-skill-package
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-skill-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual, error-prone steps required to bundle a skill’s source into a consumable, versioned, hash-verified delivery package.

Core Features & Use Cases

  • Deterministic packaging from source to delivery: Copies {paths.skills_root}/{slug}/ to {paths.skills_build}/{slug}/ and then materializes {paths.skills_dist}/{slug}.skill/ as a structured artifact.
  • Manifest and integrity guarantees: Generates .skill-manifest.json with schema versioning, skill metadata (name, version, language), framework ahrena_commit, file SHA-256 hashes, and reference snapshots.
  • Structure-safe validation gates: Validates the source up front (via kata-skill-validate) and validates the finished package against lex-skill-package-structure, blocking any packaging when violations are found.

Quick Start

Run kata-skill-package with slug set to the skill directory name you want to package.

Frequently Asked Questions about kata-skill-package

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

FAQPage Schema
How do I create a deterministic build package for a skill?▼

A skill package manifest is a JSON file containing schema versioning, skill metadata, framework commit references, and SHA-256 file hashes to verify integrity and enable deterministic builds.

How do I generate a SHA-256 integrity manifest for my skill package?▼

The skill automatically computes SHA-256 hashes for all packaged files and generates a .skill-manifest.json file, capturing metadata and reference snapshots to guarantee hash integrity.

Does the packaging process validate the skill package structure before delivery?▼

Yes, the skill validates the source up front and validates the finished package against lex-skill-package-structure, applying a hard fail on any structural violations to block bad packaging.

What do I need to set up before packaging a skill from source?▼

You need a SKILL.md file with frontmatter specifying version and language, a valid skill source directory, and the framework HEAD commit to ensure deterministic build traceability.

Why does my skill pipeline fail with a package structure violation?▼

The skill pipeline enforces a hard fail on violations when validating the finished package against lex-skill-package-structure, blocking any packaging if the source or output format is invalid.