Document Reading & Resolution Workflows

Resolve natural language document references to absolute file paths and orchestrate document operations.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/bradygaster/docx-mcp-server --skill document-reading-resolution-workflows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Document Reading & Resolution Workflows
Source: https://github.com/bradygaster/docx-mcp-server/tree/main/.squad/skills/document-reading
Command: npx skills add https://github.com/bradygaster/docx-mcp-server --skill document-reading-resolution-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables AI agents to understand and interact with documents using natural language, bridging the gap between user requests and file system operations.

Core Features & Use Cases

  • Natural Language Document Access: Resolve friendly document names (e.g., "the cloud architecture doc") to actual file paths.
  • Multi-Tool Orchestration: Seamlessly integrate document reading, searching, and metadata retrieval based on user intent.
  • Use Case: A user asks, "Summarize the RFP on my desktop." The agent uses this Skill to find the "RFP" document, read its content, and then summarize it.

Quick Start

Use the document reading skill to find and read the 'project proposal' document from your downloads folder.

Frequently Asked Questions about Document Reading & Resolution Workflows

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

FAQPage Schema
How do I read a Word document using natural language references?

This Skill resolves natural language references like "the project proposal" to absolute file paths, enabling agents to read .docx files across common directories. It supports fuzzy matching and location hints to find documents without requiring exact file names.

Can I search and summarize .docx files without knowing their exact file paths?

Yes, you can search and summarize .docx files without exact paths because the Skill resolves natural language references to absolute file paths. It orchestrates reading, searching, and summarizing operations using fuzzy matching and location hints to locate documents.

What happens when multiple Word documents match my natural language search query?

When multiple Word documents match a natural language query, the Skill performs disambiguation of multiple file matches. It uses fuzzy matching and location hints to resolve the correct absolute file path before orchestrating the requested document operation.

Does this document resolution workflow work with file formats other than .docx?

This document resolution workflow specifically processes Word documents (.docx) across common user directories. The metadata indicates support for reading, searching, summarizing, and retrieving metadata from .docx files using natural language references.

How do I use location hints to find a specific document on my desktop or downloads folder?

You provide directory context like "from my downloads folder" in your natural language request, and the Skill uses these location hints to resolve the document reference to an absolute file path. It then orchestrates retrieval operations within that specified common user directory.

What are the limitations of using natural language for file access in document workflows?

Limitations of natural language file access include potential ambiguity when fuzzy matching returns multiple files requiring disambiguation. Additionally, the workflow specifically targets Word documents (.docx) across common user directories, meaning other file formats are not supported by this resolution process.