troubleshoot SKILL.md skillA
troubleshoot 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/troubleshoot@git:20261103.7e2a158Pins git:20261103.7e2a158 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/troubleshoot/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261103.7e2a158, committed Nov 3, 2026
- First version recorded
- Oct 13, 2026
- Size
- 5,208 bytes
- Repository stars
- 6
- License
- MIT
When something did not work: read the error code, call get_help, then retry, reconnect or wake the Naver extension, or report it to the team.
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
# Troubleshoot
Use this when a call fails, a post is stuck, an automation did not react, a DM did not arrive, or the person asks why something happened.
## Procedure
1. Read the error code from the response (`error.code`), or the target's reason from `get_post`.
2. Call `get_help` with that `code` (or a short `query` in any language, and `platform` when it is one channel). Use `locale` for the person's language. Give them the answer's steps and its link.
3. Act on it with the table below. Never repeat the same failing call more than once without changing something.
4. If that does not solve it and the person wants the Uplika team to look, ask them first ("Should I send this to the Uplika team?"). Show what you will send: their own words (`personSaid`, in their language, not rewritten) and your account of what you tried (`summary`). On their OK call `report_problem` once, with the `code`, `requestId`, `tool`, `post` and `helpId` you have. Do not paste logs, tokens or keys; Uplika attaches its own request records. Tell them the reply goes to the email on their Uplika account, without promising when. A repeat of the same problem within a day is recorded but not emailed again, so…
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5omjdjt7eavpwk66/8b0f59af3d251484bde97e4c82fe8ad66c7e44a14a084fbcfd1be2807cd1c35b.json
Then /plugin install troubleshoot@markdownregistry-5omjdjt7eavpwk66 in Claude Code. It installs git:20261103.7e2a158, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add uplika/uplika-plugin/troubleshoot@sha256:8b0f59af3d251484The line at the top of this page pins the label git:20261103.7e2a158, 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_5omjdjt7eavpwk66)
2 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/troubleshoot 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 troubleshoot from somewhere else? Ask it: where did my troubleshoot 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 5 versions of this file, between Oct 13, 2026 and Nov 3, 2026, about one every 5 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261103.7e2a158 latest | 2026-11-03 | 7e2a158 | 5,208 B | A | view · diff |
| git:20261027.5a029d4 | 2026-10-27 | 5a029d4 | 4,334 B | A | view · diff |
| git:20261018.cf3a63c | 2026-10-18 | cf3a63c | 4,108 B | A | view · diff |
| git:20261017.0a2c1de | 2026-10-17 | 0a2c1de | 3,896 B | A | view · diff |
| git:20261013.28b896d | 2026-10-13 | 28b896d | 3,600 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/troubleshoot/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 (5208 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_5omjdjt7eavpwk66 GET https://markdownregistry.com/api/v1/resolve?ref=uplika/uplika-plugin/troubleshoot GET https://markdownregistry.com/api/v1/blob/8b0f59af3d251484bde97e4c82fe8ad66c7e44a14a084fbcfd1be2807cd1c35b
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.
More from uplika/uplika-plugin
Every file in uplika/uplika-plugin