engage
Skill2 starsChanged 9 days agoMITView on GitHub
Like (スキ), comment and follow on note.com; notifications, memberships.
- Pipes a download into a shell
3 other projects use a version of this.
Adopted by
Most recently taken up by
- urvijain02/claude-autopilottheir own version, first seen Oct 25, 2026
- Epistates/sparXtheir own version, first seen Mar 23, 2026
- idapixl/social-media-suitetheir own version, first seen Mar 4, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- idapixl/social-media-suite★ 8same name
- Epistates/sparX★ 3same name
- urvijain02/claude-autopilot★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If note-cli is on PATH, use it.
- Very specific: line 17
If bun is missing, ask the user to install it (curl -fsSL https://bun.sh/install | bash).
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
note-cli:engage
Interact with other people on note.com through the unofficial API wrapper note-cli. These actions are visible to others: only act on articles and creators the user named, and confirm comment text with the user before posting. Never use these commands for bulk or automated liking, following or commenting; it breaks note's terms and gets accounts restricted.
Running note-cli
This skill ships with the CLI. This file lives at <plugin root>/skills/<skill>/SKILL.md; the CLI is a dependency-free bundle at <plugin root>/dist/note-cli.js (requires Bun).
- If
note-cliis on PATH, use it. - Otherwise, if
<plugin root>/dist/note-cli.jsexists, runbun <plugin root>/dist/note-cli.js ...with the absolute path. - Otherwise (the skill was installed on its own, e.g. with
npx skills add), ask the user before installing the CLI globally withbun add -g github:shoot16625/note-cli, then usenote-cli. - If
bunis missing, ask the user to install it (curl -fsSL https://bun.sh/install | bash). Below,note-climeans whichever of these works.
Output is JSON on stdout. Errors are JSON on stderr ({"error": {"code", "message"}}) with exit code 1 (2 for usage errors). Codes: NOT_LOGGED_IN, AUTH_ERROR, FORBIDDEN (note refused, with its reason in message), NOT_FOUND, RATE_LIMITED, API_ERROR, USAGE.
Login (only for commands that need it)
note-cli auth status tells you whether a session exists. To log in, run note-cli auth login yourself with a command timeout of at least 300 seconds. It opens a Chrome/Edge/Chromium window on the note.com login page and waits for the user to finish logging in there. Tell the user to log in in that window. Never ask for their password. If no browser is found, pass --browser <path>, or have the user copy the Cookie request header (or just the _note_session_v5 value) from DevTools and pipe it to note-cli auth import.
Commands
note-cli like <key|url> # スキ
note-cli unlike <key|url>
note-cli comment <key|url> "text" # post a comment; blank lines separate paragraphs
note-cli comment <key|url> - < reply.txt # read the text from stdin
note-cli comment <key|url> "text" --reply-to <commentKey> # reply (comment keys come from `note-cli comments <key>`)
note-cli comment delete <key|url> <commentKey> --yes
note-cli follow <urlname> # also accepts @urlname or a profile URL
note-cli unfollow <urlname>
note-cli notices # unread notifications / messages
note-cli membership plans # your membership plans
note-cli membership joined # memberships you belong toTo read comments and likes, use note-cli comments <key> and note-cli likes <key> (see note-cli:research).
Errors
COMMENT_GUIDELINES: note wants the user to accept its comment guidelines once. Ask them to open any article on note.com in their browser, start a comment, and accept the guidelines, then retry. Do not try to accept them on the user's behalf.FORBIDDEN: note refused (for example, comments are turned off, or the creator blocked the account);messagecarries note's reason.AUTH_ERROR: the session has expired; log in again (note-cli auth login).
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
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.

