build-my-context7

Downloads and filters remote manifests to assemble local Context7 documentation references.

7|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/jasonz-ncc42/local-context7 --skill build-my-context7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-my-context7
Source: https://github.com/jasonz-ncc42/local-context7/tree/main/.claude/skills/build-my-context7
Command: npx skills add https://github.com/jasonz-ncc42/local-context7 --skill build-my-context7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates building a local Context7 documentation reference by downloading and filtering docs from manifests, enabling faster setup and updates.

Core Features & Use Cases

  • Download and filter docs from manifests to create a focused developer docs context.
  • Support per-manifest or all-manifests processing with deterministic workflow and parallel sub-agent execution.
  • Output summary and store results under the output/ directory for easy reuse.

Quick Start

Run the slash command /build-my-context7 to process all manifests, or /build-my-context7 zod-docs to process a specific manifest.

Frequently Asked Questions about build-my-context7

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate assembling local documentation for AI coding workflows?

Automating local documentation assembly for AI coding involves downloading and filtering remote manifests to create a focused developer docs context. This Skill executes a deterministic, multi-phase workflow with argument validation, manifest discovery, and parallel processing to build coherent references.

Can I filter specific manifests instead of processing all documentation sources?

Yes, you can filter specific manifests by passing the manifest name as an argument, such as targeting individual sources like zod-docs. Alternatively, running the command without arguments processes all available manifests to build the complete local context.

What is the best way to set up local Context7 references for multiple manifest sources?

Setting up local Context7 references is best handled by a deterministic workflow that applies across multiple manifest sources. It uses a manifest-processor sub-agent for parallel processing, downloads remote data, filters it, and outputs a final summary report for reuse.

Do I need any external dependencies to build local docs from manifests?

No external dependencies are required to build local docs from manifests. The Skill operates independently using its internal multi-phase workflow and sub-agent processing to download, filter, and store results under the output directory without prerequisite packages.

Where are assembled documentation contexts stored after processing manifests?

Assembled documentation contexts are stored under the output/ directory after processing manifests. This ensures easy reuse of the filtered developer docs context, and the workflow generates a final summary report detailing the results of the download and filtering operations.