naver-engage SKILL.md skillA
naver-engage from uplika/uplika-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add uplika/uplika-plugin/naver-engage@git:20261111.d17a644Pins git:20261111.d17a644 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- uplika/uplika-plugin
- Path
skills/naver-engage/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261111.d17a644, committed Nov 11, 2026
- First version recorded
- Oct 9, 2026
- Size
- 11,884 bytes
- Repository stars
- 6
- License
- MIT
Comment on neighbors' new posts, find neighbor candidates, like and follow on Naver Blog without guessing limits. 이웃 댓글, 서로이웃 후보, 공감.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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`. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lbd7tdan5hxbwoi5/fe033e938bf50d90b936a4126d94b27a850d6829d38a6a74fca3214a9f38fff9.json
Then /plugin install naver-engage@markdownregistry-lbd7tdan5hxbwoi5 in Claude Code. It installs git:20261111.d17a644, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add uplika/uplika-plugin/naver-engage@sha256:fe033e938bf50d90The line at the top of this page pins the label git:20261111.d17a644, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lbd7tdan5hxbwoi5)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in uplika/uplika-plugin/naver-engage since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of naver-engage from somewhere else? Ask it: where did my naver-engage come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Oct 9, 2026 and Nov 11, 2026, about one every 11 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261111.d17a644 latest | 2026-11-11 | d17a644 | 11,884 B | A | view · diff |
| git:20261027.8cb5709 | 2026-10-27 | 8cb5709 | 10,023 B | A | view · diff |
| git:20261014.991bd30 | 2026-10-14 | 991bd30 | 7,323 B | A | view · diff |
| git:20261009.4206a03 | 2026-10-09 | 4206a03 | 6,853 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/naver-engage/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11884 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
uplika/uplika-plugin · 6 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lbd7tdan5hxbwoi5 GET https://markdownregistry.com/api/v1/resolve?ref=uplika/uplika-plugin/naver-engage GET https://markdownregistry.com/api/v1/blob/fe033e938bf50d90b936a4126d94b27a850d6829d38a6a74fca3214a9f38fff9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.