source-manifest-builder

Generate a deterministic asset manifest with SHA256 hashes for catalog ingestion.

Updated Mar 28, 2026

Search Tags:#discovery #catalog #yaml #manifest #source #asset-store #repo-author

Ready to run

npx skills add https://github.com/skaile-ai/ai-assets --skill source-manifest-builder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-manifest-builder
Source: https://github.com/skaile-ai/ai-assets/tree/main/ai-asset-management/skills/source-manifest-builder
Command: npx skills add https://github.com/skaile-ai/ai-assets --skill source-manifest-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the creation of a deterministic, author-curated asset manifest for repositories, enabling reproducible inventory in .skaile-source.yaml.

Core Features & Use Cases

Walks the repository to discover assets, computes SHA256 hashes, and produces the assets block for catalog ingestion.
Applies publisher mapping and file filtering to ensure clean, reviewable entries.
Supports integration with Skaile's review workflow and publishing paths (public catalog or private libraries).

Quick Start

Run the source manifest builder to generate the .skaile-source.yaml assets block for your repository.

Frequently Asked Questions about source-manifest-builder

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

FAQPage Schema

How do I generate a deterministic asset manifest for a repository catalog?▼

Generating a deterministic asset manifest requires walking the repository to discover files, computing SHA256 hashes, and writing the curated assets block to a .skaile-source.yaml file for reproducible catalog ingestion.

What is an asset manifest and when do I need one for catalog publishing?▼

An asset manifest is a reproducible inventory of repository files with publisher mapping and hashes. You need one when submitting assets to a catalog to enforce versioning, ensure file integrity, and guard against drift during review workflows.

How do I compute SHA256 hashes and filter files for a YAML manifest?▼

Computing SHA256 hashes and filtering files for a YAML manifest involves applying file filtering rules to exclude unwanted entries, calculating cryptographic hashes for the remaining assets, and mapping them to the correct publisher before writing the block.

Can I integrate manifest generation with a review and publishing workflow?▼

Yes, manifest generation integrates with review and publishing workflows to guard against drift. This ensures that the generated .skaile-source.yaml assets block remains reproducible and clean when publishing to a public catalog or private library.

Why does my repository asset inventory drift between catalog ingestions?▼

Repository asset inventory drift occurs when manifests are not deterministic. Enforcing explicit file entries, versioning constraints, and author-curated publisher mapping during manifest generation prevents drift and ensures reproducible catalog ingestion.

Do I need explicit versioning before building a source manifest?▼

Yes, explicit versioning is required when building a source manifest. The process enforces versioning and explicit file entries to ensure the resulting .skaile-source.yaml block remains deterministic and reproducible for catalog ingestion.