source-sidecar-curator

Refine sidecar manifests for local asset sources with YAML validation and version pinning.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/skaile-ai/ai-assets --skill source-sidecar-curator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-sidecar-curator
Source: https://github.com/skaile-ai/ai-assets/tree/main/ai-asset-management/skills/source-sidecar-curator
Command: npx skills add https://github.com/skaile-ai/ai-assets --skill source-sidecar-curator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refines a sidecar manifest for local asset sources under ~/.skaile/sources by guiding users through verification, editing, and committing steps to ensure accurate publisher mappings, versioning, and asset inventories.

Core Features & Use Cases

  • Step through Locate, Read, Interview, Edit, Verify, and Commit to curate a sidecar manifest that governs local source discovery.
  • Enforce explicit file inventories, per-entry versioning, and proper requires graph enrichment, with an optional deps-analyzer for cross-asset relationships.
  • Ideal for teams maintaining local-sidecar metadata across many sources, enabling safer updates and auditable changes.

Quick Start

Run skaile source sidecar edit <slug> to begin the interactive refinement workflow.

Frequently Asked Questions about source-sidecar-curator

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

FAQPage Schema
How do I validate and refine a local sidecar manifest for asset discovery?

To validate a sidecar manifest, use an interactive workflow that steps through verification, editing, and committing. This enforces strict YAML structure, per-entry field validation, and version pinning for local asset sources.

What is the process for pinning versions in a sidecar manifest?

Version pinning in a sidecar manifest requires explicit versioned assets within a strict YAML structure. The curation workflow validates per-entry fields to ensure accurate version mapping before committing changes.

How do I manage cross-asset dependencies in local sidecar manifests?

Managing cross-asset dependencies involves running an optional dependency analyzer to enrich the requires graph. This validates relationships between local assets during the manifest refinement workflow.

Can I use the sidecar manifest curator for synchronizing local asset sources?

Yes, the sidecar manifest curator is designed for asset discovery and synchronization workflows. It guides users through locating, reading, interviewing, editing, verifying, and committing local source metadata.

What is the best way to enforce explicit file inventories in local source metadata?

The best way to enforce explicit file inventories is using a structured curation workflow that validates per-entry fields within a strict YAML format. This ensures accurate publisher mappings before committing local source updates.

Why does my sidecar manifest validation fail during local asset discovery?

Sidecar manifest validation fails when the YAML structure is invalid, assets lack proper versioning, or per-entry fields contain errors. The interactive workflow identifies these issues during the verification step before committing.