corpus-status

Audit file counts and metadata across document corpus pipeline stages.

6|3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/carson-sweet/sweetclaude --skill corpus-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: corpus-status
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/corpus-status
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill corpus-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides visibility into the document processing pipeline, helping you identify bottlenecks, stuck tasks, or unclassified files within your project's corpus.

Core Features & Use Cases

  • Pipeline Monitoring: Displays real-time file counts across all stages (inbox, staged, working, canonical, archive).
  • Status Reporting: Identifies pipeline anomalies, such as interrupted steps or abandoned reconciliation tasks.
  • Actionable Guidance: Provides specific, context-aware recommendations for the next step in your document workflow.

Quick Start

Ask the assistant to check the current status of the corpus pipeline to see if any files require triage or reconciliation.

Frequently Asked Questions about corpus-status

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

FAQPage Schema
How do I monitor my document processing pipeline for stuck files and bottlenecks?

You can monitor your document pipeline by generating a comprehensive status report that audits file counts and metadata across directories, identifying stuck tasks or unclassified files within the corpus.

What is a corpus pipeline status report and how does it work?

A corpus pipeline status report provides visibility into document processing by monitoring file progression through consolidation, triage, reconciliation, and promotion stages to ensure data integrity and prevent execution errors.

How do I check if my project directory has unclassified files requiring triage?

You can check for unclassified files requiring triage by auditing the corpus pipeline, which displays real-time file counts across stages like inbox, staged, working, canonical, and archive to spot anomalies.

Can I validate my pipeline state against project-specific configuration files?

Yes, you can validate your pipeline state against project-specific configuration files to prevent execution errors and ensure data integrity throughout the document consolidation and promotion stages.

What should I do when my document workflow pipeline has interrupted steps or abandoned reconciliation tasks?

When your document workflow has interrupted steps or abandoned reconciliation tasks, the pipeline monitoring system provides actionable guidance and context-aware recommendations for the next step to resolve the anomaly.

Does this pipeline monitoring tool work without external dependencies?

Yes, this pipeline monitoring tool operates without external dependencies, relying solely on auditing file counts and metadata across your project directories to validate the corpus pipeline state.