How do I install the File Placement skill?

Run npx get-skill add tomevault-io/file-placement in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is File Placement safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with File Placement?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is File Placement free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published File Placement?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

File Placement by tomevault-io — Agent Skill

Name: File Placement
Author: tomevault-io

File Placement

Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

File Placement Skill

Apply correct file placement rules for all output files.

Why This Matters

File placement is enforced by hooks - violations will be blocked. This skill ensures you understand the rules so your work isn't rejected.

File Placement Rules

File Type	Required Directory	Examples
Summaries	`summaries/`	execution-summary.md, review-summary.md
Reports	`summaries/`	analysis-report.md, audit-report.md
Stories	`stories/`	STORY-001-feature.md
Bugs	`bugs/`	BUG-001-issue.md
Memory (exports)	`memory/exports/`	memory/exports/patterns/oauth2.md
Documentation	`docs/`	api-docs.md, architecture.md

Forbidden Placements

NEVER place these in the wrong location:

Summaries in docs/ or project root
Reports in docs/ or project root
Memory entries outside memory/exports/
Output files in source directories

Filename Rules

ALL-CAPS Restrictions

Only these filenames may be ALL-CAPS:

README.md, LICENSE, LICENSE.md
CLAUDE.md, SKILL.md, AGENTS.md
CHANGELOG.md, CONTRIBUTING.md
AUTHORS, NOTICE, PATENTS, VERSION
MAKEFILE, DOCKERFILE, COPYING, COPYRIGHT

All other files: Use lowercase-kebab-case

execution-summary.md (correct)
EXECUTION-SUMMARY.md (blocked)

Hook Enforcement

The summary-file-enforcement.js hook will:

Block files with ALL-CAPS names (except allowlist)
Block summary/report files outside summaries/
Suggest correct filename/location

Before Creating Files

Ask yourself:

Is this a summary or report? → Put in summaries/
Is this a memory entry? → Put in memory/exports/<category>/ (category: architecture, implementation, issues, patterns)
Is my filename lowercase-kebab? → If not, fix it
Am I using ALL-CAPS? → Only if in allowlist

Integration with Hooks

This skill provides guidance - you understand the rules. The hook provides enforcement - violations are blocked.

Together they ensure consistent file organization even when:

Context is lost
Rules are forgotten
New team members join

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: file-placementdescription: Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces. Use when this capability is needed.---# File Placement SkillApply correct file placement rules for all output files.## Why This MattersFile placement is **enforced by hooks** - violations will be blocked. This skill ensures you understand the rules so your work isn't rejected.## File Placement Rules| File Type | Required Directory | Examples ||-----------|-------------------|----------|| Summaries | `summaries/` | execution-summary.md, review-summary.md || Reports | `summaries/` | analysis-report.md, audit-report.md || Stories | `stories/` | STORY-001-feature.md || Bugs | `bugs/` | BUG-001-issue.md || Memory (exports) | `memory/exports/` | memory/exports/patterns/oauth2.md || Documentation | `docs/` | api-docs.md, architecture.md |## Forbidden Placements**NEVER place these in the wrong location:**- Summaries in `docs/` or project root- Reports in `docs/` or project root- Memory entries outside `memory/exports/`- Output files in source directories## Filename Rules### ALL-CAPS RestrictionsOnly these filenames may be ALL-CAPS:- README.md, LICENSE, LICENSE.md- CLAUDE.md, SKILL.md, AGENTS.md- CHANGELOG.md, CONTRIBUTING.md- AUTHORS, NOTICE, PATENTS, VERSION- MAKEFILE, DOCKERFILE, COPYING, COPYRIGHT**All other files**: Use lowercase-kebab-case- `execution-summary.md` (correct)- `EXECUTION-SUMMARY.md` (blocked)## Hook EnforcementThe `summary-file-enforcement.js` hook will:1. **Block** files with ALL-CAPS names (except allowlist)2. **Block** summary/report files outside `summaries/`3. **Suggest** correct filename/location## Before Creating FilesAsk yourself:1. Is this a summary or report? → Put in `summaries/`2. Is this a memory entry? → Put in `memory/exports/<category>/` (category: architecture, implementation, issues, patterns)3. Is my filename lowercase-kebab? → If not, fix it4. Am I using ALL-CAPS? → Only if in allowlist## Integration with HooksThis skill provides **guidance** - you understand the rules.The hook provides **enforcement** - violations are blocked.Together they ensure consistent file organization even when:- Context is lost- Rules are forgotten- New team members join---> Converted and distributed by [TomeVault](https://tomevault.io/claim/intelligentcode-ai) — claim your Tome and manage your conversions.

Frequently asked questions