backup-project SKILL.md skillF
backup-project from whoamimi/plugin-mimi is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add whoamimi/plugin-mimi/backup-project@git:20261110.44b066cPins git:20261110.44b066c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- F, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- whoamimi/plugin-mimi
- Path
plugins/code-skills/skills/backup-project/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261110.44b066c, committed Nov 10, 2026
- First version recorded
- Oct 22, 2026
- Size
- 12,301 bytes
- Repository stars
- 3
- License
- none declared
Briefs the user on CLI steps to back up a local project to GitHub, together with a checklist of their current local system setup (Git, GitHub CLI, identity, credentials, SSH) and their access to GitHub. Run from the VS Code integrated terminal at the project root. Use this whenever the user invokes /backup-project or says things like "back up my project", "push this to GitHub", "put my code on GitHub", "save my project to GitHub", "check my GitHub setup", "is Git set up…
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
# Backup Project Help the user back up the project in their open VS Code workspace to GitHub using only terminal commands. The skill has two jobs: first confirm the local machine and GitHub access are ready, then give the shortest reliable set of CLI steps to create the backup and to repeat it later. A backup only counts if it can be restored, and most failed pushes come from a missing identity, an expired login, or secrets nearly committed by accident. That is why the readiness checklist comes before the steps, and why the steps include a safety review of what is about to be uploaded. ## Arguments (both optional) | Argument | Meaning | Default | | ------------ | ------------------------------ | --------------------------- | | `repo` | Name for the GitHub repository | The workspace folder's name | | `visibility` | `private` or `public` | `private` | Invocation example: `/backup-project repo="habit-tracker" visibility="private"` Accept `key="value"` form or plain natural language. Never default to public. Only use `--public` when the user explicitly asks for it. ## Assumptions …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hkc3syautxtfjp4i/07acaf20651ddd878fe85e01e8e9ebdee835251f281fc2e118f63e6659cd818e.json
Then /plugin install backup-project@markdownregistry-hkc3syautxtfjp4i in Claude Code. It installs git:20261110.44b066c, the one graded F here, pinned to the commit it was graded at, and leaves it there.
mdr add whoamimi/plugin-mimi/backup-project@sha256:07acaf20651ddd87The line at the top of this page pins the label git:20261110.44b066c, 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_hkc3syautxtfjp4i)
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 whoamimi/plugin-mimi/backup-project 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 backup-project from somewhere else? Ask it: where did my backup-project 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 22, 2026 and Nov 10, 2026, about one every 19 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261110.44b066c latest | 2026-11-10 | 44b066c | 12,301 B | F | view · diff |
| git:20261022.6bef449 | 2026-10-22 | 6bef449 | 9,446 B | F | 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/backup-project/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
- FAIL, critical: No instruction to send local credentials anywhere (matched: upload it with `gh ssh-key add ~/.ssh)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12301 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 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
whoamimi/plugin-mimi · 3 stars · license none declared · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hkc3syautxtfjp4i GET https://markdownregistry.com/api/v1/resolve?ref=whoamimi/plugin-mimi/backup-project GET https://markdownregistry.com/api/v1/blob/07acaf20651ddd878fe85e01e8e9ebdee835251f281fc2e118f63e6659cd818e
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.