ccn:create-topic
About
This skill creates structured topic files in a `.notes/` directory with formatted frontmatter and section headers. It automatically validates input, normalizes filenames (converting to uppercase with underscores), and checks for existing files to prevent overwrites. Use it to quickly scaffold new documentation or note files with consistent formatting.
Quick Install
Claude Code
Recommended/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/ccn:create-topicCopy and paste this command in Claude Code to install this skill
Documentation
Create Topic Skill
This skill creates a new topic file in the .notes/ directory with structured frontmatter and section headers.
Instructions for Claude
When this command is invoked with /ccn:create-topic $ARGUMENTS:
Step 1: Validate argument
If $ARGUMENTS is empty or not provided:
- Show error: "Error: Topic name required"
- Show usage: "Usage: /ccn:create-topic <topic-name>"
- STOP - do not continue
Step 2: Normalize topic name to filename
Take the provided topic name and transform it:
- Replace all spaces with underscores
- Replace all hyphens with underscores
- Convert to UPPERCASE
- Add
.mdextension
Examples:
- "api-design" → "API_DESIGN.md"
- "my topic" → "MY_TOPIC.md"
- "error_handling" → "ERROR_HANDLING.md"
Store the result as the filename.
Step 3: Check if file exists
Use the Read tool to check if .notes/{filename} already exists.
-
If the file EXISTS:
- Tell user: "Error: Topic already exists: .notes/{filename}"
- Tell user: "Use /ccn:update-topic to add entries to this topic"
- STOP - do not continue
-
If the file DOES NOT exist:
- Continue to next step
Step 4: Create .notes/ directory if needed
Use the Bash tool to ensure the directory exists:
mkdir -p .notes
Step 5: Generate frontmatter
Create YAML frontmatter with these fields:
-
description: "Knowledge and patterns for {original topic name}"
- Use the original input, not the normalized filename
- Example: input "api-design" → "Knowledge and patterns for api-design"
-
keywords: Generate array from normalized filename
- Split filename (without .md) on underscores
- Lowercase each part
- Include the combined form (full filename without .md, lowercased)
- Example: "API_DESIGN.md" →
["api", "design", "api_design"]
-
last_updated: Today's date in YYYY-MM-DD format
Step 6: Create file with template
Use the Write tool to create .notes/{filename} with this structure:
---
description: "Knowledge and patterns for {topic}"
keywords: [{keyword array}]
last_updated: "YYYY-MM-DD"
---
# {Topic Name}
## Overview
(Add overview content here)
## Key Concepts
(Document key concepts here)
## Patterns
(Capture recurring patterns here)
## Notes
(Add detailed notes here)
---
*Topic created: YYYY-MM-DD*
Important formatting notes:
- Use the original topic name (not normalized) for the H1 heading
- Use proper YAML array syntax for keywords
- Include the footer timestamp at the bottom
Step 7: Confirm completion
Tell the user: "Created: .notes/{filename}"
Error Handling
If any tool fails (mkdir, Read, Write):
- Show the error message
- Explain what went wrong
- Do NOT create partial files
GitHub Repository
Related Skills
algorithmic-art
MetaThis Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
executing-plans
DesignUse the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
cost-optimization
OtherThis Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.
