Andrew Yim
d1cd1298a8
Pipeline Orchestrator: - Add 07-pipeline-orchestrator skill with code/CLAUDE.md and desktop/SKILL.md - Add /reference-curator-pipeline slash command for full workflow automation - Add pipeline_runs and pipeline_iteration_tracker tables to schema.sql - Add v_pipeline_status and v_pipeline_iterations views - Add pipeline_config.yaml configuration template - Update AGENTS.md with Reference Curator Skills section - Update claude-project files with pipeline documentation Skill Format Refactoring: - Extract YAML frontmatter from SKILL.md files to separate skill.yaml - Add tools/ directories with MCP tool documentation - Update SKILL-FORMAT-REQUIREMENTS.md with new structure - Add migrate-skill-structure.py script for format conversion Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
89 lines
2.5 KiB
Markdown
89 lines
2.5 KiB
Markdown
# 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
|