orkcore-catalog

Answer questions about Orkid asset catalogs, manifests, and import/export workflows.

35|16|Updated Feb 10, 2013
One-click install
npx skills add https://github.com/tweakoz/orkid --skill orkcore-catalog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orkcore-catalog
Source: https://github.com/tweakoz/orkid/tree/main/.claude/skills/orkcore-catalog
Command: npx skills add https://github.com/tweakoz/orkid --skill orkcore-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Answer questions about Orkid's asset catalog system, manifests, asset entries, config spaces, and the import/export workflow.

Core Features & Use Cases

  • Provides a reference for AssetCatalog components, manifest loading, asset entries, and config spaces.
  • Covers the asset import/export workflow, chunking, and encryption concepts used by Orkid's catalog system.
  • Use Case: When debugging asset packaging, manifests, or CDN integration within Orkid.

Quick Start

Explain how to use the catalog references to answer questions about asset packaging, manifests, and the import workflow.

Frequently Asked Questions about orkcore-catalog

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

FAQPage Schema
How does the Orkid asset catalog import pipeline handle manifest loading and asset entries?

The Orkid asset catalog import pipeline processes manifests and asset entries by referencing public interfaces in catalog.h and manifest.h. It structures asset packaging, chunking, and config spaces for precise catalog tooling integration.

What is the role of config spaces in Orkid's asset catalog system?

Config spaces in Orkid's asset catalog system organize asset entries and manifests into distinct configuration environments. They are defined in config.h to manage asset packaging and import/export workflow variations.

How do I debug asset packaging and CDN integration issues within the Orkid ecosystem?

Debug asset packaging and CDN integration in Orkid by examining the catalog references and chunk_manifest.h. These sources provide detailed guidance on the import pipeline, asset entries, and CDN delivery mechanisms.

Does the Orkid catalog system support encryption for asset entries during the import workflow?

Yes, the Orkid catalog system supports encryption concepts for asset entries during the import and export workflow. It integrates encryption directly into the asset packaging and chunking processes defined by the catalog tooling.

How does chunking work when processing chunk manifests in Orkid's asset catalog?

Chunking in Orkid's asset catalog splits asset data into manageable chunks defined by chunk_manifest.h. This process optimizes asset packaging and CDN integration during the import pipeline and manifest loading.

Can I use the Orkid asset catalog tooling without external dependencies for manifest loading?

Yes, the Orkid asset catalog tooling operates without external dependencies. It relies solely on internal public interfaces like catalog.h, manifest.h, and config.h to manage manifest loading and asset entries.