schedule-week SKILL.md skillA
schedule-week 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/schedule-week@git:20261009.4206a03Pins git:20261009.4206a03 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/schedule-week/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261009.4206a03, committed Oct 9, 2026
- Size
- 8,019 bytes
- Repository stars
- 6
- License
- MIT
Plan a week of posts across your channels and schedule them in one pass; everything is shown for approval before anything is scheduled.
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
# Schedule a week Use this for "plan next week's posts", "fill my content calendar", "schedule this week across my channels". It plans the week, writes every post the way that channel's skill writes it, shows the whole week for approval, then schedules all of it in one pass. Uplika's server holds each post and sends it at its time. ## 1. Channels, dates and time zone 1. Call `select_channels` with no scope to get the connected candidates and let the person choose (or `all`). Never assume a channel is connected; if nothing comes back, send them to https://uplika.com/dashboard/connections. Read out `skipped` (expired or not-yet-live channels, with the sentence and reconnect link it gives). If it answers `workspace_required`, show the workspaces it lists, ask which one, and pass `workspaceId` on every later call. 2. Ask which time zone the times are in, and use the one the person states. Do not guess it from their language, their location or this machine. 3. Turn "next week" into real dates in that time zone and say them back. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xhdgv6ojr75qmndw/4f1d3d5558b98f67e4c534db351a1e00f3e24d3e3f263503837f9348b392714a.json
Then /plugin install schedule-week@markdownregistry-xhdgv6ojr75qmndw in Claude Code. It installs git:20261009.4206a03, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add uplika/uplika-plugin/schedule-week@sha256:4f1d3d5558b98f67The line at the top of this page pins the label git:20261009.4206a03, 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_xhdgv6ojr75qmndw)
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/schedule-week 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 schedule-week from somewhere else? Ask it: where did my schedule-week 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 1 version of this file, committed on Oct 9, 2026.
Watch this file (sign in, one email per new version)
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/schedule-week/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 (8019 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_xhdgv6ojr75qmndw GET https://markdownregistry.com/api/v1/resolve?ref=uplika/uplika-plugin/schedule-week GET https://markdownregistry.com/api/v1/blob/4f1d3d5558b98f67e4c534db351a1e00f3e24d3e3f263503837f9348b392714a
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.