b6a478e1df
## Summary - Add portable installation tool (`install.sh`) for cross-machine setup - Add Claude.ai export files with proper YAML frontmatter - Add multi-agent-guide v2.0 with consolidated framework template - Rename `00-claude-code-setting` → `00-our-settings-audit` (avoid reserved word) - Add YAML frontmatter to 25+ SKILL.md files for Claude Desktop compatibility ## Commits Included - `93f604a` feat: Add portable installation tool for cross-machine setup - `9b84104` feat: Add Claude.ai export for portable skill installation - `f7ab973` fix: Add YAML frontmatter to Claude.ai export files - `3fed49a` feat(multi-agent-guide): Add v2.0 with consolidated framework - `3be26ef` refactor: Rename settings-audit skill and add YAML frontmatter Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
96 lines
2.8 KiB
Markdown
96 lines
2.8 KiB
Markdown
---
|
|
name: notion-organizer
|
|
description: |
|
|
Notion workspace manager for database optimization, property cleanup, and bulk operations.
|
|
Triggers: organize Notion, workspace cleanup, database schema, property standardization.
|
|
---
|
|
|
|
# Notion Organizer Skill
|
|
|
|
## Purpose
|
|
|
|
Specialized Notion workspace management capability for:
|
|
- Database schema analysis and optimization
|
|
- Property standardization and cleanup
|
|
- Content restructuring and hierarchy optimization
|
|
- Database merging and migration
|
|
- Bulk operations with rate-limit compliance
|
|
|
|
## Execution Strategy: Three-Tier Approach
|
|
|
|
Always follow this priority order:
|
|
|
|
### Tier 1: Notion MCP Tools (Primary)
|
|
|
|
Use built-in MCP tools first. Available tools:
|
|
|
|
| Tool | Purpose |
|
|
|------|---------|
|
|
| `mcp__notion__search` | Find pages/databases by keyword |
|
|
| `mcp__notion__get-page` | Retrieve page content |
|
|
| `mcp__notion__get-database` | Retrieve database schema |
|
|
| `mcp__notion__create-page` | Create new pages |
|
|
| `mcp__notion__update-page` | Modify page properties |
|
|
| `mcp__notion__query-database` | Query database with filters |
|
|
|
|
### Tier 2: Alternative Approaches (Fallback)
|
|
|
|
If MCP tools insufficient:
|
|
- Export/import via filesystem (user action required)
|
|
- Memory tools for tracking state across sessions
|
|
- Sequential thinking for complex planning
|
|
|
|
### Tier 3: Python Scripts (Advanced)
|
|
|
|
For bulk operations (50+ items):
|
|
- Generate async Python scripts
|
|
- Include rate limiting (3 req/sec max)
|
|
- Provide requirements.txt
|
|
- Always include dry-run option
|
|
|
|
See `scripts/` directory for templates.
|
|
|
|
## Operational Guidelines
|
|
|
|
### Before Any Modification
|
|
1. **Fetch first**: Always examine current structure before changes
|
|
2. **Confirm destructive actions**: Get user approval for deletes/major restructures
|
|
3. **Estimate impact**: For large operations, provide time/API call estimates
|
|
4. **Backup reminder**: Remind about Notion version history
|
|
|
|
### Rate Limits (Critical)
|
|
- Maximum: 3 requests/second average
|
|
- Use pagination (100 items max per request)
|
|
- Implement exponential backoff on 429 errors
|
|
|
|
### Communication
|
|
- Korean for explanations (한국어로 설명)
|
|
- English for code and technical terms
|
|
- Structured before/after summaries
|
|
|
|
## Quick Commands
|
|
|
|
### Database Audit
|
|
"Analyze [database name] structure and recommend optimizations"
|
|
|
|
### Property Cleanup
|
|
"Standardize property names in [database] to [convention]"
|
|
|
|
### Bulk Move
|
|
"Move all pages tagged [X] from [source] to [target]"
|
|
|
|
### Schema Migration
|
|
"Migrate data from [source database] to [target database]"
|
|
|
|
## Workflow Patterns
|
|
|
|
See `reference.md` for detailed workflow documentation.
|
|
See `scripts/` for Python templates.
|
|
|
|
## Limitations
|
|
|
|
- Cannot access unshared databases/pages
|
|
- Cannot modify workspace settings
|
|
- Cannot recover permanently deleted content
|
|
- Large operations (1000+ pages) require Python scripts
|