elnora-folders

Create, rename, move, and delete folders within Elnora projects.

4|1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Elnora-AI/elnora-plugins --skill elnora-folders
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elnora-folders
Source: https://github.com/Elnora-AI/elnora-plugins/tree/main/elnora/skills/elnora-folders
Command: npx skills add https://github.com/Elnora-AI/elnora-plugins --skill elnora-folders

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage folders within Elnora projects to organize files, structure hierarchies, and perform lifecycle operations.

Core Features & Use Cases

  • List folders in a project
  • Create nested folders (with optional parent_id)
  • Rename, move, and delete folders with safety prompts

Quick Start

Create a new folder in a project and optionally assign a parent_id to nest it under an existing folder.

Frequently Asked Questions about elnora-folders

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

FAQPage Schema
How do I create nested folders in a project management system?

To create nested folders, you create a new folder within your project and assign an optional parent_id, which nests it under an existing folder in the hierarchy. This structures your project files logically.

Can I move and rename folders within an existing project hierarchy?

Yes, you can move and rename folders within a project hierarchy by specifying the project_id and folder_id. Moving folders between parents restructures your file organization without data loss.

Does MCP tooling support safe folder deletion in project management workflows?

MCP tooling supports folder deletion by requiring project_id and folder_id parameters, and it includes safeguards with safety prompts for destructive deletes to prevent accidental data removal.

What is needed to manage folders across single and nested project structures?

Managing folders requires MCP tooling parameters including project_id, folder_id, and name, plus an optional parent_id for nesting. This enables listing, creating, moving, and deleting across hierarchies.

What happens when I delete a folder in a nested hierarchy?

Deleting a folder in a nested hierarchy triggers a safety prompt to prevent destructive deletes. The MCP tooling requires the specific project_id and folder_id to execute the removal safely.

Are there limitations when moving folders between parent directories?

The metadata does not specify explicit limitations for moving folders between parents, but the operation requires valid project_id, folder_id, and target parent_id parameters to execute correctly.