resource-extractor SKILL.md skillA
resource-extractor from bitnormie01/build-system is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bitnormie01/build-system/resource-extractor@git:20261024.f795b0aPins git:20261024.f795b0a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bitnormie01/build-system
- Path
resource-extractor/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261024.f795b0a, committed Oct 24, 2026
- First version recorded
- Jul 5, 2026
- Size
- 13,399 bytes
- Repository stars
- 4
- License
- MIT
Use this at the very START of a hackathon build — BEFORE idea-forge — to gather the event's full, accurate documentation ecosystem into one committed resource pack: rules, published judging criteria and weights, every track/bounty, each sponsor's SDK/protocol docs (with testnet package/contract addresses and entry points), prize structure, and prior winners/showcases. idea-forge then diverges and converges on REAL extracted sources instead of guesses, and the architect plans against accurate…
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
# Resource Extractor — Step 0a: the hackathon's docs, extracted accurately ## What this is The upstream-most step. Before idea-forge invents anything, this skill collects the hackathon's **inter-related documentation** — rules → tracks → sponsors → each sponsor's SDK/protocol docs → prior winners — into a **committed resource pack** the rest of the pipeline reads as ground truth. The whole kit's top residual risk is a strong model confidently building on *wrong* facts (a mis-read judging weight, a stale package address, a track it doesn't actually qualify for). This skill removes that risk by extracting the facts verbatim, with source URLs and fetch dates, before ideation begins. **Announce at start:** "I'm using the resource-extractor skill to pull this hackathon's rules, tracks, sponsor docs, and prior art into a committed resource pack before we ideate." ## The one output — a resource pack Write everything under `docs/resources/<YYYY-MM-DD>-<event-slug>/` **in the project repo**, then commit and push it (the project repo is the single source of truth — every downstream step syncs and …
Read the whole file at its exact version.
How to install
mdr add bitnormie01/build-system/resource-extractor@sha256:af40768497d2a754The line at the top of this page pins the label git:20261024.f795b0a, 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_qwcbzsjjptp23ucl)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 5, 2026 and Oct 24, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.f795b0a latest | 2026-10-24 | f795b0a | 13,399 B | A | view · diff |
| git:20260710.be104d3 | 2026-07-10 | be104d3 | 13,316 B | A | view · diff |
| git:20260710.31c2709 | 2026-07-10 | 31c2709 | 13,315 B | A | view · diff |
| git:20260710.401faad | 2026-07-10 | 401faad | 12,862 B | A | view · diff |
| git:20260705.5aa56d6 | 2026-07-05 | 5aa56d6 | 11,570 B | A | view |
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 (13399 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
bitnormie01/build-system · 4 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qwcbzsjjptp23ucl GET https://markdownregistry.com/api/v1/resolve?ref=bitnormie01/build-system/resource-extractor GET https://markdownregistry.com/api/v1/blob/af40768497d2a754eee5da2fc0cb7c98c0a071605088933ee861fd26e8886940
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.