celestia

Route Celestia requests to the correct repository and apply canonical source guardrails.

182|421|Updated Mar 16, 2022
One-click install
npx skills add https://github.com/celestiaorg/docs --skill celestia-celestiaorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: celestia
Source: https://github.com/celestiaorg/docs/tree/main/public
Command: npx skills add https://github.com/celestiaorg/docs --skill celestia-celestiaorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route Celestia requests to the correct repository and apply docs guardrails, ensuring changes reference canonical sources and align with repo-specific conventions.

Core Features & Use Cases

  • Route requests to docs, celestia-node, celestia-app, or celestia-core based on ownership and task scope.
  • Enforce docs guardrails and source-of-truth references (llms.txt, CLAUDE.md) when proposing edits or commands.
  • Coordinate multi-repo tasks by clearly signaling the target repo and separating outputs per ownership.

Quick Start

Route a Celestia query to the appropriate repository and apply the latest docs guardrails.

Frequently Asked Questions about celestia

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

FAQPage Schema
How do I route Celestia development requests to the correct repository?

Celestia repo-routing directs requests to the appropriate repository—docs, celestia-node, celestia-app, or celestia-core—based on task scope and ownership. It applies canonical guardrails and ensures outputs reference source-of-truth files like llms.txt and CLAUDE.md.

What are docs guardrails and how do they apply to Celestia repository edits?

Docs guardrails are canonical conventions enforced during Celestia repo routing. They ensure proposed edits and commands reference source-of-truth files like llms.txt and CLAUDE.md, maintaining consistency across docs, celestia-node, celestia-app, and celestia-core repositories.

How do I coordinate multi-repo tasks across Celestia repositories?

Multi-repo Celestia tasks are coordinated by signaling target repo ownership and splitting outputs per repository. This ensures each repo receives only its relevant changes while maintaining canonical blob submission and retrieval guidance across docs, celestia-node, celestia-app, and celestia-core.

Can I use repo-routing for Celestia blob submission and retrieval guidance?

Yes, Celestia repo-routing applies canonical blob submission and retrieval guidance when directing requests to the correct repository. It enforces repo-specific guardrails and ensures outputs align with updated official source conventions.

What's the best way to ensure Celestia docs changes reference canonical sources?

Use repo-routing to enforce docs guardrails that require references to canonical sources like llms.txt and CLAUDE.md. This ensures all proposed Celestia edits and commands align with official repo-specific conventions and source-of-truth documentation.

When should I not use automated repo-routing for Celestia repository tasks?

Repo-routing may not suit tasks requiring cross-repo atomic commits or custom workflows outside standard Celestia docs, celestia-node, celestia-app, or celestia-core conventions. It enforces specific guardrails and canonical source references, limiting flexibility for unconventional or unsupported operations.