source-document-validator

Name: source-document-validator
Availability: InStock
Author: fredrikc3-sketch

Validates readability and extractability of project requirement documents, flagging encrypted or corrupt files.

23|11|Updated Feb 20, 2026

Search Tags:#readability #compliance #PDF #file extraction #corruption #document validation

Ready to run

npx skills add https://github.com/fredrikc3-sketch/VibeConfigStarterKit --skill source-document-validator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-document-validator
Source: https://github.com/fredrikc3-sketch/VibeConfigStarterKit/tree/main/skills/source-document-validator
Command: npx skills add https://github.com/fredrikc3-sketch/VibeConfigStarterKit --skill source-document-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It prevents the use of incomplete or corrupted source documents by validating that each file can be successfully read and accurately extracted, safeguarding subsequent analysis steps.

Core Features & Use Cases

Document Validation: Checks the readability, extractability, and integrity of files in the Requirements folder.
Risk Detection: Identifies encrypted, corrupt, unsupported, or image-based PDFs needing OCR, and flags files with potential sensitivity or PII.
Use Case: Before starting requirements analysis, verify that all documents are accessible and complete to avoid wasting time on unreadable sources.

Quick Start

Run source-document-validator to confirm all requirement files can be read and properly extracted from.

Frequently Asked Questions about source-document-validator

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

FAQPage Schema

How do I check if a PDF is corrupt or encrypted before processing?▼

Document validation checks PDF readability and extractability to detect encryption, corruption, and unsupported formats before you process them, providing remediation guidance to fix unreadable files.

How do I validate project requirements documents for file extraction errors?▼

Validating project requirements documents involves checking each file for readability, extractability, and integrity to ensure complete access. This process flags encrypted, corrupt, or image-based PDFs needing OCR before analysis begins.

Can I detect image-based PDFs that need OCR during document validation?▼

Yes, document validation can detect image-based PDFs needing OCR. It identifies files lacking extractable text and flags them so you can run optical character recognition before starting requirements analysis.

Does source-document-validator work for compliance and PII detection workflows?▼

Yes, source-document-validator works for compliance workflows by flagging files with potential sensitivity or PII. It ensures documents meet readability and extractability standards required for secure, compliant processing.

What is the best way to prevent unreadable source documents from breaking analysis?▼

The best way to prevent unreadable source documents from breaking analysis is to run document validation beforehand. This verifies file integrity and extractability, stopping corrupted or unsupported formats from entering your workflow.