Nestjs Trpc
trycompai/crm
Build end-to-end type-safe tRPC APIs inside NestJS using the nestjs-trpc adapter — @Router/@Query/@Mutation/@Subscription decorators, TRPCModule.forRoot, injectable middlewares and context, Zod…
Guide for regenerating Axone contract schemas and rendered Markdown docs.
Install Doc Generation
$ npx skills add axone-protocol/contracts --skill doc-generation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install axone-protocol/contracts doc-generation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/doc-generation .claude/skills/doc-generation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "doc-generation" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/skills/doc-generation into .claude/skills/doc-generation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-generation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/axone-protocol/contracts/tree/main/.agents/skills/doc-generationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add axone-protocol/contracts --skill doc-generation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install axone-protocol/contracts doc-generation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/doc-generation .agents/skills/doc-generation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "doc-generation" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/skills/doc-generation into .agents/skills/doc-generation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-generation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add axone-protocol/contracts --skill doc-generation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install axone-protocol/contracts doc-generation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/doc-generation .cursor/skills/doc-generation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "doc-generation" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/skills/doc-generation into .cursor/skills/doc-generation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-generation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/axone-protocol/contracts.git --path .agents/skills/doc-generation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add axone-protocol/contracts --skill doc-generation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install axone-protocol/contracts doc-generation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/doc-generation .gemini/skills/doc-generation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "doc-generation" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/skills/doc-generation into .gemini/skills/doc-generation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-generation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install axone-protocol/contracts doc-generationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add axone-protocol/contracts --skill doc-generation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/doc-generation .github/skills/doc-generation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "doc-generation" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/skills/doc-generation into .github/skills/doc-generation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-generation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add axone-protocol/contracts --skill doc-generation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install axone-protocol/contracts doc-generation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/axone-protocol/contracts.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/doc-generation .opencode/skills/doc-generation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "doc-generation" agent skill from https://github.com/axone-protocol/contracts/tree/main/.agents/skills/doc-generation into .opencode/skills/doc-generation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-generation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
doc-generation- GitHub stars
- 123
- Token cost
- ~590 tokens
- SKILL.md length
- 223 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Guide for regenerating Axone contract schemas and rendered Markdown docs.
- Metadata change
- SKILL.md covers Source of Truth, What cargo make docs really does, Standard Workflow and When regeneration is required, plus 2 more sections
- Calls cargo and git
- Checking generated-doc drift
What it does
Doc Generation is an agent skill from axone-protocol/contracts. Guide for regenerating Axone contract schemas and rendered Markdown docs. Use when contract APIs or metadata change, when checking generated-doc drift, or when preparing documentation commits.
Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs. It works with Rust. The repository describes itself as: 📜 Smart contracts for the Axone protocol. The licence is BSD-3-Clause.
When your agent uses it
- Metadata change
- Checking generated-doc drift
- Preparing documentation commits
Example prompts
- “/doc-generation”
What it can do on your machine
Read from SKILL.md and the folder at commit 02724f3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
cargogit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Doc Generation loads about 590 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 223 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from axone-protocol/contracts at commit 02724f3, republished under its BSD-3-Clause licence (© axone-protocol). 223 words, ~590 tokens.
Download SKILL.mdSave it as
.claude/skills/doc-generation/SKILL.md (or your agent's skills folder).- name
- doc-generation
- description
- Guide for regenerating Axone contract schemas and rendered Markdown docs. Use when contract APIs or metadata change, when checking generated-doc drift, or when preparing documentation commits.
- license
- BSD-3-Clause
- metadata.author
- axone.xyz
- metadata.version
- 1.0
Generated Documentation
Source of Truth
Generated docs come from Rust API types and schema metadata:
Rust messages/types + metadata.json
↓
contracts/*/schema/*
↓
docs/*.mdIn this repository, the canonical command is:
cargo make docsDo not treat docs/*.md as hand-edited source files. The Rust types and metadata are the source of truth.
What cargo make docs really does
cargo make docs already depends on:
- prerequisite checks (
npx,awk,perl,jq) cargo make schema
That means one docs refresh can update both:
contracts/*/schema/*docs/*.md
Standard Workflow
Regenerate everything
cargo make docsInspect what changed
git status --short
git diff -- docs contractsCommit the generated artifacts
If the change is documentation generation only, prefer a message such as:
docs(gov): regenerate documentation
docs(vc): regenerate documentation
docs: regenerate generated documentationAvoid vague subjects such as docs: update generated documentation.
When regeneration is required
Refresh generated docs whenever you change:
- message types in
msg.rs - response types exported in schemas
- doc comments that feed schema descriptions
metadata.json- schema generation code in
src/bin/schema.rs - the docs generation pipeline in
Makefile.toml
File Expectations
After regeneration, review and commit all relevant generated artifacts:
docs/*.mdcontracts/*/schema/*
Even if CI only reports drift on docs/*.md, schema files are still generated source artifacts in this repo and should stay in sync with the code.
Repo-Specific Notes
cargo make docsis the preferred entrypoint; it already triggers schema generation.- The docs renderer uses
@fadroma/schema,jq,awk,perl, andprettierthroughMakefile.toml. - The generated docs reflect the semantics encoded in Rust doc comments. Fix the Rust comments first, then regenerate.
© axone-protocol, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/doc-generation of axone-protocol/contracts.
Open the folder on GitHubat commit 02724f3
Compare with similar skills
Doc Generation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Doc Generation this skillaxone-protocol/contracts | 123 | — | ~590 | Automated safety check: Pass | BSD-3-Clause | |
| Nestjs Trpctrycompai/crm | 11k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Feynman Auditor0xiehnnkta/nemesis-auditor | 244 | 1 repos | ~11k | Automated safety check: Pass | MIT | |
| RadarAuditware/radar | 154 | — | ~2.1k | Automated safety check: Pass | GPL-3.0 | |
| Safe Solana BuilderFrankcastleauditor/safe-solana-builder | 145 | — | ~3.6k | Automated safety check: Pass | None | |
| Temporal Developertemporalio/skill-temporal-developer | 230 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Feynman Auditor
0xiehnnkta/nemesis-auditor
Deep business logic bug finder using the Feynman technique. An agent skill from 0xiehnnkta/nemesis-auditor.
Radar
Auditware/radar
Use radar for smart contract security analysis, AST generation, and detection template development.
Safe Solana Builder
Frankcastleauditor/safe-solana-builder
A skill your agent uses whenever the user wants to write, scaffold, or build a Solana smart contract or program from scratch.
- Official
Temporal Developer
temporalio/skill-temporal-developer
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust.
Fast Resume
angristan/fast-resume
Search local coding-agent session history and identify safe resume commands.
More from axone-protocol/contracts
All 9 skills in this repoConventional Commits
axone-protocol/contracts
Guide for writing conventional commit messages. An agent skill from axone-protocol/contracts.
Rust Testing
axone-protocol/contracts
Patterns for Rust testing in Axone CosmWasm contracts. An agent skill from axone-protocol/contracts.
Rust Quality Gates
axone-protocol/contracts
Repository quality gates for Rust and generated artifacts. An agent skill from axone-protocol/contracts.
API Design
axone-protocol/contracts
Best practices for designing CosmWasm smart contract APIs. An agent skill from axone-protocol/contracts.
API Doc Comments
axone-protocol/contracts
Guide for writing Rust doc comments that produce accurate generated contract documentation.
Cosmwasm Contract
axone-protocol/contracts
Axone contract structure and Abstract SDK patterns. An agent skill from axone-protocol/contracts.
Related
Works with
Categories
Questions about Doc Generation
What does Doc Generation do?
Guide for regenerating Axone contract schemas and rendered Markdown docs. Doc Generation is an agent skill from axone-protocol/contracts. Guide for regenerating Axone contract schemas and rendered Markdown docs.
When should I use Doc Generation?
Doc Generation fits situations like: metadata change; checking generated-doc drift; preparing documentation commits.
How do I install Doc Generation in Claude Code?
Run `npx skills add axone-protocol/contracts --skill doc-generation -a claude-code`. Or copy the skill folder (.agents/skills/doc-generation in axone-protocol/contracts) into .claude/skills/doc-generation in your project. Claude Code loads it when a task matches its description.
How do I install Doc Generation in Codex?
Run `npx skills add axone-protocol/contracts --skill doc-generation -a codex`. Or copy the skill folder (.agents/skills/doc-generation in axone-protocol/contracts) into .agents/skills/doc-generation in your project. Codex loads it when a task matches its description.
Can I use Doc Generation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add axone-protocol/contracts --skill doc-generation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doc-generation, .gemini/skills/doc-generation, .github/skills/doc-generation and .opencode/skills/doc-generation in your project.
What does Doc Generation need to run?
Going by SKILL.md and its folder, Doc Generation needs the command-line tools its instructions call (cargo and git).
Does Doc Generation access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Doc Generation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Doc Generation use?
Doc Generation is published under the BSD-3-Clause licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Doc Generation use?
About 590 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Doc Generation?
Skills that share tags, products or a category with Doc Generation: Nestjs Trpc (trycompai/crm, 11k stars), Feynman Auditor (0xiehnnkta/nemesis-auditor, 244 stars), Radar (Auditware/radar, 154 stars) and Safe Solana Builder (Frankcastleauditor/safe-solana-builder, 145 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Doc Generation?
axone-protocol (a GitHub organization) maintains it in axone-protocol/contracts, which has 123 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on September 25, 2026.
Source: axone-protocol/contracts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.