competition-submission-checker SKILL.md skillA
competition-submission-checker from bg-szy/top-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bg-szy/top-skills/competition-submission-checker@v2.0Pins v2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bg-szy/top-skills
- Path
skills/agent-skills/competition-submission-checker/SKILL.md- Versions recorded
- 5
- Latest version
- v2.0, committed Nov 11, 2026
- First version recorded
- Jul 12, 2026
- Size
- 4,142 bytes
- Repository stars
- 6
- License
- a license file GitHub does not identify
Validate GCI competition predictions and notebook outputs against expected schema, metric, and submission constraints.
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
# Competition Submission Checker Use this skill for the folder `04. Competition (due Jun 12th 11AM UTC)` or any NFL Draft prediction submission work. ## Context Source Load current competition facts from Serena memory first. If Serena is unavailable, use `docs/memory-bank/progress.md`, then verify against the current competition README or notebook before final advice. Snapshot from project onboarding: - training target: `Drafted` - metric reported in audit: AUC - `train.csv`: 2781 rows x 16 columns - `test.csv`: 696 rows x 15 columns - `sample_submission.csv`: 696 rows x 2 columns - deadline needs verification because folder and README dates may differ ## Workflow 1. Read `AGENTS.md` and relevant Serena memory or `docs/memory-bank/` fallback context. 2. Verify the current README/notebook instructions for columns, metric, and deadline before final advice. 3. Compare output columns to `sample_submission.csv`. 4. Confirm row count, ID alignment, duplicate IDs, missing predictions, numeric prediction range, and file encoding. 5. Check that target leakage is not used. 6. If evaluating locally, use AUC-compatible probabilities, not hard labels …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_6vl45mgok4wodzbh/40e30e0d4e4a23f3d5ba993f836ddbb35f8a573460afd2357f6469f105fc26fa.json
Then /plugin install competition-submission-checker@markdownregistry-6vl45mgok4wodzbh in Claude Code. It installs v2.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add bg-szy/top-skills/competition-submission-checker@sha256:40e30e0d4e4a23f3The line at the top of this page pins the label v2.0, 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_6vl45mgok4wodzbh)
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 bg-szy/top-skills/competition-submission-checker 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 competition-submission-checker from somewhere else? Ask it: where did my competition-submission-checker 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 Jul 12, 2026 and Nov 11, 2026, about one every 31 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.0 latest | 2026-11-11 | b533f7f | 4,142 B | A | view · diff |
| v2.0 | 2026-08-25 | b67c05b | 4,142 B | A | view · diff |
| v2.0 | 2026-08-15 | 7b5e773 | 4,142 B | A | view · diff |
| v2.0 | 2026-07-30 | 5be6365 | 4,142 B | A | view · diff |
| v1.3 | 2026-07-12 | 94eb15d | 4,339 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/competition-submission-checker/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 (4142 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
bg-szy/top-skills · 6 stars · license a license file GitHub does not identify · pushed 2026-11-15 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_6vl45mgok4wodzbh GET https://markdownregistry.com/api/v1/resolve?ref=bg-szy/top-skills/competition-submission-checker GET https://markdownregistry.com/api/v1/blob/40e30e0d4e4a23f3d5ba993f836ddbb35f8a573460afd2357f6469f105fc26fa
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.