booking-rules SKILL.md skillA
booking-rules from danmcinerney/orchflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add danmcinerney/orchflows/booking-rules@git:20261002.979492bPins git:20261002.979492b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- danmcinerney/orchflows
- Path
example-workflows/benchmaker/trials/benchmaking-benchmark/meta-tasks/calendar-skill/subject/booking-rules/skills/booking-rules/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261002.979492b, committed Oct 2, 2026
- Size
- 2,617 bytes
- Repository stars
- 125
- License
- MIT
Book a meeting into the team's calendar files under the booking policy. Use when asked to schedule, book or find a time for a meeting by editing the calendars/ and rooms/ files of a workspace that has request.json and policy.md.
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
# Booking rules How the calendar team books a meeting. `policy.md` in the workspace is the policy; this skill is how we apply it. ## The workspace - `request.json`: attendees, optional invitees, duration, window, granularity, preference and priority. - `calendars/<person>.json` and `rooms/<room>.json`: the entries of each person and room. A calendar also holds the person's `utc_offset` and `work_hours`; a room holds its `capacity` and `features`. - `policy.json` holds the rules and `policy.md` is generated from it. Read `policy.md`; never edit either. ## Rules we apply - Every required attendee must be inside their work hours, in their own `utc_offset`, and free. Optional invitees never restrict the time. - Start times lie on the request's granularity grid, counted from the start of the window, and the meeting ends inside the window. - **Buffers.** `buffer_minutes` in `policy.json` is a gap: keep at least that many minutes between the new meeting and every other entry on each required attendee's calendar, on both sides. - With rooms, book one that is free for the whole meeting and seats every required attendee. …
Read the whole file at its exact version.
How to install
mdr add danmcinerney/orchflows/booking-rules@sha256:91c61c574c6dd0c4The line at the top of this page pins the label git:20261002.979492b, 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_jetqfcpdrpyeh5sf)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 2, 2026.
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 (2617 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
danmcinerney/orchflows · 125 stars · license MIT · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jetqfcpdrpyeh5sf GET https://markdownregistry.com/api/v1/resolve?ref=danmcinerney/orchflows/booking-rules GET https://markdownregistry.com/api/v1/blob/91c61c574c6dd0c4c895c625beb7dd10b95c379d70e4fe52e7e896d40e722ed3
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.