Zread
ZreadAI/zread-skill
Produce and consume a wiki-style knowledge base for a code repository via the zread CLI and its on-disk output under ./.zread/wiki/.
Create or update docs/knowledge-base/ chapters in mdbook format for human-first technical documentation.
Install Docs Knowledge Base
$ npx skills add agglayer/agglayer --skill docs-knowledge-base -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agglayer/agglayer docs-knowledge-base --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/agglayer/agglayer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/docs-knowledge-base .claude/skills/docs-knowledge-base && 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 "docs-knowledge-base" agent skill from https://github.com/agglayer/agglayer/tree/main/.agents/skills/docs-knowledge-base into .claude/skills/docs-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-knowledge-base", 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/agglayer/agglayer/tree/main/.agents/skills/docs-knowledge-baseType 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 agglayer/agglayer --skill docs-knowledge-base -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agglayer/agglayer docs-knowledge-base --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agglayer/agglayer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/docs-knowledge-base .agents/skills/docs-knowledge-base && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docs-knowledge-base" agent skill from https://github.com/agglayer/agglayer/tree/main/.agents/skills/docs-knowledge-base into .agents/skills/docs-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-knowledge-base", 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 agglayer/agglayer --skill docs-knowledge-base -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agglayer/agglayer docs-knowledge-base --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agglayer/agglayer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/docs-knowledge-base .cursor/skills/docs-knowledge-base && 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 "docs-knowledge-base" agent skill from https://github.com/agglayer/agglayer/tree/main/.agents/skills/docs-knowledge-base into .cursor/skills/docs-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-knowledge-base", 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/agglayer/agglayer.git --path .agents/skills/docs-knowledge-base--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 agglayer/agglayer --skill docs-knowledge-base -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agglayer/agglayer docs-knowledge-base --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agglayer/agglayer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/docs-knowledge-base .gemini/skills/docs-knowledge-base && 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 "docs-knowledge-base" agent skill from https://github.com/agglayer/agglayer/tree/main/.agents/skills/docs-knowledge-base into .gemini/skills/docs-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-knowledge-base", 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 agglayer/agglayer docs-knowledge-baseInstalls 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 agglayer/agglayer --skill docs-knowledge-base -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agglayer/agglayer.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/docs-knowledge-base .github/skills/docs-knowledge-base && 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 "docs-knowledge-base" agent skill from https://github.com/agglayer/agglayer/tree/main/.agents/skills/docs-knowledge-base into .github/skills/docs-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-knowledge-base", 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 agglayer/agglayer --skill docs-knowledge-base -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agglayer/agglayer docs-knowledge-base --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agglayer/agglayer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/docs-knowledge-base .opencode/skills/docs-knowledge-base && 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 "docs-knowledge-base" agent skill from https://github.com/agglayer/agglayer/tree/main/.agents/skills/docs-knowledge-base into .opencode/skills/docs-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-knowledge-base", 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
docs-knowledge-base- GitHub stars
- 117
- Token cost
- ~344 tokens
- SKILL.md length
- 133 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create or update docs/knowledge-base/ chapters in mdbook format for human-first technical documentation.
- Tasks that involve Knowledge bases
- SKILL.md covers Audience and tone, mdbook structure, Chapter format and Writing conventions, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Technical documentation
What it does
Docs Knowledge Base is an agent skill from agglayer/agglayer. Create or update docs/knowledge-base/ chapters in mdbook format for human-first technical documentation.
Its SKILL.md is about 340 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 Knowledge Management, covering Knowledge bases and Technical documentation. The repository describes itself as: Rust implementation of the Agglayer. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Knowledge bases
- Tasks that involve Technical documentation
Example prompts
- “/docs-knowledge-base”
What it can do on your machine
Read from SKILL.md and the folder at commit 77667ba. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Docs Knowledge Base loads about 344 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 133 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 agglayer/agglayer at commit 77667ba, republished under its Apache-2.0 licence (© agglayer). 133 words, ~344 tokens.
Download SKILL.mdSave it as
.claude/skills/docs-knowledge-base/SKILL.md (or your agent's skills folder).- name
- docs-knowledge-base
- description
- Create or update docs/knowledge-base/ chapters in mdbook format for human-first technical documentation.
- disable-model-invocation
- true
Use this workflow when creating or editing files under docs/knowledge-base/.
Audience and tone
- Primary audience: human maintainers and contributors.
- Secondary audience: AI agents reading project documentation.
- Write concise, factual prose.
- Avoid AI-specific annotations or prompt-oriented formatting.
mdbook structure
- Keep chapter sources under
docs/knowledge-base/src/. - Keep
docs/knowledge-base/src/SUMMARY.mdas the navigation source of truth. - When adding a new chapter,
update
SUMMARY.mdin the same change.
Chapter format
- One top-level heading (
#) per chapter. - Prefer short sections with explicit responsibilities, invariants, and workflows.
- Link related terms to
glossary.md. - Link to relevant code paths when making concrete claims.
Writing conventions
- Follow semantic line breaks for prose.
- Prefer active voice and operational wording.
- Keep guidance implementation-neutral unless a path is repository-specific.
- Clearly separate facts, constraints, and recommendations.
Verification
Before finishing, build the book and report the exact command and result:
mdbook build docs/knowledge-base/© agglayer, Apache-2.0. 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/docs-knowledge-base of agglayer/agglayer.
Open the folder on GitHubat commit 77667ba
Compare with similar skills
Docs Knowledge Base 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 |
|---|---|---|---|---|---|---|
| Docs Knowledge Base this skillagglayer/agglayer | 117 | — | ~344 | Automated safety check: Pass | Apache-2.0 | |
| ZreadZreadAI/zread-skill | 177 | — | ~1.4k | Automated safety check: Pass | None | |
| New LoopAI-Builder-Club/skills | 1.3k | — | ~1.2k | Automated safety check: Notes | None | |
| Knowledge Base Builderrevfactory/harness-100 | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Tech Distilleryaofeino1/tech-distiller | 144 | — | ~1.2k | Automated safety check: Pass | None | |
| Share Session Learnings with the TeamTencent/teamai-cli | 5.1k | — | ~727 | Automated safety check: Pass | Custom licence |
Similar skills
New Loop
AI-Builder-Club/skills
Spin up a new loop (domain) in a file-based knowledge base — bootstrap the substrate if it's missing, gather the loop's charter, scaffold domains/<loop/README.md, then do ONE real test run and…
Knowledge Base Builder
revfactory/harness-100
A pipeline where an agent team builds organizational knowledge management systems.
Tech Distiller
yaofeino1/tech-distiller
Collects technical documents from URLs, files, wikis or APIs, filters them by role or technical direction, and writes a structured report on architecture, algorithms and design decisions.
Share Session Learnings with the Team
Tencent/teamai-cli
Summarizes what an AI coding session solved or discovered and publishes it to the team knowledge base with the teamai contribute command.
LLM Wiki Knowledge Graph
Egonex-AI/Understand-Anything
Detects a Karpathy-pattern LLM wiki and builds an interactive knowledge graph with entities, implicit relationships and topic clusters.
More from agglayer/agglayer
Tech E2E Tests
agglayer/agglayer
Architecture and agent rules for kurtosis-cdk E2E tests. An agent skill from agglayer/agglayer.
Verify
agglayer/agglayer
Mandatory before any commit or push. An agent skill from agglayer/agglayer.
Commit
agglayer/agglayer
Create a git commit following project conventions. An agent skill from agglayer/agglayer.
Style Prose
agglayer/agglayer
Text formatting conventions for markdown and prose files. An agent skill from agglayer/agglayer.
Session Retro
agglayer/agglayer
Review the current conversation and propose structured improvements to skills, documentation, and agent rules.
Create PR
agglayer/agglayer
Create a pull request following project conventions. An agent skill from agglayer/agglayer.
Related
Categories
Questions about Docs Knowledge Base
What does Docs Knowledge Base do?
Create or update docs/knowledge-base/ chapters in mdbook format for human-first technical documentation. Docs Knowledge Base is an agent skill from agglayer/agglayer. Create or update docs/knowledge-base/ chapters in mdbook format for human-first technical documentation.
When should I use Docs Knowledge Base?
Docs Knowledge Base fits situations like: tasks that involve Knowledge bases; tasks that involve Technical documentation.
How do I install Docs Knowledge Base in Claude Code?
Run `npx skills add agglayer/agglayer --skill docs-knowledge-base -a claude-code`. Or copy the skill folder (.agents/skills/docs-knowledge-base in agglayer/agglayer) into .claude/skills/docs-knowledge-base in your project. Claude Code loads it when a task matches its description.
How do I install Docs Knowledge Base in Codex?
Run `npx skills add agglayer/agglayer --skill docs-knowledge-base -a codex`. Or copy the skill folder (.agents/skills/docs-knowledge-base in agglayer/agglayer) into .agents/skills/docs-knowledge-base in your project. Codex loads it when a task matches its description.
Can I use Docs Knowledge Base 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 agglayer/agglayer --skill docs-knowledge-base -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-knowledge-base, .gemini/skills/docs-knowledge-base, .github/skills/docs-knowledge-base and .opencode/skills/docs-knowledge-base in your project.
What does Docs Knowledge Base need to run?
SKILL.md names no scripts, command-line tools or credentials: Docs Knowledge Base is instructions for the agent only.
Does Docs Knowledge Base access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Docs Knowledge Base 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 Docs Knowledge Base use?
Docs Knowledge Base is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Docs Knowledge Base use?
About 344 tokens (SKILL.md is roughly 1.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 Docs Knowledge Base?
Skills that share tags, products or a category with Docs Knowledge Base: Zread (ZreadAI/zread-skill, 177 stars), New Loop (AI-Builder-Club/skills, 1.3k stars), Knowledge Base Builder (revfactory/harness-100, 1.3k stars) and Tech Distiller (yaofeino1/tech-distiller, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docs Knowledge Base?
agglayer (a GitHub organization) maintains it in agglayer/agglayer, which has 117 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 6, 2026.
Source: agglayer/agglayer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.