Ceres Content Pipeline
SkillFiles & storageDesign, implement, or diagnose Ceres content builds, Addressables backends, bundle partitioning, dynamic releases, and build storage maintenance.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Ceres Content Pipeline skill
What this skill tells your AI
The instructions your AI receives, as published by akikurisu/ceres in Plugins/ceres/skills/ceres-contentpipeline/SKILL.md and read by ahel’s review.
Treat content identity, dependency analysis, partitioning, build execution, release output, and storage cleanup as separate stages. Inspect Editor/ContentPipeline and the application's content policy before changing a stage.
References
- Read build-graph.md for graph construction, dependency resolution, mounts, partitioning, and build backends.
- Read releases-and-storage.md for release outputs, artifact ownership, cleanup, and validation.
Content Pipeline APIs are Editor-only. Do not move build orchestration into runtime assemblies or make Ceres depend on a downstream product's catalog conventions.
Signals
- GitHub stars
- 129
- Forks
- 4
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
ceres-contentpipeline- Source
- github.com/akikurisu/ceres