filter-docs

Generate per-file metadata manifests and apply deletions to filter documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

AI-assisted documentation filtering to keep only files useful for developers, removing clutter and preserving essential references.

Core Features & Use Cases

  • Generate per-file metadata manifest including path, size, line count, and a short preview to inform decisions.
  • Create deletions list (output/manifest/._delete.txt) to remove non-useful files and clean up repositories.
  • Iterative workflow: review the manifest, mark files to delete, then apply deletions to update the workspace.
  • Use cases include pruning legacy docs, focusing context for AI-assisted coding, and maintaining lean documentation sets.

Quick Start

Run the filter to generate a review manifest, review its suggestions, create a _delete.txt of files to remove, and re-run the filter to apply deletions.

Frequently Asked Questions about filter-docs

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

FAQPage Schema
How do I filter documentation to keep only files useful for developers?

Filtering documentation to keep useful files involves generating a per-file metadata manifest with path, size, line count, and a short preview to inform decisions. You review this manifest, mark files to delete, and apply changes to remove deselected files from your repository.

How do I prune legacy docs to focus context for AI-assisted coding?

To prune legacy docs for AI-assisted coding context, generate a review manifest to evaluate each file's usefulness, create a deletions list of non-useful files, and apply the deletions to clean up the repository and maintain a lean documentation set.

What is the process for removing clutter from repositories with mixed content?

Removing clutter from mixed-content repositories uses a two-step process: first generating an output review manifest with per-file metadata, then applying changes to remove deselected files based on a created deletions list.

Do I need jq to generate a review manifest and deletions list?

Yes, you need jq installed to generate the review manifest and deletions list. The filtering process relies on this dependency to create per-file metadata and apply the workflow to remove non-useful files from your workspace.

Can I review documentation suggestions before applying deletions to my workspace?

Yes, you can review documentation suggestions before applying deletions. The workflow is iterative: you review the generated manifest, mark files to delete in a _delete.txt file, then re-run the filter to apply the deletions and update the workspace.

What's the best way to maintain lean documentation sets in a repository?

The best way to maintain lean documentation sets is using an iterative workflow that generates per-file metadata, allows you to review and mark non-useful files for deletion, then applies those deletions to clean up the repository and preserve essential references.