gws-meeting-scheduler SKILL.md skillA
gws-meeting-scheduler from jackchuka/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jackchuka/skills/gws-meeting-scheduler@git:20260604.0da3398Pins git:20260604.0da3398 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jackchuka/skills
- Path
gws-meeting-scheduler/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260604.0da3398, committed Jun 4, 2026
- First version recorded
- Mar 11, 2026
- Size
- 5,085 bytes
- Repository stars
- 15
- License
- MIT
Schedule meetings between people using the `gws` CLI (Google Calendar). Use when the user wants to find a meeting time, schedule a meeting, check availability, or book time with someone. Triggers on requests like "schedule a meeting with X", "find time with Y", "book a 1:1", "when can I meet with Z", "set up a sync".
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
# Meeting Scheduler
Find mutual availability and create Google Calendar events using the `gws` CLI.
## Prerequisites
- `gws` CLI installed and authenticated
## Workflow
### 1. Resolve attendee email
If the user provides a name but no email, search past calendar events:
```bash
gws calendar events list --params '{"calendarId":"primary","q":"<name>","maxResults":10}'
```
Look at the `attendees` array in results to find the matching email. If multiple matches, ask the user to confirm.
### 2. Detect timezones
Detect each person's timezone by querying **their own calendar** directly. When you query a person's calendar via their email as `calendarId`, the API returns `start.dateTime` with that person's local UTC offset — this is the most reliable signal.
```bash
gws calendar events list --params '{"calendarId":"<user-email>","maxResults":10}'
gws calendar events list --params '{"calendarId":"<attendee-email>","maxResults":10}'
```
For each person:
- Look at `start.dateTime` on non-all-day events (skip events with only `start.date`)
- Extract the UTC offset (e.g., `-08:00`, `+09:00`) — this reflects their calendar's timezone
…Read the whole file at its exact version.
How to install
mdr add jackchuka/skills/gws-meeting-scheduler@sha256:22b2038b35c8446bThe line at the top of this page pins the label git:20260604.0da3398, 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_7bc7behmmfnzdhcf)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Mar 11, 2026 and Jun 4, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260604.0da3398 latest | 2026-06-04 | 0da3398 | 5,085 B | A | view · diff |
| git:20260421.19f33a5 | 2026-04-21 | 19f33a5 | 5,067 B | A | view · diff |
| git:20260321.fb3b945 | 2026-03-21 | fb3b945 | 5,054 B | A | view · diff |
| git:20260311.2835406 | 2026-03-11 | 2835406 | 5,000 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 (5085 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
jackchuka/skills · 15 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7bc7behmmfnzdhcf GET https://markdownregistry.com/api/v1/resolve?ref=jackchuka/skills/gws-meeting-scheduler GET https://markdownregistry.com/api/v1/blob/22b2038b35c8446b326e77fb594fc6fb13193b354855ca1c6e93632ef70dc0ff
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.