file-document

Store documents, emails, and text with provenance and entity linking.

283|44|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/kbanc85/claudia --skill file-document
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-document
Source: https://github.com/kbanc85/claudia/tree/main/template-v2/.claude/skills/file-document
Command: npx skills add https://github.com/kbanc85/claudia --skill file-document

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and preserve important documents, emails, and notes for future reference, with clear provenance and entity linking.

Core Features & Use Cases

  • Centralized storage for documents, emails, transcripts, and notes with automatic provenance tracking.
  • Entity linking to people, organizations, and projects to surface related context.
  • Fast, searchable access to saved content for later review or decision making.

Quick Start

Save a document you need to reference again by telling your assistant to store this for later retrieval.

Frequently Asked Questions about file-document

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

FAQPage Schema
How do I store documents and emails with provenance for later retrieval?

Store documents with provenance by pasting content, uploading files, or forwarding emails to memory. The system preserves full content and applies automatic entity linking to people, organizations, and projects for fast retrieval and traceable history.

What is entity linking and how does it help with document search?

Entity linking connects stored documents, notes, and emails to specific people, organizations, and projects. This automatically surfaces related context during search, making it easier to find and recall relevant information for decision making and auditing.

Can I use this for ad-hoc capture workflows with pasted text and files?

Yes, ad-hoc capture workflows are fully supported for pasting text, uploading files, or forwarding emails. The system requires explicit linking to entities and automatically preserves full content with traceable history for future recall and auditing.

What's the best way to keep a traceable history of captured notes and transcripts?

Keep a traceable history by storing notes and transcripts with automatic provenance tracking. This preserves the full content and its origin, supporting fast search, auditing, and recall when you need to reference past decisions or context.

Do I need to manually link documents to projects and people before storing them?

Yes, explicit linking to entities like people, organizations, and projects is required when storing a document. This ensures the content is correctly associated with related context for fast, searchable access and accurate auditing later.