deepagents

Name: deepagents
Author: langchain-ai/docs

$npx mdskill add langchain-ai/docs/deepagents

Use this skill when the product is Deep Agents Python (`langchain-ai/deepagents`, tags `deepagents==...`). For TypeScript releases from `langchain-ai/deepagentsjs`, use the `deepagentsjs` skill. For Deep Agents Code, use `deepagents-code`. Do not use this skill for Managed Deep Agents.

SKILL.md

.github/skills/deepagentsView on GitHub ↗

---
name: deepagents
description: Analyze Deep Agents Python library releases against LangChain Deep Agents docs and prepare one-feature documentation updates.
---

# Deep Agents docs release skill

## Sources of truth

- Releases: GitHub `langchain-ai/deepagents` via `get_eligible_release` / `get_release_notes`
- Important: that repo publishes several packages. For this product, only tags that start with `deepagents==` count (not `deepagents-code==`, `deepagents-acp==`, or `langchain-quickjs==`).
- Docs paths in `langchain-ai/docs`:
- `src/oss/deepagents/` library pages
- Exclude `src/oss/deepagents/code/` (Deep Agents Code is a separate product)
- Navigation for Deep Agents in `src/docs.json`
- Docs style authority: root `AGENTS.md` in `langchain-ai/docs` (read via `get_docs_file` before drafting)
- Changelog entry pages:
- `src/oss/deepagents/changelog-py.mdx`
- `src/oss/deepagents/changelog-js.mdx`

## What usually needs docs

Prioritize user-facing changes:

- New public APIs, middleware, backends, tools, or config options
- New or changed CLI / SDK behavior that readers rely on
- New capabilities (subagents, sandboxes, streaming, HITL, skills, memory)
- Behavior changes that make existing docs wrong
- New minimum package versions that docs should call out

Usually skip docs for:

- Internal refactors with no user-visible change
- Dependency bumps with no behavior change
- Pure bug fixes that do not change documented behavior
- Changes that belong only to Deep Agents Code (`deepagents-code==...` releases)

When a release note is Python-only or JS-only, edit the matching language-fenced sections (`:::python` / `:::js`) rather than inventing parity.

When unsure, open a small clarifying ticket/PR only if a reader of the current docs would be misled.

## Workflow for one Deep Agents release

The main agent must run **phase 1** through the `release-research` subagent first (diff + source investigation). This skill guides **phase 2** shipping and judgment details the subagent also uses.

1. After research returns features with `needs_docs: true`, read `/memories/agent/deepagents-releases.md` and skip any already recorded for that tag.
2. Call `get_docs_file` on `AGENTS.md` and read it in full. Then call `get_docs_file` for Deep Agents pages named in the research report. Stay out of `src/oss/deepagents/code/`.
3. For each remaining feature:
- Edit surgically from the page `get_docs_file` content, following the docs repo `AGENTS.md`. Prefer `:::python` sections; leave `:::js` alone unless the change is shared.
- Prefer updating the owning page over creating a new page. If a new page is required, also plan the `src/docs.json` navigation update.
- Load the `ship-docs-update` skill and ship that feature alone with the research report's `evidence` as `evidence_json`.
4. After shipping, append the release tag, feature name, Linear URL, and PR URL to `/memories/agent/deepagents-releases.md`.
5. Keep `/memories/agent/AGENTS.md` short: last processed Deep Agents tag and date, alongside other products.

## Memory format

Use cold memory file `/memories/agent/deepagents-releases.md`:

```md
# Deep Agents release tracking

## deepagents==0.7.24
- feature: async subagent fork mode
- linear: https://linear.app/...
- pr: https://github.com/langchain-ai/docs/pull/...
```

More from langchain-ai/docs

Skill	Description
add-docs-page	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.
deep-agents	Build batteries-included agents with planning, context management, subagent delegation, and sandboxed execution. Use for complex, multi-step tasks that need built-in capabilities.
deepagents-code	Analyze Deep Agents Code releases against LangChain Deep Agents Code docs and prepare one-feature documentation updates.
deepagentsjs	Analyze Deep Agents TypeScript releases against LangChain Deep Agents docs and prepare one-feature documentation updates for JS-facing content.
docs-code-samples	Use this skill 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 snippets. Applies when extracting code blocks from documentation, creating runnable code samples, using snippet delineators, or wiring snippet output into MDX includes.
docs-edit	Edit a docs page that already has an open pull request, or revise a page in place. Covers checking out the PR's own branch instead of cutting a new one, forked cross-repository PRs, reading the real diff, checking the edit against related pages, and the verification to run before handing off. Use when asked to edit, revise, fix, or review changes on a named PR, branch, or existing page.
docs-restructure	Restructure documentation that spans several pages. Covers splitting a page that has grown too long, moving sections between pages, retiring a page, and fixing a topic documented in two places at once. Use when asked to streamline, simplify, consolidate, or reorganize docs, or when a page review keeps producing edits without the page getting shorter.
docs-review	Review changed docs prose against Vale and the AGENTS.md style guide, reporting findings with the rule each one breaks. Use after authoring or editing a page and before committing, or to review a PR, a branch, or the current diff.
docs-team-voice	Write or revise documentation prose so it reads like the rest of this site, in the docs team's shared voice. Covers sentence length, cross-link density, how to state defaults and conditions, naming exact identifiers, and what to cut in a revision pass. Use when drafting or rewriting a page, a section, a concept overview, a how-to, a callout, or landing copy.
docs-tooling-notion	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.