New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Docs Tooling Notion

by langchain-ai in langchain-ai/docs

Document new or changed docs-team tooling on the Notion tooling pages.

OfficialMITAuto-check passedDevOps & Cloud

Install Docs Tooling Notion

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

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

GitHub CLI
$ gh skill install langchain-ai/docs docs-tooling-notion --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/docs-tooling-notion .claude/skills/docs-tooling-notion && 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
docs-tooling-notion
GitHub stars
426
Token cost
~1.7k tokens
SKILL.md length
856 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Document new or changed docs-team tooling on the Notion tooling pages.

  • Works in 6 steps: Route the topic → Check whether it belongs in Notion at all → Write it → …
  • Tasks that involve Background jobs
  • SKILL.md covers Rule one: one home per topic, Step 1. Route the topic, Step 2. Check whether it… and Step 3. Write it, plus 3 more sections
  • Calls git

What it does

Docs Tooling Notion is an agent skill from langchain-ai/docs, published by the product's own GitHub organization. Document new or changed docs-team tooling on the Notion tooling pages. Decides which of the five pages owns the topic, what belongs in the repo instead of Notion, and how to edit safely through the Notion MCP server. Invoke it whenever work adds or changes a script under scripts/, a GitHub Actions workflow, a Makefile target, a PR check, a scheduled job, an agent, a skill, or an MCP server, and invoke it before handing off that pull request. Shipping tooling is itself the trigger, so do not wait to be asked to…

Its SKILL.md is about 1.7k 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 DevOps & Cloud, covering Background jobs, CI/CD and MCP servers. It works with Notion, Model Context Protocol, LangSmith and LangChain. The repository describes itself as: Unified LangChain documentation. The licence is MIT.

When your agent uses it

  • Tasks that involve Background jobs
  • Tasks that involve CI/CD
  • Tasks that involve MCP servers

Example prompts

  • “/docs-tooling-notion”

Workflow steps

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

  1. Route the topic
  2. Check whether it belongs in Notion at all
  3. Write it
  4. Edit safely
  5. Add a row to the Detailed list
  6. Close the loop

What it can do on your machine

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

    • git

    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

Docs Tooling Notion loads about 1.7k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 856 words of instructions outside code blocks.

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

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 be3028f, republished under its MIT licence (© langchain-ai). 856 words, ~1,684 tokens.

Download SKILL.mdSave it as .claude/skills/docs-tooling-notion/SKILL.md (or your agent's skills folder).
name
docs-tooling-notion
description
Document new or changed docs-team tooling on the Notion tooling pages. Decides which of the five pages owns the topic, what belongs in the repo instead of Notion, and how to edit safely through the Notion MCP server. Invoke it whenever work adds or changes a script under scripts/, a GitHub Actions workflow, a Makefile target, a PR check, a scheduled job, an agent, a skill, or an MCP server, and invoke it before handing off that pull request. Shipping tooling is itself the trigger, so do not wait to be asked to document it and do not wait for the PR to merge.
license
MIT
metadata.author
langchain
metadata.version
1.0

Document tooling in Notion

The docs team's internal tooling documentation is five Notion pages under Docs Team. This skill routes a change to the one page that owns it, then edits that page without tripping the known Notion failure modes.

Requires the Notion MCP server (notion-fetch, notion-update-page).

Rule one: one home per topic

Every topic lives on exactly one page. Duplicates drift, and drift is worse than a long page. Before writing anything, search the other four pages for the topic. If it already appears somewhere, update it there instead of adding a second copy.

Step 1. Route the topic

PageIDOwns
Docs tooling and agents3ca808527b178153839bff0f2831914cParent directory. Page table, "Owned elsewhere" list, quick-answers FAQ.
Docs tech stack30c808527b178073876af57f7d87d8caThe production site only: fencing, src versus build, build pipeline, navigation, integration docs.
Local setup and quality gates3c8808527b1781dcbaf5d04834a843bfmise and prek setup, the docs and mint CLIs, Vale, git hooks, broken-link triage, the CI matrix, preview deployments, publishing.
Docs automation and agents3c8808527b17815b81cbf92896b5c3eeScheduled workflows and their cron times, the changelog agents, the #ask-docs intake agent, tracked skills, agent-instruction files, MCP servers.
Reference docs3c9808527b1781858ebbe92914b02970The three LangSmith OpenAPI sources, reference.langchain.com, the @[ClassName] link map.

Most new tooling lands on Docs automation and agents (a workflow, script, agent, skill, or MCP server) or Local setup and quality gates (anything a contributor runs on their own machine or that gates a PR).

The changelog system is not owned by these pages. LangSmith release notes owns fragments, the fragment schema, and both pipelines. Link to it; do not re-explain it. These pages keep only the runbook: deployment IDs, HTTP routes, required environment variables, and recovery paths.

Step 2. Check whether it belongs in Notion at all

Do not write a Notion page for something the repo already documents where people find it. Deliberately excluded: IDE_SETUP.md, .github/brand-guidelines.md, .github/pull_request_template.md, .github/CONTRIBUTING.md, the issue templates, and the navigation map, which lives only in AGENTS.md because the Notion copy went stale once already.

Skills are the same: a skill is its own authoritative reference. Name it on the Notion page, say what it covers and the one or two facts a reader needs in order to decide whether to open it, and stop there.

Untracked tooling is not team infrastructure. Anything under a gitignored path is personal tooling and does not go on these pages.

Step 3. Write it

Follow the docs-team-voice skill. Do not restate its rules here. The three that get missed most often on Notion pages: no first person, no spaced em dashes, and definition lists written as - **Term**: Explanation. with the colon outside the bold and a period at the end.

Open a section with a one-sentence statement of what the thing is, then what it enables, then the procedure. Close a substantial page with ## See also.

Show full SKILL.md (390 more words)Show less

Step 4. Edit safely

Fetch the page with notion-fetch before every edit. Then use notion-update-page with command: "update_content" and narrow content_updates pairs rather than rewriting the page.

Five failure modes, each of which has already cost a debugging cycle:

  • old_str must match the stored indentation exactly. Tables are stored with no leading tabs; callouts do use tabs. A mismatch fails with an indentation hint.
  • Never use replace_content on a page holding an uploaded image. The fetched image URL is a short-lived signed S3 link, and rewriting the page body can break the image.
  • A timed-out or async update may already have applied. Updates default to allow_async: true. Fetch the page and verify before retrying anything that appeared to fail, otherwise the retry duplicates the block.
  • Bold that contains inline code mid-sentence renders as stray asterisks. Bold wrapping code entirely is fine. Reword so the two do not collide.
  • In-page anchor links do not resolve. Notion addresses blocks by ID, not by heading slug. Reference sections by name in prose.

Step 5. Add a row to the Detailed list

The parent page embeds a Detailed list database (collection://3ce80852-7b17-8004-8735-000bc758a8cd) holding one row per piece of tooling. Prose on a page is where someone reads about a thing; this database is where they find that it exists at all. It is easy to miss, because the parent page renders it as a single inline block.

Every new workflow, script, skill, agent, MCP server, or git hook gets a row. The schema is Title, Description, Docs page (the URL of the page that explains it), Source (the repo paths it lives at), and Type, a select over GH Actions (scheduled), GH Actions (PR/CI), Fleet agent, Deep agent, External bot, Skill, MCP server, Manual script, and Git hook.

Query it with notion-query-data-sources before adding, so a rename becomes an update rather than a duplicate row. Renaming or moving a file means updating Source here too, not only in the prose: four rows still pointed at a skills directory that had been renamed months earlier, and every one of them read as plausible.

Step 6. Close the loop

Update the parent page's page table when a page's scope changes, and repoint any ## See also entry that is now wrong. Report which page was edited and what was deliberately left out, so the routing decision is reviewable.

© 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/docs-tooling-notion of langchain-ai/docs.

Open the folder on GitHubat commit be3028f

Compare with similar skills

Docs Tooling Notion 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.

Docs Tooling Notion compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Docs Tooling Notion this skilllangchain-ai/docs426—~1.7kAutomated safety check: PassMIT
Code Reviewoaslananka/kicad-mcp-pro120—~3.9kAutomated safety check: PassMIT
Claude Docs Consultantcentminmod/my-claude-code-setup2.7k—~959Automated safety check: PassMIT
ReleaseWebMCP-org/npm-packages104—~1.6kAutomated safety check: NotesMIT
Publishingadeze/raindrop-mcp188—~398Automated safety check: PassMIT
MCP Server Trello Releasedelorenj/mcp-server-trello445—~3.5kAutomated safety check: PassMIT

Similar skills

  • Code Review

    oaslananka/kicad-mcp-pro

    A skill your agent uses for GitHub Copilot pull request and code reviews in oaslananka/kicad-mcp-pro.

    120 GitHub stars~3.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Claude Docs Consultant

    centminmod/my-claude-code-setup

    Consult official Claude Code documentation from code.claude.com using selective fetching.

    2.7k GitHub stars~959 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Release

    WebMCP-org/npm-packages

    Release the @mcp-b monorepo with Changesets and pnpm, using npm trusted publishing in GitHub Actions.

    104 GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check: notes

  • Publishing

    adeze/raindrop-mcp

    Publishing and release workflow with semantic-release and GitHub Actions

    188 GitHub stars~398 tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • MCP Server Trello Release

    delorenj/mcp-server-trello

    Canonical build → release → tag → publish procedure for the @delorenj/mcp-server-trello repo.

    445 GitHub stars~3.5k tokensUpdated 16 days ago
    DevelopmentAuto-check passed

  • Example Harness

    ruvnet/metaharness

    Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot…

    694 GitHub stars~735 tokensUpdated today
    DevOps & CloudAuto-check passed

More from langchain-ai/docs

All 17 skills in this repo

  • Add Docs Page

    langchain-ai/docs

    Official

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

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

  • 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

Works with

Categories

Questions about Docs Tooling Notion

What does Docs Tooling Notion do?

Document new or changed docs-team tooling on the Notion tooling pages. Docs Tooling Notion is an agent skill from langchain-ai/docs, published by the product's own GitHub organization. Document new or changed docs-team tooling on the Notion tooling pages.

When should I use Docs Tooling Notion?

Docs Tooling Notion fits situations like: tasks that involve Background jobs; tasks that involve CI/CD; tasks that involve MCP servers.

How do I install Docs Tooling Notion in Claude Code?

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

How do I install Docs Tooling Notion in Codex?

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

Can I use Docs Tooling Notion 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 docs-tooling-notion -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-tooling-notion, .gemini/skills/docs-tooling-notion, .github/skills/docs-tooling-notion and .opencode/skills/docs-tooling-notion in your project.

What does Docs Tooling Notion need to run?

Going by SKILL.md and its folder, Docs Tooling Notion needs the command-line tools its instructions call (git).

Does Docs Tooling Notion 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 Docs Tooling Notion 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 Tooling Notion use?

Docs Tooling Notion 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 Docs Tooling Notion use?

About 1.7k tokens (SKILL.md is roughly 6.7k 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 Tooling Notion?

Skills that share tags, products or a category with Docs Tooling Notion: Code Review (oaslananka/kicad-mcp-pro, 120 stars), Claude Docs Consultant (centminmod/my-claude-code-setup, 2.7k stars), Release (WebMCP-org/npm-packages, 104 stars) and Publishing (adeze/raindrop-mcp, 188 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docs Tooling Notion?

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 9, 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.