naver-keywords SKILL.md skillA
naver-keywords 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-keywords@git:20261013.28b896dPins git:20261013.28b896d 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-keywords/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261013.28b896d, committed Oct 13, 2026
- First version recorded
- Oct 9, 2026
- Size
- 8,121 bytes
- Repository stars
- 6
- License
- MIT
Research Naver Blog keywords: diagnose the blog, expand seeds, measure and judge, pick one set per post. 네이버 키워드 조사, 검색량.
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 keywords Find keywords a Naver Blog post can actually win, measured and judged by Uplika, and leave with one keyword set per post. The set's `draftPrompt` is the brief the writing skills work from. Use it when the person asks what to write about on Naver, which keywords to target, how often a keyword is searched (검색량), or wants a keyword set before writing. Writing and publishing belong to the `naver-post` skill, or `naver-ai-cite` when the goal is to be cited in Naver's AI Briefing. ## Procedure 1. **Blog.** Ask which blog this is for (its id or any link to it). If the person has a connected Naver Blog, `list_accounts` shows it and its handle is the blog id. Any public blog works, connected or not. 2. **Diagnose.** Call `diagnose_naver_blog` with the blog. Read what it returns: the share of titles that carry a search intent word (price, how to, review), how many titles start with a date or episode label, posts per month, the categories, and `flags` with `thresholds` (for example `lowIntent`). `summary.oldest` and `summary.newest` say which dates it read and `summary.capped` says whether it stopped early, so do not describe a long-running blog's whole history from it… …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_zeg7tejx5wf7y76o/4a0141bb97b5f4659c6d13e91b5476759ffc97d5b52ca8aae866ea95c0e7c304.json
Then /plugin install naver-keywords@markdownregistry-zeg7tejx5wf7y76o in Claude Code. It installs git:20261013.28b896d, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add uplika/uplika-plugin/naver-keywords@sha256:4a0141bb97b5f465The line at the top of this page pins the label git:20261013.28b896d, 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_zeg7tejx5wf7y76o)
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-keywords 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-keywords from somewhere else? Ask it: where did my naver-keywords 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 2 versions of this file, between Oct 9, 2026 and Oct 13, 2026, about one every 3 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261013.28b896d latest | 2026-10-13 | 28b896d | 8,121 B | A | view · diff |
| git:20261009.4206a03 | 2026-10-09 | 4206a03 | 7,584 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-keywords/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 (8121 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_zeg7tejx5wf7y76o GET https://markdownregistry.com/api/v1/resolve?ref=uplika/uplika-plugin/naver-keywords GET https://markdownregistry.com/api/v1/blob/4a0141bb97b5f4659c6d13e91b5476759ffc97d5b52ca8aae866ea95c0e7c304
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.