agentleFS
taixuanntaixuann/development-space/.agents/skills/notion-cli/SKILL.md

notion-cli

Skill1 starsChanged 13 days agoMITView on GitHub

Use the Notion CLI (`ntn`) to interact with the Notion API, manage workers, and upload files. Use when the user asks to "call the Notion API", "deploy a worker", "upload a file to Notion", "create a page", "query a database", or any task involving the `ntn` command.

  • Pipes a download into a shell

8 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check NOTION_API_TOKEN first.

    line 35
  2. Very specific:

    Run ntn api --help for full syntax.

    line 43
  3. Very specific:

    Prefer ntn pages create / ntn pages update for Markdown page content.

    line 61
  4. Very specific:

    Only fall back to rich_text if you need features that Markdown cannot express (e.g.

    line 73
  5. Very specific:

    Search with a JSON body, sorted newest first: ntn api v1/search -d …

    line 78

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Notion CLI

Look things up before answering

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 pages get <page-id> — retrieve a page as Markdown. Use this to read page content.
  • ntn <command> --help — help for any command or subcommand.

Install

curl -fsSL https://ntn.dev | bash

Authentication

  • The CLI automatically uses NOTION_API_TOKEN when it is set.
  • Check NOTION_API_TOKEN first. If it is already set, prefer using it instead of telling the user to run ntn login.
  • ntn login / ntn logout — log the CLI in or out (only use if not using NOTION_API_TOKEN). ntn login requires the user to visit a URL in a web browser.

ntn api

Run 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.

Markdown for pages and comments

Prefer ntn pages create / ntn pages update for Markdown page content. Use the markdown field when creating or updating comments via ntn api.

# Comment with markdown
ntn api v1/comments -d '{"parent":{"page_id":"abc123"},"markdown":"Here is a [link](https://example.com) and **bold text**."}'

# Page with markdown body
ntn pages create --parent page:abc123 --content '## Heading\n\nSome *formatted* content.'

The markdown field supports inline formatting (bold, italic, code, links, etc.). Only fall back to rich_text if you need features that Markdown cannot express (e.g. mentions, custom emoji, or colors).

Reading pages and search results

  • A page URL ends in a 32-character ID after the slug. Strip any query string. ntn pages get <id> accepts that bare ID and prints Markdown with a YAML title: line at the top.
  • Search with a JSON body, sorted newest first: ntn api v1/search -d '{"query":"...","page_size":30,"sort":{"direction":"descending","timestamp":"last_edited_time"}}'.
  • Results mix object types. A page's title is under properties, in the entry whose type is title. A data source's title is in its title array. Read both, or the list prints blank titles.

ntn files

Convenience 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 workers

Manage 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.