메뉴
Use the Notion CLI `ntn` for authenticated Notion API requests, pages, data sources, file uploads, and Notion Workers. Use when the user asks to run or script `ntn`, inspect Notion API endpoints, create or edit Notion content from the terminal, or deploy and operate Notion Workers.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | notion-cli |
| description | Use the Notion CLI `ntn` for authenticated Notion API requests, pages, data sources, file uploads, and Notion Workers. Use when the user asks to run or script `ntn`, inspect Notion API endpoints, create or edit Notion content from the terminal, or deploy and operate Notion Workers. |
| allowed-tools | ["WebFetch(domain:developers.notion.com)","Bash(ntn *)"] |
ntn is the official Notion CLI. Prefer it over hand-written HTTP calls when the task can use CLI auth, endpoint discovery, inline request bodies, page Markdown commands, file uploads, or Workers commands.
Assume ntn is installed and authenticated when the user asks for Notion CLI work. Do not install, update, configure completions, run login flows, or inspect auth files. If a command fails because the CLI or auth is missing, report the exact command and error; the user fixes local setup.
Load only what the task needs:
ntn api, inline body syntax, query params, endpoint discovery, debugging.ntn api.Use official Markdown docs for drift checks:
https://developers.notion.com/cli/get-started/overview.md
https://developers.notion.com/cli/reference/commands.md
https://developers.notion.com/llms.txt
--json for machine parsing and --plain for shell scripts that need stable tab-separated fields.-v or --verbose when diagnosing CLI failures.NOTION_WORKSPACE_ID=<id> for a one-command workspace override.--notion-version or NOTION_API_VERSION only when the user needs a specific API version.Browser automation CLI wrapping Playwright for one-shot tasks like navigation, page interaction, screenshots, and scraping. Use when driving a live browser from the terminal. Skip for repeat automations that warrant a full Playwright script.
Author and maintain agent context markdown — AGENTS.md, rules, skills, memory files. Use when creating, editing, or refactoring any agent-focused doc, or after major codebase exploration to capture learning.
Author and audit Agent Skills. Use when creating a new skill, refactoring an existing one, or rewriting skill metadata (name, description, allowed-tools).
Build ASCII/Unicode animations such as loading spinners, logo reveals, particle effects, and terminal art. Covers character grids, frame loops, per-character state machines, ordering, and performance. Use when designing any character-based visual animation.
Run tests, builds, migrations, or any command needing real CI secrets/services on Blacksmith. Use when testing or validating code, or before any commit or push that should be verified against CI.
Use when editing files in a Bun project (bun.lock or bun.lockb at the root, a packageManager field set to bun in package.json, or imports from the bun namespace) or running bun/bunx commands. Covers Bun-native APIs, the bun test runner, bun build --compile, and the Bun-optimized tsconfig.