assignment-compliance-check SKILL.md skillA
assignment-compliance-check from pekral/cursor-rules is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pekral/cursor-rules/assignment-compliance-check@git:20260716.7828b68Pins git:20260716.7828b68 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pekral/cursor-rules
- Path
skills/assignment-compliance-check/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260716.7828b68, committed Jul 16, 2026
- First version recorded
- May 18, 2026
- Size
- 14,036 bytes
- Repository stars
- 12
- License
- MIT
Use when checking that the pull request implementation actually fulfills the business requirements stated in the linked issue or task. Returns a plain-language markdown block that is the Functional review half of the two-part CR output (`@rules/code-review/general.mdc` Two-part CR output — Technical & Functional review): a full checklist of every extracted acceptance criterion with its status (Met / Not met / Partial / Divergent) and an explicit Goal met: Yes/No verdict, rendered on every run…
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
## Constraints - Apply `@rules/php/core-standards.mdc` - Apply `@rules/git/general.mdc` - Apply `@rules/jira/general.mdc` - Apply `@rules/reports/general.mdc` — the **Assignment Compliance** markdown block this skill returns to the caller must be written in the language of the linked assignment (Czech issue / JIRA description → Czech block; English → English). Linked-task / PR URLs, author handles, and severity labels follow the rule's *Scope clarifications*. - The skill **must not** write any output to disk. It also **must not** publish anywhere itself — no `gh issue comment`, no `acli`, no JIRA / GitHub MCP write call. The skill returns either the assembled markdown block (on every run that has a linked tracker, including the affirmative report on a clean run) or a skip status (only when no linked tracker is detected) to the calling CR wrapper. The wrapper embeds the block into the **single consolidated linked-tracker comment** authored by `@skills/pr-summary/SKILL.md` (one comment per linked issue / JIRA ticket per CR run — see issue #498) **only when a block is returned**; on the skip status the wrapper embeds nothing and surfaces the status only on the PR comment summary… …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2rk7oldrmiwqn7hw/47b1e45d7fd55c7ea567ca46fc1543cdae9970cddc5b58935aac4530253c4abb.json
Then /plugin install assignment-compliance-check@markdownregistry-2rk7oldrmiwqn7hw in Claude Code. It installs git:20260716.7828b68, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add pekral/cursor-rules/assignment-compliance-check@sha256:47b1e45d7fd55c7eThe line at the top of this page pins the label git:20260716.7828b68, 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_2rk7oldrmiwqn7hw)
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 pekral/cursor-rules/assignment-compliance-check 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 assignment-compliance-check from somewhere else? Ask it: where did my assignment-compliance-check 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 May 18, 2026 and Jul 16, 2026, about one every 15 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260716.7828b68 latest | 2026-07-16 | 7828b68 | 14,036 B | A | view · diff |
| git:20260615.dcf1d43 | 2026-06-15 | dcf1d43 | 13,274 B | A | view · diff |
| git:20260602.a8f543f | 2026-06-02 | a8f543f | 12,987 B | A | view · diff |
| git:20260519.4fb0d1b | 2026-05-19 | 4fb0d1b | 11,869 B | A | view · diff |
| git:20260518.28cede7 | 2026-05-18 | 28cede7 | 11,168 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/assignment-compliance-check/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 (14036 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
pekral/cursor-rules · 12 stars · license MIT · pushed 2026-10-03 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_2rk7oldrmiwqn7hw GET https://markdownregistry.com/api/v1/resolve?ref=pekral/cursor-rules/assignment-compliance-check GET https://markdownregistry.com/api/v1/blob/47b1e45d7fd55c7ea567ca46fc1543cdae9970cddc5b58935aac4530253c4abb
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.