Ceres Content Pipeline
SkillFiles & storageHelps your agent design, build, and fix game content build pipelines, bundle packaging, releases, and storage cleanup.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Ceres Content Pipeline skill
About this skill
Design, implement, or diagnose Ceres content builds, Addressables backends, bundle partitioning, dynamic releases, and build storage maintenance.
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
- Key
ceres-contentpipeline- Source
- github.com/akikurisu/ceres