Inventory, read, and synthesize source documents from .project/input/ folders.
npx skills add https://github.com/bbolek-ap/new-ai-native --skill read-documents
Please help me install this Agent Skill. Skill: read-documents Source: https://github.com/bbolek-ap/new-ai-native/tree/main/.claude/skills/read-documents Command: npx skills add https://github.com/bbolek-ap/new-ai-native --skill read-documents
Inventory, read, and synthesize source documents from the .project/input/ folder before producing output. This skill standardizes the folder structure, document conventions, and citation formats used across all agents, ensuring a coherent knowledge base.
Scan the relevant folders, read all potentially related documents, and apply per-type extraction rules to build a consolidated knowledge digest before acting.
High-intent search queries and answers about installing and using this skill.
To inventory and synthesize project documents, scan the .project/input/ folders and apply per-type extraction rules to meetings, formal documents, and emails to surface decisions and context. This produces a consolidated knowledge digest with consistent citations.
Cross-referencing source documents to find conflicts involves scanning the .project/input/ directory, reading related files, and applying extraction rules to flag inconsistencies, gaps, and supersessions across meetings, formal documents, and emails.
Standardizing citation formats across agents requires defining folder structures, naming conventions, and cross-document citation workflows before producing output. This ensures all extracted items maintain a consistent reference system within a coherent knowledge base.
Yes, you can extract requirements and decisions from meetings and emails by scanning the .project/input/ subfolders and applying per-document-type extraction rules to surface directives, context, and formal requirements into a single digest.
Organizing input documents for agent processing requires a .project/input/ folder structure containing separate subfolders for meetings, formal documents, and emails. This standardizes the directory layout before applying extraction rules and generating citations.
You should scan and read source documents before generating any project output to ensure all decisions, requirements, and context are extracted and cross-referenced. Building a consolidated knowledge digest first prevents conflicting or incomplete outputs.
erencodingCreate standardized document folder structures with project and practice subdirectories.
m13vGenerate formatted Google Docs reports from Google Sheets data with email permissions.
udecodeDocument and standardize a project's tech stack for consistent development practices.
rysweetExtract action items, decisions, and follow-ups from meeting notes.
