schedule-extractor SKILL.md skillA
schedule-extractor from dleerdefi/claude-code-construction is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dleerdefi/claude-code-construction/schedule-extractor@git:20261016.c156778Pins git:20261016.c156778 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dleerdefi/claude-code-construction
- Path
skills/schedule-extractor/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261016.c156778, committed Oct 16, 2026
- First version recorded
- Oct 12, 2026
- Size
- 21,256 bytes
- Repository stars
- 44
- License
- MIT
Extract tabular schedule data from construction drawings — door, window, finish, fixture, panel schedules — and output to Excel. Triggers: 'door schedule', 'extract schedule', 'schedule to Excel', 'panel schedule'.
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 Extractor
Extracts tabular schedule data embedded in drawing sheets or spec pages and outputs structured Excel files. Schedules are typically one element among many on a sheet — or the entire sheet may be a schedule.
## First: the mode (both workflows)
Before extracting or reconciling, read `.construction/project.yaml`. Present and readable means AgentCM mode: note its `contract_version` and follow `${CLAUDE_PLUGIN_ROOT}/reference/agentcm-mode.md`. Absent means flat-file mode. A listing that shows the file, or `.construction/database.yaml` alone, does not decide it: read the file.
## Workflow
```
Extraction Progress:
- [ ] Step 1: Discover schedule locations
- [ ] Step 2: Isolate (crop) the schedule region
- [ ] Step 3: Extract structured data (pdfplumber + vision)
- [ ] Step 4: Validate and clean data
- [ ] Step 5: Output to Excel
- [ ] Step 6: Ingest to AgentCM (AgentCM mode)
- [ ] Step 7: Write a finding
```
### Step 1: Discover Schedule Locations
Use a multi-source discovery approach, checking all available sources:
#### Source A — Sheet titles in sheet index (primary, most reliable)
…Read the whole file at its exact version.
How to install
mdr add dleerdefi/claude-code-construction/schedule-extractor@sha256:58e414a8f7c04cfcThe line at the top of this page pins the label git:20261016.c156778, 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_hbqzao5fiquvntr4)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 12, 2026 and Oct 16, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.c156778 latest | 2026-10-16 | c156778 | 21,256 B | A | view · diff |
| git:20261016.34d1544 | 2026-10-16 | 34d1544 | 21,279 B | A | view · diff |
| git:20261012.a0d5b44 | 2026-10-12 | a0d5b44 | 21,134 B | A | view · diff |
| git:20261012.f4852dc | 2026-10-12 | f4852dc | 20,846 B | A | view · diff |
| git:20261012.3e60614 | 2026-10-12 | 3e60614 | 18,405 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 (21256 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
dleerdefi/claude-code-construction · 44 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hbqzao5fiquvntr4 GET https://markdownregistry.com/api/v1/resolve?ref=dleerdefi/claude-code-construction/schedule-extractor GET https://markdownregistry.com/api/v1/blob/58e414a8f7c04cfc5b5f02d8c0de611c1d65afc2309c0262415a4a6297fd421c
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.