url-or-path

Import URL or Path

You are executing the /import:url-or-path command. Import documentation from a URL or local path.

Arguments

• $ARGUMENTS - URL (https://...) or local file/directory path

Dynamic Folder Structure

All imports go to mabi-import/ with intelligent substructure:

Documentation Sites (detected by Context7 or docs.* domain)

mabi-import/{library}/{version}/
  datahub.md
  data-importer.md

Example: https://docs.pimcore.com/platform/Data_Importer/ (version 2025.4) -> mabi-import/pimcore/v2025.4/data-importer.md

Regular Websites

mabi-import/website/{domain}/
  {page-name}.md

Example: https://example.com/api/docs -> mabi-import/website/example.com/api-docs.md

Local Files

mabi-import/local/{project-or-context}/
  {filename}

Determine context from:

• Parent directory name (if meaningful, not generic like "Downloads")
• File content (check for project name in headers)
• Ask user if unclear

Example: /home/user/projects/myapp/docs/config.md -> mabi-import/local/myapp/config.md

Process

1. Determine Source Type

Check if $ARGUMENTS is:

• URL: Starts with http:// or https://
• Local path: Everything else (file or directory)

2a. Local Path Import

If local path:

1. Check if exists:

   ls -la "$ARGUMENTS"
   

2. Determine context for folder structure:

   • Extract project name from path (e.g., /projects/myapp/ -> myapp)
   • If path is generic (Downloads, tmp, home), ask user for context name
   • Read file header if available to detect project/tool name

3. Confirm with user:

   You specified a local path: {path}
   
   Suggested location: mabi-import/local/{context}/{filename}
   
   Is this correct? (The path will be copied, not moved)
   

4. Use AskUserQuestion to confirm or let user provide different context.

5. If confirmed:

   mkdir -p "mabi-import/local/{context}"
   cp -r "$ARGUMENTS" "mabi-import/local/{context}/"