Create new files in knowledge base with directory governance. Use when user wants to save, create, or add content. Reads RULE.md to understand directory purpose and follows specified rules. Recommends target directory based on content analysis.
Create new files in knowledge base with directory governance. Use when user wants to save, create, or add content. Reads RULE.md to understand directory purpose and follows specified rules. Recommends target directory based on content analysis.
Add Content Skill
Generic file creation Skill that works with any directory structure by reading RULE.md to understand purpose and rules.
When to use this Skill
User says "save", "create", "add", "note", "記錄", "筆記"
User provides content to store
User provides URLs to archive
User mentions "readlater", "bookmark", "save article"
Identify root directory (current working directory or user-specified)
List main directories using ls or Glob
Read RULE.md from each main directory
Build directory catalog with purposes
Example scan result:
ReadLater/ - Purpose: "Archive web content for later reading"
Research/ - Purpose: "Technical and academic research notes"
Work/ - Purpose: "Professional work-related content"
Personal/ - Purpose: "Personal life documentation"
Miscellaneous/ - Purpose: "General notes and articles"
3. Smart Classification
Match content to directories:
Analyze content topics vs directory purposes
Check if content type matches directory specialization
Consider user's past behavior (if known)
Rank directories by suitability (0-100 score)
Classification logic:
URL + directory purpose mentions "web archival" → high score
Technical content + directory purpose mentions "research" → high score
Work keywords + directory purpose mentions "professional" → high score
Default to "Miscellaneous" or similar general-purpose directory
4. User Confirmation
Present recommendation:
I analyzed your content about [topic].
Recommended location: [Directory]/
Reason: [Why this directory suits the content]
Is this correct?
- Yes (proceed with this directory)
- No, use different directory (please specify path)
- Show me other options
If user requests alternatives:
Show top 3 ranked directories with scores and reasons
Allow user to choose or specify custom path
If user specifies custom path:
Validate path exists or create if requested
Continue with specified path
5. Read Target RULE.md
Locate and read RULE.md:
Check target directory for RULE.md
If not found, check parent directories (inheritance)
If no RULE.md found, ask user if should create one
Special instructions (e.g., "fetch from URL", "generate summary")
Business logic workflows (e.g., web archival process)
Format examples
6. Execute Operation Per RULE.md
Follow RULE.md instructions exactly:
Example 1 - Simple Note:
RULE.md says: "Files named YYYY-MM-DD-title.md with markdown format"
→ Generate filename: 2025-10-28-transformer-architecture.md
→ Create file with content
→ Save in target directory
Example 2 - Web Archival:
RULE.md says:
"When user provides URL:
1. Fetch content using WebFetch
2. Convert to markdown
3. Create directory: Articles/YYYY/MM/YYYY-MM-DD_title-slug/
4. Save article.md and metadata.yaml"
→ Execute WebFetch on URL
→ Extract title, content, date
→ Convert to clean markdown
→ Create directory structure
→ Save article.md with content
→ Create metadata.yaml with:
- url: [original URL]
- title: [article title]
- date: [fetch date]
- summary: [brief summary]
→ Optionally save images if referenced
Example 3 - Structured Content (WorkLog):
RULE.md says:
"Daily logs in YYYY/QX/MM-Month/ structure.
MUST verify datetime first.
Format: [specific template shown in RULE.md]"
→ Execute `date` command to verify current date
→ Parse date: 2025-10-28 → 2025/Q4/10-October/
→ Check if directory structure exists, create if needed
→ Read RULE.md template section
→ Create/update 2025-10-28.md with template format
→ Fill in sections per RULE.md specifications
Key principles:
Execute special instructions literally (e.g., "fetch from URL")
Brief description (from content analysis or user input)
Timestamp: current date
Update "Recent Changes" section
Update "Last updated" timestamp
Save README.md
Update parent README.md if needed:
If created new subdirectory, update parent's README.md
Add entry for new subdirectory with description
Verify updates:
Check README.md is valid markdown
Ensure no duplicate entries
Confirm timestamps are current
8. Report to User
Confirm operation complete:
✅ Content created successfully
Location: [full path to file]
Format: [file format used]
Governance: [which RULE.md applied]
README.md updated:
- [target directory]/README.md
- [parent directory]/README.md (if applicable)
Summary:
[Brief summary of what was created and where]
Special Cases
URL Content Archival
When content is URL and RULE.md specifies archival:
Validate URL:
Check URL format is valid
Optionally test if URL is accessible
Check for Duplicates:
Search existing README.md for this URL
If found: warn user, ask if should re-archive
Fetch Content:
Use WebFetch tool with prompt: "Extract the main article content, title, and publication date"
