Official agent skill

Add Docs Page

by langchain-ai in langchain-ai/docs

Add, move, rename, or delete a page on the LangChain docs site.

OfficialMITAuto-check passedAI & LLM Engineering

Install Add Docs Page

skills CLI
$ npx skills add langchain-ai/docs --skill add-docs-page -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install langchain-ai/docs add-docs-page --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/langchain-ai/docs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/add-docs-page .claude/skills/add-docs-page && rm -rf skills-src

Use ~/.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/

Facts

Skill name
add-docs-page
GitHub stars
426
Token cost
~2k tokens
SKILL.md length
995 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Add, move, rename, or delete a page on the LangChain docs site.

  • Works in 6 steps: Choose the source directory → Write the page → Add the navigation entry → …
  • Asked to add a new doc
  • SKILL.md covers Step 1. Choose the source…, Step 2. Write the page, Step 3. Add the navigation entry and Step 4. Add redirects for a…, plus 4 more sections
  • Calls make, uv and python3

What it does

Add Docs Page is an agent skill from langchain-ai/docs, published by the product's own GitHub organization. Add, move, rename, or delete a page on the LangChain docs site. Covers choosing the source directory, writing frontmatter, placing the entry in src/docs.json navigation, adding redirects, and verifying with the lint and broken-link gates. Use when asked to add a new doc or page, move or rename a page, put something in the nav, or add a redirect.

Its SKILL.md is about 2k 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 AI & LLM Engineering, covering Building AI agents and Static sites and blogs. It works with LangChain, LangSmith, Python and TypeScript. The repository describes itself as: Unified LangChain documentation. The licence is MIT.

When your agent uses it

  • Asked to add a new doc
  • Put something in the nav

Example prompts

  • “/add-docs-page”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Choose the source directory
  2. Write the page
  3. Add the navigation entry
  4. Add redirects for a move, rename, or deletion
  5. Verify
  6. Review the prose

What it can do on your machine

Read from SKILL.md and the folder at commit cd302e5. 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:

    • make
    • uv
    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, 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

Add Docs Page loads about 2k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 995 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~2k

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 langchain-ai/docs at commit cd302e5, republished under its MIT licence (© langchain-ai). 995 words, ~1,978 tokens.

Download SKILL.mdSave it as .claude/skills/add-docs-page/SKILL.md (or your agent's skills folder).
name
add-docs-page
description
Add, move, rename, or delete a page on the LangChain docs site. Covers choosing the source directory, writing frontmatter, placing the entry in src/docs.json navigation, adding redirects, and verifying with the lint and broken-link gates. Use when asked to add a new doc or page, move or rename a page, put something in the nav, or add a redirect.
license
MIT
metadata.author
langchain
metadata.version
1.0

Add or move a docs page

A page is not finished when the MDX file exists. It also needs a navigation entry, and a move or deletion needs a redirect. CI enforces both.

Read AGENTS.md for the navigation map, the style guide, and the frontmatter rules. This skill covers the procedure around them and does not repeat them.

Step 1. Choose the source directory

Use the "Source directory summary" table in AGENTS.md to go from subject to directory. Two traps:

  • Directory names do not match navigation names. src/langsmith/fleet/ appears as "No-code agents"; src/langsmith/managed-deep-agents*.mdx appears under Build, not under a LangSmith menu.
  • Lifecycle menus mix products. Build draws from both src/oss/ and src/langsmith/; Test, Deploy, and Monitor all draw from src/langsmith/.

Never write to build/. It is Mintlify output, regenerated by make build.

Step 2. Write the page

Required frontmatter:

yaml
---
title: Clear, concise page title
description: SEO summary with no markdown, no links, and no backticks
---

For OSS pages that differ by language, use :::python and :::js fences in one file rather than writing two files. The build pipeline emits both versions.

Step 3. Add the navigation entry

Navigation lives in src/docs.json under navigation.products. There are two products: products[0] is AGENT DEVELOPMENT LIFECYCLE (Home, Build, Test, Deploy, Monitor) and products[1] is PRODUCTS AND SETUP (LangSmith setup, LLM Gateway, No-code agents, Engine, Deep Agents Code).

Each menu item is addressed by its item key, then nests one of two ways:

  • menu[].tabs[].pages[] for most menu items.
  • menu[].dropdowns[].tabs[].pages[] for Build, which has Python and TypeScript dropdowns.

A pages array holds page-path strings and {"group": ..., "pages": [...]} objects, nested to any depth.

Three rules:

  1. A language-versioned OSS page needs two entries. Build page paths carry the language segment (oss/python/deepagents/overview and oss/javascript/deepagents/overview), so one new page means one entry in the Python dropdown and one in the TypeScript dropdown. Omitting the TypeScript entry is the most common miss.
  2. Page paths omit the src/ prefix and the file extension. src/langsmith/sandboxes.mdx is "langsmith/sandboxes".
  3. A new group leads with an index page: "pages": ["group/index", "group/page"].

Integration pages are the exception. Add them to the component's index.mdx instead, and touch docs.json only when creating a brand-new component group.

Step 4. Add redirects for a move, rename, or deletion

For a move or rename of a file that was already on main, run the repo's mover first. It rewrites cross-references across the corpus, which hand-editing misses:

bash
uv run docs mv src/langsmith/old-name.mdx src/langsmith/new-name.mdx --dry-run

Drop --dry-run once the preview looks right. Then add the redirect to the redirects array in src/docs.json:

json
{ "source": "/langsmith/old-name", "destination": "/langsmith/new-name" }

Redirect paths are site paths and start with /. A language-versioned page needs a redirect per language, plus one for the unversioned path if the old URL had one.

scripts/check_removed_pages_redirects.py runs in CI and fails the PR when a page leaves the navigation and its source file is gone with no redirect. The same script fails when docs.json names a page whose file does not exist, so a typo in a page path is caught there rather than at build time.

Step 4b. Two traps that fail silently

Extract a snippet once a block appears on three pages

AGENTS.md covers how to add a snippet. The rule for when: the same block repeated on three or more pages becomes one file under src/snippets/. A status callout duplicated across a page family means the wording change that retires it is an edit to every page in the family, and one will be missed.

Verify a new snippet reaches the build. The pipeline rewrites snippet imports to language-specific paths, so /snippets/langsmith/x.mdx becomes /snippets/python/langsmith/x.mdx in the output, and a missing target renders as nothing at all rather than as an error:

bash
ls build/snippets/python/langsmith/<name>.mdx build/snippets/javascript/langsmith/<name>.mdx
Show full SKILL.md (410 more words)Show less
Editing a heading moves its anchor

A heading's slug is derived from its text, so rewording one silently breaks every #anchor link pointing at it, including links from other pages and entries in src/docs.json. Grep before editing:

bash
grep -rn 'use-with-the-langsmith-gateway' src/ --include=*.mdx --include=*.json

Changing only capitalization is safe, because slugs are lowercased. Changing a word is not, and needs either a reworded inbound link or a redirect. <Step> and <Accordion> accept an explicit id, which is how to keep a landing spot that is no longer a heading.

Step 5. Verify

Run all three, in this order:

bash
make lint_prose FILES="src/path/to/page.mdx"
make build
make broken-links-with-anchors

When make build fails with Required uv version >=0.9.26 does not match the running version, the local uv has drifted from the one pyproject.toml expects. Run the pipeline directly rather than working around the build:

bash
PYTHONPATH="$(pwd)" .venv/bin/python -m pipeline build

make broken-links-with-anchors depends on build, so it fails the same way. Its link-check half runs on its own once the build output exists:

bash
cd build && mint broken-links --check-anchors | tee /tmp/bl.txt
cd .. && python3 scripts/filter_mint_broken_links.py --check-anchors --input /tmp/bl.txt

Read make broken-links-with-anchors output by skipping to the ⎿ lines. Those are the only real failures. A bare filename with no indented lines beneath it is an OpenAPI-generated page that exists at deploy time but not locally.

Fix every Vale finding. CI blocks on lint_prose, and its most common failure is a spaced em dash (word — word must be word—word).

Step 6. Review the prose

Once the edit is complete and before committing, invoke the docs-review skill on the files this pass changed. It runs in working-tree mode, so it needs no checkout, and it covers the style-guide rules Vale cannot see: passive voice, filler, product versus common noun capitalization, structure conventions, and link text.

Run it on finished edits only. A review of a half-written section produces findings that go stale as soon as writing resumes.

Skip this step for a change too small to have prose in it, such as a pure docs.json reorder or a redirect-only fix.

Checklist

  • File in the directory the source-directory table names, not build/.
  • Frontmatter present, description free of markdown.
  • src/docs.json entry in the right product, menu item, tab, and group.
  • Both language entries added if the page is language-versioned.
  • Index page first if a new group was created.
  • Redirect added for every moved, renamed, or deleted path.
  • Inbound #anchor links checked before any heading was reworded.
  • A block now on three or more pages extracted to src/snippets/, and its built python/ and javascript/ targets confirmed to exist.
  • make lint_prose clean, make broken-links-with-anchors shows no new ⎿ lines.
  • docs-review run on the changed files, findings addressed.

© langchain-ai, MIT. 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/add-docs-page of langchain-ai/docs.

Open the folder on GitHubat commit cd302e5

Compare with similar skills

Add Docs Page 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.

Add Docs Page compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add Docs Page this skilllangchain-ai/docs426—~2kAutomated safety check: PassMIT
Langchain Dependencieslangchain-ai/langchain-skills1.3k—~3.6kAutomated safety check: PassMIT
Langgraph Testing Evaluationsoba-labs/langchain-agent-skills107—~2.3kAutomated safety check: PassMIT
Add Example AgentGetBindu/Bindu10k—~1.1kAutomated safety check: NotesCustom licence
Failproof AI SDK IntegrationFailproofAI/failproofai5.3k—~6kAutomated safety check: PassCustom licence
LangGraph Decision Modelslangchain-ai/langchain-skills1.3k—~2.3kAutomated safety check: PassMIT

Similar skills

  • Langchain Dependencies

    langchain-ai/langchain-skills

    Official

    INVOKE THIS SKILL when setting up a new project or when asked about package versions, installation, or dependency management for LangChain, LangGraph, LangSmith, or Deep Agents.

    1.3k GitHub stars~3.6k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Langgraph Testing Evaluation

    soba-labs/langchain-agent-skills

    A skill your agent uses when you need to test or evaluate LangGraph/LangChain agents: writing unit or integration tests, generating test scaffolds, mocking LLM/tool behavior, running trajectory…

    107 GitHub stars~2.3k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed
  • Add Example Agent

    GetBindu/Bindu

    Add a new self-contained example agent under examples/. An agent skill from GetBindu/Bindu.

    10k GitHub stars~1.1k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check: notes
  • Failproof AI SDK Integration

    FailproofAI/failproofai

    Helps instrument a custom Python or TypeScript agent to record events for Failproof AI, verify what gets written, and run an evaluator worker that scores the runs.

    5.3k GitHub stars~6k tokensUpdated 3 days ago
    AI & LLM EngineeringAuto-check passed
  • LangGraph Decision Models

    langchain-ai/langchain-skills

    Official

    Routes LangGraph agents with typed decision models that return probabilities, and finds LLM calls that only exist to produce a routing decision.

    1.3k GitHub stars~2.3k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Tool Design

    agentailor/fullstack-langgraph-nextjs-agent

    Design and verify tools that AI agents can actually use — for any framework or language (MCP servers, LangChain/LangGraph, function-calling, raw JSON schema; TypeScript, Python, or otherwise).

    132 GitHub stars~3.2k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed

More from langchain-ai/docs

All 17 skills in this repo
  • Deep Agents

    langchain-ai/docs

    Official

    Build batteries-included agents with planning, context management, subagent delegation, and sandboxed execution.

    426 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Docs Code Samples

    langchain-ai/docs

    Official

    A skill your agent uses when migrating inline code samples from LangChain docs (MDX files) into external, testable code files that are extracted by this repo’s snippet scripts and used as Mintlify…

    426 GitHub stars~4.6k tokensUpdated today
    Auto-check passed
  • Docs Edit

    langchain-ai/docs

    Official

    Edit a docs page that already has an open pull request, or revise a page in place.

    426 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Docs Restructure

    langchain-ai/docs

    Official

    Restructure documentation that spans several pages. An agent skill from langchain-ai/docs.

    426 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Docs Team Voice

    langchain-ai/docs

    Official

    Write or revise documentation prose so it reads like the rest of this site, in the docs team's shared voice.

    426 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Langchain

    langchain-ai/docs

    Official

    Build agents with a prebuilt architecture and integrations for any model or tool.

    426 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Questions about Add Docs Page

What does Add Docs Page do?

Add, move, rename, or delete a page on the LangChain docs site. Add Docs Page is an agent skill from langchain-ai/docs, published by the product's own GitHub organization. Add, move, rename, or delete a page on the LangChain docs site.

When should I use Add Docs Page?

Add Docs Page fits situations like: asked to add a new doc; put something in the nav.

How do I install Add Docs Page in Claude Code?

Run `npx skills add langchain-ai/docs --skill add-docs-page -a claude-code`. Or copy the skill folder (.agents/skills/add-docs-page in langchain-ai/docs) into .claude/skills/add-docs-page in your project. Claude Code loads it when a task matches its description.

How do I install Add Docs Page in Codex?

Run `npx skills add langchain-ai/docs --skill add-docs-page -a codex`. Or copy the skill folder (.agents/skills/add-docs-page in langchain-ai/docs) into .agents/skills/add-docs-page in your project. Codex loads it when a task matches its description.

Can I use Add Docs Page 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 langchain-ai/docs --skill add-docs-page -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-docs-page, .gemini/skills/add-docs-page, .github/skills/add-docs-page and .opencode/skills/add-docs-page in your project.

What does Add Docs Page need to run?

Going by SKILL.md and its folder, Add Docs Page needs the command-line tools its instructions call (make, uv and python3). Our summary lists: Python 3.

Does Add Docs Page access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Add Docs Page 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 Add Docs Page use?

Add Docs Page is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Add Docs Page use?

About 2k tokens (SKILL.md is roughly 7.9k 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 Add Docs Page?

Skills that share tags, products or a category with Add Docs Page: Langchain Dependencies (langchain-ai/langchain-skills, 1.3k stars), Langgraph Testing Evaluation (soba-labs/langchain-agent-skills, 107 stars), Add Example Agent (GetBindu/Bindu, 10k stars) and Failproof AI SDK Integration (FailproofAI/failproofai, 5.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Docs Page?

langchain-ai (a GitHub organization, an official publisher) maintains it in langchain-ai/docs, which has 426 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 10, 2026.

Source: langchain-ai/docs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.