The CLI is self-documenting. Always prefer running these commands over guessing
Works with
syntax or relying on memorized knowledge:
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnotion-cliExecute the skills CLI command in your project's root directory to begin installation:
Fetches notion-cli from makenotion/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate notion-cli. Access via /notion-cli in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
7
total installs
7
this week
69
GitHub stars
0
upvotes
Run in your terminal
7
installs
7
this week
69
stars
The CLI is self-documenting. Always prefer running these commands over guessing syntax or relying on memorized knowledge:
ntn api ls — list every public API endpoint.ntn api <path> --help — show methods, doc links, and usage for an endpoint.ntn api <path> --docs — print the full official docs for an endpoint.ntn api <path> --spec — print a reduced OpenAPI fragment (useful for
understanding request/response schemas).ntn <command> --help — help for any command or subcommand.npm i -g ntn@latest
NOTION_API_TOKEN — required for ntn api and ntn files. Set this env var
to a Notion integration token.ntn login / ntn logout — session auth for ntn workers and ntn tokens.
This does not authenticate ntn api or ntn files today.ntn apiRun ntn api --help for full syntax. Quick summary:
# GET with query param
ntn api v1/users page_size==100
# POST with inline body fields
ntn api v1/pages parent[page_id]=abc123
# POST with JSON body
ntn api v1/pages -d '{"parent":{"page_id":"abc123"}}'
The method is inferred (GET by default, POST when a body is present). Override
with -X METHOD.
ntn filesConvenience wrapper around the File Uploads API.
ntn files create < image.png
ntn files create --external-url https://example.com/photo.png
ntn files list
ntn files get <upload-id>
ntn workersManage Notion workers (deploy, list, execute, etc.). Run ntn workers --help
for subcommands.
ntn workers new my-worker # scaffold a new project
ntn workers deploy # deploy from current directory
ntn workers ls # list workers
ntn workers exec <capability> # execute a capability
ntn tokensManage tokens used by ntn workers. Requires ntn login. These are separate
from NOTION_API_TOKEN integration tokens.
ntn tokens create
ntn tokens ls
ntn tokens revoke <token-id>
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
jezweb/claude-skills
notion-cli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
notion-cli reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: notion-cli is focused, and the summary matches what you get after install.
I recommend notion-cli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
notion-cli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: notion-cli is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in notion-cli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for notion-cli matched our evaluation — installs cleanly and behaves as described in the markdown.
notion-cli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added notion-cli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 28