Directory Management Agent Skill

Manages project directory setup and artifact organization. Use when starting a new project, resuming an existing one, or when a PLAN.md needs to be associated with a project directory. Creates the project folder structure (specs/, scripts/, notebooks/, manifests/, agent_memory/) and resolves project naming.

440 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

850

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/awslabs/agent-plugins --skill directory-management

The instruction itself

3 sections, as written by the author

Directory Management

Project Setup

Before any work begins, resolve the project name:

If the project name is already known from conversation context, use it.
Otherwise, scan for existing */PLAN.md files in the current directory. If found, ask the user if they are resuming an existing project and load that PLAN.md into context.
If no existing projects are found, recommend a ≤64-char lowercase slug based on what you know from the conversation (only [a-z0-9-]), or ask directly if there isn't enough context. Present the recommended name and wait for user confirmation.

Once project name is resolved:

Create and/or use the <experiment-name>/ directory using the confirmed name for storing all the artifacts

Directory Structure

When working with the agent, all generated files are organized under an project directory.

<project-name>/
├── specs/  
│   ├── PLAN.md             # Your customization plan
├── scripts/                # Generated Python scripts
│   ├── <project-name>_transform_fn.py
├── notebooks/              # Generated Jupyter notebooks
│   ├── <project-name>.ipynb
├── manifests/              # Machine-readable outputs (JSON)
└── agent_memory/           # Session persistence (git-ignored)
    └── session-notes.md    # Progress, artifacts, next steps

Other skills for the same job

different authors, same section of the catalogue

Skill Creator

by anthropics

vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Replace with description of the skill and when Claude should use it.

35 tokens

Dispatching Parallel Agents

by ZhanlinCui

×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take awslabs/directory-management from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.