manifest

Generate and maintain a machine-readable metadata block in CLAUDE.md from pyproject.toml and the file tree.

Updated May 23, 2026
One-click install
npx skills add https://github.com/The-Interdependency/skill-lib --skill manifest-the-interdependency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manifest
Source: https://github.com/The-Interdependency/skill-lib/tree/main/manifest
Command: npx skills add https://github.com/The-Interdependency/skill-lib --skill manifest-the-interdependency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically generates a living spec that captures the observable facts of a repository, ensuring consistency and up-to-date information without manual editing.

Core Features & Use Cases

  • Repo Facts Generation: Automatically derives package metadata, dependencies, layout, and CI workflows from pyproject.toml and the file tree.
  • Block Integration: Splices the generated facts into a machine-owned block within CLAUDE.md for consistent documentation.
  • CI Enforcement: Includes a CI check to fail builds if the CLAUDE.md block drifts from the source facts.
  • Use Case: For developers setting up or maintaining a CLAUDE.md document, ensuring its factual half is always accurate and up-to-date.

Quick Start

Use the manifest skill to insert or refresh the generated block in your CLAUDE.md document.

Frequently Asked Questions about manifest

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

FAQPage Schema
How do I automatically generate repository metadata for CLAUDE.md from pyproject.toml?

You can automatically generate repository metadata for CLAUDE.md by using a tool that parses pyproject.toml and the file tree to derive package facts, dependencies, and CI workflows. This ensures the documentation block stays up-to-date without manual editing.

What is a living spec for repository facts and how does it prevent documentation drift?

A living spec for repository facts is a machine-authored, machine-readable block in CLAUDE.md containing derived metadata from pyproject.toml. It prevents documentation drift by using CI checks that fail builds if the generated block diverges from the actual source facts.

How do I enforce CI checks to keep CLAUDE.md metadata in sync with source files?

To enforce CI checks that keep CLAUDE.md metadata in sync with source files, you configure a validation script that compares the machine-owned block against facts derived from pyproject.toml and the file tree. The CI pipeline fails the build if any drift is detected.

Do I need Python 3.11 or higher to parse pyproject.toml for repository documentation?

Yes, you need Python 3.11 or higher to parse pyproject.toml for repository documentation because the process relies on the built-in tomllib module to read the configuration file and manipulate text blocks in CLAUDE.md.

Can I integrate dependency management and code documentation layout into a single automated spec?

Yes, you can integrate dependency management and code documentation layout into a single automated spec. The process derives package metadata, dependencies, and file tree layout from pyproject.toml, splicing them into a unified machine-owned block within CLAUDE.md.

What are the limitations of using a machine-authored block for repo metadata in CLAUDE.md?

The main limitation of using a machine-authored block for repo metadata in CLAUDE.md is that it is strictly machine-owned, meaning manual edits to that specific block are overwritten. It also requires Python 3.11+ and a valid pyproject.toml to function correctly.