Agent skill
julien-notion-inbox-to-github
Move a GitHub repo entry from Notion Inbox [DB] to Github [DB]. Use when user wants to route a GitHub URL from inbox to the dedicated GitHub database, migrate inbox entry to github database, or move github link.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/julien-notion-inbox-to-github
SKILL.md
Notion Inbox to GitHub
Move GitHub repository entries from Inbox [DB] to Github [DB].
Prerequisites
NOTION_TOKENenvironment variable setrequestspackage:pip install requests
Usage
Run the migration script with a page ID or URL:
python ~/.claude/skills/notion-inbox-to-github/scripts/migrate.py <page_id_or_url>
Arguments:
page_id_or_url: Notion page ID (UUID) or full URL of the Inbox entry
Example:
python ~/.claude/skills/notion-inbox-to-github/scripts/migrate.py 12345678-1234-1234-1234-123456789abc
Output
- On success: URL of created Github [DB] entry
- On failure: Error message with reason
Workflow
- Script reads the Inbox entry properties
- Extracts GitHub URL from URL or Link property
- Checks for duplicates in Github [DB]
- Creates new entry with Name, URL, Source DB = "Inbox"
- Returns new page URL
Error Handling
| Error | Meaning |
|---|---|
DUPLICATE |
Entry already exists in Github [DB] |
NO_GITHUB_URL |
Entry doesn't have a github.com URL |
PAGE_NOT_FOUND |
Invalid page ID or no access |
NOT_INBOX_ENTRY |
Page is not from Inbox [DB] |
Database IDs
- Inbox [DB]:
e50fb9d3-5d64-4601-a2f2-c0ac80d84d86 - Github [DB]:
2cacdc04-12e3-81cc-a84e-fdbba086ab29
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?