feat: add SKILL.md

[jcstein]

Overview

Goal: SKILL.md should have an overview of how to post and retrieve blobs from Celestia.

• these are best methods/practices
• if submitting txs, this is how to

Nice-to-have: turn node api into something consumable by the agents – automation that puts out the openrpc.json into SKILL.md – or at least the top methods.

We already have these:
https://github.com/celestiaorg/docs?tab=readme-ov-file#llm-and-agent-support
https://github.com/celestiaorg/celestia-node/blob/main/CLAUDE.md
https://github.com/celestiaorg/celestia-app/blob/main/CLAUDE.md
https://github.com/celestiaorg/celestia-core/blob/main/CLAUDE.md

TODOs

• add site map https://docs.celestia.org/llms.txt to this
• easy based rollup deployment, like https://github.com/jcstein/dummy_rollup, in Go
• cron job: for an agent to check against openrpc.json and propose PR tag me + gbarros for review
• test with
  • claude code opus 4.6 https://mocha.celenium.io/tx/30b18ed62f7843b2a1325096903e6f4f3db0db6ebb0a29eaee8cd3a0c16f218f?tab=messages
  • claude opus 4.6 - gave me a main.go without go.mod, then go mod tidy ran into replace errs.
  • claude code sonnet 4.6 https://mocha-4.celenium.io/address/celestia1ed3kxqxvcemxcfgfxsh7mn6lmh4tlgfu4g2n20?tab=transactions
  • antigravity gemini 3.1 pro https://mocha-4.celenium.io/address/celestia1n20l3vdne0hpshcv3zzss5c3glh3sjyr7kmpdr?tab=transactions
  • codex gpt 5.4 https://mocha.celenium.io/address/celestia1fv6ch7v6d0n54zn3zp5un4e48ku5e5w9lqky55?tab=transactions
  • Codex 5.3 medium https://mocha-4.celenium.io/tx/65e5d9064ab1417c514568330e83082b6458159f58a658d19009ae3a240aa955?tab=messages
  • chatgpt
  • openclaw
• consolidates Celestia guidance into one SKILL.md
• routes by repo ownership and existing CLAUDE.md files
• adds conceptual grounding for what Celestia is and its role in the stack
• recommends tested Mocha blob submit/retrieve endpoints
• tells agents how to handle unfunded signers and which faucet to use
• replaces dead node RPC docs links with the current Node API docs page
• add to docs.celestia.org/SKILL.md, in /public directory

test prompt

I've downloaded this skill SKILL.md from Celestia website, a preview (use this as docs reference: https://celestiaorg.github.io/docs-preview/pr-2427/, not the production docs.celestia.org).

I want to build a PoC of a vanilla rollups on celestia DA. I want to prove we can post and retrieve blobs. I want all of it to be local to this project as if I am dockerizing it later as a service (not config/setup leakage to the user environment).

This rollup with be a ticker ping-pong (ping is a post, pong is a cofirmed retrieval from the chain).

[gemini-code-assist]

Summary of Changes

Hello @jcstein, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces two new "skill" definitions to streamline development and documentation processes within the Celestia project. One skill provides detailed guidelines for maintaining the Celestia documentation site, ensuring consistency and accuracy. The other establishes a routing mechanism to direct broad Celestia tasks to the appropriate repository, clarifying ownership and preventing misdirected effort.

Highlights

• Docs Maintainer Skill: Introduced a comprehensive guide for maintaining Celestia documentation, covering structural rules, style guidelines, variable usage, directory intent, chain-id warnings, link rules, repository facts, and a workflow checklist.
• Celestia Router Skill: Added a skill definition for routing Celestia-related tasks to the correct repositories (docs, celestia-app, celestia-node, cips), including decision rules, an intake checklist, handoff behavior, and safety considerations.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• SKILL.md
  • Added a new skill definition for Celestia documentation maintenance.
• skills/celestia-router/SKILL.md
  • Added a new skill definition for routing Celestia tasks across repositories.

Activity

• No activity has occurred on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

🚀 Preview Deployment

Your preview is ready: https://celestiaorg.github.io/docs-preview/pr-2427/

[jcstein]

https://app.devin.ai/review/celestiaorg/docs/pull/2427

[jcstein]

tested with Codex 5.4 extra-high:

Retest succeeded.

Using the same funded signer:

• Address: celestia1fv6ch7v6d0n54zn3zp5un4e48ku5e5w9lqky55
• Balance: 1000000utia
• Submitted at height: 10728758
• Retrieved payload: hello from codex

So the tested flow now works end-to-end with:

• CELE_DA_URL=http://celestia-testnet-consensus.itrocket.net:26658
• CELE_CORE_GRPC=rpc-mocha.pops.one:9090

That means the skill guidance is now grounded in a real successful Mocha submit/retrieve path, and the unfunded fallback guidance is also validated.

The final faucet-url edits are still local only. If you want, I can push those two last changes now.

[jcstein]

claude code opus 4.6:

~ % cd $HOME/code/test/celestia-blob && ./celestia-blob


Submitting blob: Hello from Celestia! Timestamp: 2026-04-02T01:39:12Z

=== Blob submitted successfully! ===
  Height:     10734598
  Namespace:  30303030303030303030303030303030303030303030303030303030303030303030303030303664373935663734363537333734356636653733
  Commitment: a04f94dbc834f9947c3d09c7b2231419a6c2ecfe97afc31d9caffd1d3496537b

Retrieving blob...
Retrieved data: Hello from Celestia! Timestamp: 2026-04-02T01:39:12Z
Done!

blob tx: https://mocha.celenium.io/tx/30b18ed62f7843b2a1325096903e6f4f3db0db6ebb0a29eaee8cd3a0c16f218f?tab=messages

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 18 additional findings in Devin Review.

[devin-ai-integration]

🟡 "Mainnet Beta" network reference line broken into two markdown list items

The replacement of "Coffee Beta" with "Mainnet Beta" was incorrectly split across two lines. Line 112 begins with - which markdown interprets as a new list item. The rendered output shows two broken list items: one ending with use "Mainnet and another starting with Beta" network..., instead of a single item reading use "Mainnet Beta" network.

Suggested change

	- **Network references**: use “Mainnet
	- Beta” network (note the specific capitalization)
	- **Network references**: use "Mainnet Beta" network (note the specific capitalization)

---

Was this helpful? React with 👍 or 👎 to provide feedback.