data-import

Classify project documents from an input directory into source/ and org-data/ repositories.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/danishi/arcadia --skill data-import
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-import
Source: https://github.com/danishi/arcadia/tree/main/.claude/skills/data-import
Command: npx skills add https://github.com/danishi/arcadia --skill data-import

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of incorporating new project documents into the correct directories, ensuring all project information is organized and accessible.

Core Features & Use Cases

  • Automatic File Classification: Intelligently sorts files from an input directory into either project-specific (source/) or organization-wide (org-data/) locations based on predefined rules.
  • Catalog Updates: Automatically updates reference catalogs like docs-catalog.md and indexes for organizational data.
  • Use Case: After receiving a new set of technical specifications and meeting minutes via email, place them in the input/ folder. The data-import Skill will automatically categorize and move them to source/rfp_reference/specs/ and source/minutes/ respectively, updating relevant project documentation.

Quick Start

Use the data-import skill to automatically classify and move all files from the input directory.

Frequently Asked Questions about data-import

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

FAQPage Schema
How do I automatically organize project documents from an input directory?

Automatically organizing project documents involves classifying files from an input directory into structured repositories. The data-import skill sorts files into project-specific 'source/' or organizational 'org-data/' directories while updating catalogs and logs.

How does automatic file classification separate project data from organizational assets?

Automatic file classification separates project data from organizational assets using predefined rules to route files. It intelligently directs documents to 'source/' for project-specific information or 'org-data/' for organization-wide assets, updating reference catalogs accordingly.

Can I preview file movements before automatically importing documents to project repositories?

Yes, you can preview file movements before importing documents using the dry-run capability. This feature allows you to see how files will be categorized and moved into 'source/' or 'org-data/' directories before any actual changes are made.

How do I handle duplicate detection and versioning when categorizing project files?

Handling duplicate detection and versioning during project file categorization is managed internally by the ingestion process. The skill checks for duplicate files and considers versioning rules before sorting documents into the structured project repositories.

What is the best way to ingest technical specifications and meeting minutes into project repositories?

The best way to ingest technical specifications and meeting minutes is placing them in an 'input/' folder for automatic categorization. The skill moves specs to 'source/rfp_reference/specs/' and minutes to 'source/minutes/', updating relevant project documentation.

How do catalog updates work when importing new files into project directories?

Catalog updates occur automatically during file import by modifying reference files like 'docs-catalog.md'. As documents are sorted into 'source/' or 'org-data/' locations, the skill updates relevant indexes and logs to reflect the newly ingested assets.