How do I install the Manage Toc skill?

Run npx skillmds@latest add pingcap/manage-toc in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Manage Toc safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Manage Toc?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Manage Toc free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Manage Toc?

pingcap (@pingcap) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Manage Toc by pingcap — Agent Skill

Name: Manage Toc
Author: pingcap

Manage Toc

Modify TOC extraction, navigation generation, or TOC-based filtering behavior in website-docs when the task changes how document navigation trees, right-side headings, or TOC membership are computed. Update the Gatsby TOC pipeline under gatsby/, keep runtime filtering logic in src/shared/ aligned, and add or adjust Jest coverage for the changed TOC behavior.

pingcap 223f1aa 2 files · 2.6 KB Updated Sep 17, 2026

File contents

Manage TOC

Overview

Use this skill when the request changes how navigation trees or heading TOCs are generated, filtered, or consumed. In this repo, TOC behavior spans build-time Gatsby code and runtime filtering helpers.

Workflow

1) Locate the TOC layer being changed

Common files:

gatsby/toc.ts
gatsby/toc-filter.ts
gatsby/toc-ignore.ts
gatsby/create-types/create-navs.ts
src/shared/filterTOC.ts
src/shared/filterRightToc.ts

Choose the layer deliberately:

Build-time extraction and nav construction in gatsby/
Runtime hiding or conditional filtering in src/shared/

2) Keep TOC membership and nav generation coherent

Current repo behavior includes:

Parsing TOC MDX into nav structures
Filtering build output based on TOC references
Mapping docs to TOC names
Special starter and essential nav handling for TiDB Cloud

If you change one of these, check whether the others must also change.

3) Prefer existing helper paths

Examples to follow:

getFilesFromTocs() and filterNodesByToc() in gatsby/toc-filter.ts
createNavs() in gatsby/create-types/create-navs.ts
filterTOC() and filterRightToc() in src/shared/

Avoid duplicating TOC parsing rules in templates or components.

4) Update tests

TOC logic in this repo already has Jest coverage under gatsby/__tests__/. When changing build-time TOC behavior, add or adjust tests near the affected code.

Typical areas:

TOC whitelist or ignore behavior
file inclusion/exclusion from TOCs
right TOC filtering conditions
nav generation for starter or essential plans

5) Validate

At minimum:

Confirm the changed TOC layer is the right one
Confirm runtime consumers still receive the expected shape
Run targeted Jest tests when applicable
Run yarn test or at least the relevant test file when feasible

Output Checklist

Report:

Which TOC build-time or runtime files changed
Whether Jest tests were updated
What navigation or filtering behavior changed
Whether yarn test or targeted tests were run

---name: manage-tocdescription: Modify TOC extraction, navigation generation, or TOC-based filtering behavior in website-docs when the task changes how document navigation trees, right-side headings, or TOC membership are computed. Update the Gatsby TOC pipeline under gatsby/, keep runtime filtering logic in src/shared/ aligned, and add or adjust Jest coverage for the changed TOC behavior.---# Manage TOC## OverviewUse this skill when the request changes how navigation trees or heading TOCs are generated, filtered, or consumed. In this repo, TOC behavior spans build-time Gatsby code and runtime filtering helpers.## Workflow### 1) Locate the TOC layer being changedCommon files:- `gatsby/toc.ts`- `gatsby/toc-filter.ts`- `gatsby/toc-ignore.ts`- `gatsby/create-types/create-navs.ts`- `src/shared/filterTOC.ts`- `src/shared/filterRightToc.ts`Choose the layer deliberately:- Build-time extraction and nav construction in `gatsby/`- Runtime hiding or conditional filtering in `src/shared/`### 2) Keep TOC membership and nav generation coherentCurrent repo behavior includes:- Parsing TOC MDX into nav structures- Filtering build output based on TOC references- Mapping docs to TOC names- Special starter and essential nav handling for TiDB CloudIf you change one of these, check whether the others must also change.### 3) Prefer existing helper pathsExamples to follow:- `getFilesFromTocs()` and `filterNodesByToc()` in `gatsby/toc-filter.ts`- `createNavs()` in `gatsby/create-types/create-navs.ts`- `filterTOC()` and `filterRightToc()` in `src/shared/`Avoid duplicating TOC parsing rules in templates or components.### 4) Update testsTOC logic in this repo already has Jest coverage under `gatsby/__tests__/`.When changing build-time TOC behavior, add or adjust tests near the affected code.Typical areas:- TOC whitelist or ignore behavior- file inclusion/exclusion from TOCs- right TOC filtering conditions- nav generation for starter or essential plans### 5) ValidateAt minimum:- Confirm the changed TOC layer is the right one- Confirm runtime consumers still receive the expected shape- Run targeted Jest tests when applicable- Run `yarn test` or at least the relevant test file when feasible## Output ChecklistReport:- Which TOC build-time or runtime files changed- Whether Jest tests were updated- What navigation or filtering behavior changed- Whether `yarn test` or targeted tests were run

Frequently asked questions