material-organizer

Material Organizer

Organize only the materials the user has already provided or explicitly pointed to. The job is to make messy inputs easier to scan, reuse, archive, or continue from later while preserving source traceability.

When To Use

• The user provides 2 or more materials and asks to organize, extract, classify, archive, generate research notes, or produce an organizing report.
• The user provides a local directory path and asks to scan files, analyze categories, identify duplicate/abnormal files, or generate archiving suggestions.
• The user wants mixed materials converted into a searchable Markdown/HTML/table-like structure: table of contents, sources, tags, keyword index, and exception log.
• The user wants webpages, notes, meeting minutes, emails, conversations, or research fragments turned into knowledge cards, entity relationships, tags, verification gaps, and review prompts.

Do not use for:

• Close reading of one article, standalone paper reading, or broad evidence synthesis.
• Translation, writing polish, resume optimization, or course knowledge-framework design.
• Searching for new materials unless the user explicitly provides search results or links to organize.
• Writing into an external knowledge base, editing a note vault, or changing files inside a directory without a confirmed plan.

How To Call

1. Identify the mode:

• content_organizing: links, PDFs, Word files, images, text snippets, notes, or mixed source materials.
• knowledge_flow: user-provided materials that should become reusable knowledge cards, entity links, source records, verification gaps, and review prompts.
• directory_organizing: a local folder that needs scanning, classification, deduplication review, or cleanup planning.

1. Decide whether clarification is needed:

• 1-5 materials: organize directly with sensible defaults and state the classification method and detail level.
• 6-30 materials: confirm classification method, detail level, report format, and whether to save files.
• More than 30 materials: ask the user to submit batches or split by topic/folder.

1. Extract content:

• Use the extraction rules for source fields, core points, excerpts, tags, evidence levels, and exception handling.
• Preserve filenames, URLs, source titles, authors/organizations, dates, and access issues.
• Mark unreadable or low-confidence inputs instead of filling gaps.

1. Build knowledge cards when needed:

• Use the knowledge-flow guide when the user asks for knowledge-base notes, personal knowledge flow, knowledge cards, entity relationships, review prompts, or reusable long-term notes.
• Keep each knowledge card traceable to original material. Mark unsourced content as source not provided.
• Suggest save locations or filenames only as recommendations unless the user has confirmed actual writing.

1. Deduplicate and classify:

• Use the deduplication strategy to merge duplicates only when the source relationship is clear.
• Use the classification rules; user-specified dimensions come first.
• Keep conflicting materials separate and log contradictions.

1. Handle directories safely:

• First scan and report the directory. Do not move, rename, delete, or overwrite files during the first pass.
• Use the directory-organizing guide to identify type distribution, possible duplicates, sensitive files, and cleanup levels.
• For any operation that changes files or generates an executable organizing script, show the exact plan and obtain explicit confirmation.

1. Return the report:

• Use the output schema.
• Write files only when the user explicitly requests or confirms saving.
• If saving, return the output path and note what was not processed.

Return Format

Content organizing report:

**Organizing Scope**
- Material count:
- Classification method:
- Detail level:
- Processing basis:

**Extraction Overview**
- Successfully processed:
- Access failures:
- Deduplicated/merged:
- Topic categories:

**Topic Directory**
1. ...

**Entry Details**
...

**Keyword Index**
...

**Exception Log**
...

Knowledge flow report:

**Knowledge Flow Scope**
- Material count:
- Processing basis:
- Intended destination:

**Knowledge Cards**
...

**Entity Links**
...

**Source Records**
...

**Verification Gaps**
...

**Review Prompts**
...

Directory organizing report:

**Directory Overview**
- Path:
- File/directory count:
- Type distribution:
- Possible duplicates:
- Abnormal files:

**Suggested Classification**
...

**Cleanup Suggestions**
...

**Important Files Requiring Confirmation**
...

**Next Step**
...

If a material item cannot be read, preserve the source and record the exception. Do not fill missing content with guesses.

External Dependencies

• The current environment must be able to read user-provided URLs, PDFs, Word documents, images, text, or local paths. If a file type cannot be read, ask the user to paste the text or provide the material in another format.
• Directory organizing requires read permission for the local path provided by the user.
• Generating HTML, Excel, or other file formats requires the current environment to support the corresponding file writing and format generation.
• No fixed third-party package, account, database, long-term memory, or background service is required.

Limits And Known Issues

• Do not proactively search for new materials; organize only the inputs already provided by the user.
• Do not save files by default, move files by default, or delete duplicate files by default.
• Do not treat a directory report as permission to execute cleanup.
• OCR, scanned PDFs, and complex chart recognition may be unstable; low-confidence content must be marked and…