doc-creation

Intercept markdown file creation in managed docs directories and suggest `/docs new`.

6|1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/L3DigitalNet/Claude-Code-Plugins --skill doc-creation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-creation
Source: https://github.com/L3DigitalNet/Claude-Code-Plugins/tree/main/plugins/docs-manager/skills/doc-creation
Command: npx skills add https://github.com/L3DigitalNet/Claude-Code-Plugins --skill doc-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents the accumulation of untracked documents within managed documentation directories by guiding users to use the appropriate /docs new command.

Core Features & Use Cases

  • Proactive Guidance: Intercepts new .md file creation attempts in managed documentation locations.
  • Contextual Suggestions: Recommends using /docs new for proper frontmatter and index registration.
  • Use Case: When a user tries to create a new README.md file directly inside a project's /docs/api/ folder, this skill prompts them to use /docs new instead, ensuring the new document is correctly added to the documentation's index.

Quick Start

Use the doc-creation skill to create a new markdown file in the managed documentation directory.

Frequently Asked Questions about doc-creation

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

FAQPage Schema
How do I create markdown files in managed documentation directories?

To create markdown files in managed documentation directories, use the `/docs new` command. This ensures the file is correctly added to the documentation index with proper frontmatter registration.

Why does creating a new README.md directly in a docs folder get intercepted?

Creating a new README.md directly in a docs folder is intercepted to prevent untracked documents from accumulating. The system checks if the target path is within a docs-manager library before allowing normal file creation.

What is the best way to prevent untracked markdown documents in a docs-manager library?

The best way to prevent untracked markdown documents in a docs-manager library is to use the `/docs new` command for proper frontmatter and index registration instead of manual file creation.

Does this skill allow normal file creation outside of known docs directories?

Yes, this skill allows normal file creation outside of known docs directories. It specifically intercepts new `.md` file creation attempts within managed documentation locations to provide proactive guidance.

What happens when I try to create a new .md file in a project's /docs/ folder?

When you try to create a new `.md` file in a project's `/docs/` folder, the skill prompts you to use `/docs new` instead, ensuring the new document is correctly added to the documentation's index.