About ton-blockchain
ton-blockchain is a documentation workflow skill for tasks involving TON. It guides agents to consult TON Docs as the primary source, discover relevant pages, and use documentation as the basis for answers or implementation.
Key features
- 01Start with the TON Docs orientation page
- 02Discover pages through llms.txt
- 03Fetch relevant Markdown sources
- 04Use TON Docs as the primary reference
- 05Identify consulted documentation pages
Use cases
- 01Research TON APIs and concepts
- 02Check official guidance before changing code
- 03Resolve conflicts between repository conventions and docs
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ ton-blockchain/ skills --skill ton-blockchainAfter installing, type/ton-blockchainin Claude Code to confirm it loaded.
Bundled filesagents/openai.yaml
Details
From the project READMETON Docs-first workflow
Prefer primary sources from TON Docs.
1) Read the orientation page first
Fetch and skim the TON Docs “start here” page to align terminology and the docs’ structure before making assumptions:
curl -fsSL https://docs.ton.org/llms/start-here/content.md
If the .md URL fails, try the HTML page:
curl -fsSL https://docs.ton.org/start-here
2) Discover available pages
Fetch llms.txt to get the authoritative list of TON Docs pages and then search within it for relevant sections/pages:
curl -fsSL https://docs.ton.org/llms.txt
Practical pattern:
curl -fsSL https://docs.ton.org/llms.txt | rg -n "<topic>|<keyword>" || true
(Use grep -nE instead of rg if ripgrep isn’t available.)
3) Pull only the pages you need
For any relevant page path from llms.txt, prefer the Markdown source by appending /content.md and prepending /llms:
curl -fsSL "https://docs.ton.org/llms/<page-path>/content.md"
If that 404s, try the path as-is (some entries may already include .md or may not support source rendering):
curl -fsSL "https://docs.ton.org/<page-path>"
4) Execute the task using the docs as ground truth
- Treat TON Docs as the primary reference; reconcile contradictions explicitly.
- When answering, mention which TON Docs pages you consulted (page titles/paths).
- If the user’s code/repo conventions conflict with TON Docs guidance, ask for clarification before proceeding.