naver-engage · git:20261014.991bd30 · 2026-10-14 · sha256 91bd5d7ac02fec90

naver-engage git:20261014.991bd30A

Immutable. This exact content never changes and is served at /api/v1/blob/91bd5d7ac02fec90.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lbd7tdan5hxbwoi5/91bd5d7ac02fec90e8aa683a522a255e6a7c9ba2c9665e765e9c56e0aefd4979.json

Then /plugin install naver-engage@markdownregistry-lbd7tdan5hxbwoi5 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: naver-engage
description: Comment on neighbors' new posts, like, and follow on Naver Blog through automations, without guessing limits. 이웃 댓글, 공감.
---

# Naver engage

Engage with other Naver blogs from the person's connected blog: an automation that comments on neighbors' new posts (이웃 새 글 댓글), and one-off likes (공감) and follows (이웃추가). Everything here shows up on someone else's blog under the person's name, so every action is confirmed with them first.

All of it runs in the Uplika extension in the person's Chrome. Call `bridge_status` before a like, a follow or turning the automation on. If `state` is not `online`, relay `userMessage` word for word and wait until the person says Chrome is open.

## Actor and target are two different blogs

- **Actor:** the person's connected Naver Blog, the account the action is done as. In the extension's jobs this is `blogId`, and the server fills it in from the connected account. A workspace holds one Naver Blog, so choosing the workspace chooses the actor (`follow` still has an `accountId` argument for several blogs in one workspace; you will not need it). If a call answers `workspace_required`, show the workspaces it lists, ask which blog should act, and pass `workspaceId`.
- **Target:** the other blog, the owner of the post being liked or commented on, or the blog being followed. In the jobs this is `targetBlogId`, taken from the link.
- They are different values. Never derive one from the other: a link to someone else's post does not change who acts, and the actor never comes from a link.
- The person's Chrome has to be logged in to Naver as the actor blog. If it is logged in as a different blog, the job stops with `naver_wrong_login` and touches nothing. Relay the message, ask the person to log in as the actor blog, then try once more.

## Limits are not ours to guess

Never state, estimate or promise how many comments, likes or follows are safe per day or per hour, and never invent a pace. Naver closed its writing API over mechanical mass activity, and when Naver restricts an account it is the person's blog that gets suspended, not Uplika. Uplika's server and Naver decide the limits:

- The neighbor comment automation applies its own skip rules on the server (one comment per post, a gap between comments, nothing older than 48 hours). Uplika sets no daily count of its own since 2026-10-14; its description in `list_automation_templates` says what it skips; repeat that, not numbers of your own.
- If a call answers `naver_rate_limited`, `naver_engagement_limited` or `rate_limited`, stop. Do not call again before `retryAfterSeconds`, and do not work around it through another account or workspace. `naver_engagement_limited` means Naver itself stopped showing the add-neighbor page for that blog today (the page came back blank more than once); the answer carries `until`, and nothing goes out from that blog before midnight Korea time. Tell the person it is Naver's limit, not Uplika's, and pass on the `help` link.
- Like and follow only the posts and blogs the person names. Do not walk a list of blogs or a search result liking or following each one.

## Comment on neighbors' new posts (automation)

`template:neighbor_post_comment`: when a neighbor publishes a new post, Uplika reads it and leaves one comment written by AI in the channel's persona.

1. Call `list_accounts` to find the Naver Blog and its `accountId`. Call `list_automations` with that `accountId` and `templateId` `neighbor_post_comment` to see whether one already exists; reuse it rather than creating a second one.
2. Read the template in `list_automation_templates`: its params and what it skips.
3. Ask the person:
   - Whose posts: mutual neighbors only (`mutual`, the default) or every neighbor in the feed (`all`).
   - The instruction: what the blog is about and how the comments should sound (예: 「여행 블로그예요. 글에서 구체적인 장면 하나를 짚어 짧게 공감하는 댓글, 홍보 문구는 넣지 않기」).
   - A name for the automation.
4. Call `create_automation` with `accountId`, `templateId` `neighbor_post_comment` and `params` (`neighbors`, `instruction`, `name`). It is saved as a draft; nothing is posted yet.
5. Before turning it on, tell the person plainly:
   - Once it is live, each comment goes out on the neighbor's post without passing by them first.
   - It reacts only to posts published after it is turned on, and it skips posts and holds back comments by the rules in the template's description.
   - It runs only while Chrome with the Uplika extension is open on their computer.

   Show the instruction and the neighbor setting, and turn it on with `enable_automation` only after they approve.
6. Afterwards, `list_automation_runs` shows what it commented on and what it skipped. When the person wants it stopped, call `disable_automation`.

## Like (공감)

1. Take the link to the post from the person. On Naver Blog the post can belong to another blog; the connected blog does the liking.
2. Confirm with the person which post it is and which blog acts. Uplika has no unlike.
3. Call `like` with the link as `id`. To like a comment on the person's own post instead, pass `replyTo` with the comment's id from `list_replies`.
4. `already: true` means it was already liked and nothing changed. `naver_not_allowed` means Naver offers no like there: the person's own post, a secret or hidden comment, or a blog that turned comment likes off. Retrying does not help.

## Follow (이웃추가)

1. Take the blog from the person: its id or any link to it.
2. Ask which kind: a neighbor (이웃), added right away, or a mutual neighbor (서로이웃), a request the other blog has to accept, optionally with a message Naver shows them.
3. Confirm, then call `follow` with `blog`, `mutual` and `message`. Uplika has no unfollow.
4. The answer is `following` (added), `pending` (the mutual request waits for them) or `already` (already a neighbor). `naver_follow_blocked` means that blog does not take neighbor requests.

## When something fails

- `bridge_offline`: the extension in the person's Chrome is not connected, so the like or follow did not happen. Relay the message (`faq:naver-extension-offline`), and try again once the person says Chrome is open.
- `extension_outdated`: the extension in that Chrome is too old for this job; the response says the installed and required versions. Relay it with `faq:extension-not-updating`.
- Anything else: call `get_help` with the error code and pass its answer and link on.

## Tools

- `list_accounts`: the connected Naver Blog that acts
- `bridge_status`: whether the extension in the person's Chrome is online
- `list_automations`: an existing neighbor comment automation on that account
- `list_automation_templates`: the template's params and what it skips
- `create_automation`: save the neighbor comment automation as a draft
- `enable_automation`: turn it on (after approval)
- `list_automation_runs`: what it commented on and what it skipped
- `disable_automation`: turn it off
- `list_replies`: comment ids on the person's own post
- `like`: like a post or comment as the connected blog (after approval)
- `follow`: add a blog as a neighbor (after approval)
- `get_help`: the answer for an error code