find-technician-slot

find-technician-slot is a skill for Claude Code from markmhendrickson/ateles. It costs 73 tokens per session (1,359 once invoked), scanned A, original, MIT.

A calendar search workflow for finding a one-hour appointment slot for a technician or repair visit. It checks Google Calendar and prefers times after a morning workout or between 4 and 6pm, normally from tomorrow through the next three weeks.

In plain words
What is it for?
It is for scheduling technicians, installers, repair visits, and similar appointments around existing calendar events.
Why use it?
It removes the need to scan the calendar manually while applying preferred times and the required gap after a workout.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit It is for scheduling technicians, installers, repair visits, and similar appointments around existing calendar events.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/markmhendrickson/ateles/find-technician-slot
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add markmhendrickson/ateles --skill find-technician-slot
Clone the repo
git clone --depth 1 https://github.com/markmhendrickson/ateles

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for find-technician-slot

README.md
[![agentmods](https://agentmods.dev/badge/skills/markmhendrickson/ateles/find-technician-slot/github.svg)](https://agentmods.dev/skills/markmhendrickson/ateles/find-technician-slot)
Your own site
<a href="https://agentmods.dev/skills/markmhendrickson/ateles/find-technician-slot"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/find-technician-slot/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for find-technician-slot

Your own site · 80×15
<a href="https://agentmods.dev/skills/markmhendrickson/ateles/find-technician-slot"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/find-technician-slot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,359 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.01359
Opus 5 $0.00036 $0.00679
Sonnet 5 $0.00015 $0.00272
Haiku 4.5 $0.00007 $0.00136

Measured 10d ago against content hash bb6d41f8c3da, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

find-technician-slot scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/find-technician-slot/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Find Technician Appointment Slot

Finds available times for a technician (or similar) appointment by checking the user's calendar. Prefers morning right after workout (gym, yoga, strength training, or similar) or 4–6pm. Uses the project-0-ateles-google-calendar MCP; call its tools directly (do not list descriptor files for this workflow).

Defaults

  • Window: Tomorrow through the next 3 weeks (≈21 days). If the user specifies a range (e.g. "next 2 weeks", "between March 1 and March 15"), use that instead.
  • Timezone: Europe/Madrid (Barcelona). Override only if the user specifies another timezone.
  • Appointment length: 1 hour unless the user says otherwise (e.g. "2 hour window").
  • Buffer after workout: Prefer slots starting 30 minutes after a morning workout ends.

Workflow

  1. Get current time

    • Call get_current_time with timeZone: "Europe/Madrid" so all later ranges use the correct "today" and "tomorrow".
  2. Set time range

    • timeMin: Start of tomorrow (00:00) in Europe/Madrid.
    • timeMax: End of day at (today + 21 days), or the user-specified end date.
    • Format: YYYY-MM-DDTHH:mm:ss (no Z); the MCP uses the timeZone parameter when needed.
  3. Get free/busy

    • Call get_freebusy with:
      • calendars: [{ "id": "primary" }] (or use calendar IDs from list_calendars if the user has multiple and you need to aggregate).
      • timeMin, timeMax from step 2.
      • timeZone: "Europe/Madrid".
    • The response lists busy periods per calendar. Free slots are the gaps: between timeMin and the first busy start, between consecutive busy end and next busy start, and between last busy end and timeMax. Each gap that is at least the appointment length (e.g. 1 hour) is a candidate slot.
  4. Find morning workouts

    • Call search_events (or list_events) with the same timeMin/timeMax/timeZone.
    • Search for workout-related events by running separate searches for: "gym", "yoga", "strength", "strength training", and "workout" (or "training"). Merge results and deduplicate by event id. This catches gym, yoga, strength training, and similar descriptors.
    • Collect each event's end time; "first thing after workout" = first free slot that starts ≥ 30 minutes after a workout end (e.g. workout ends 8:30 → prefer slots from 9:00 onward that day).
    • When labelling slots, use a short label from the event summary when possible (e.g. "After yoga", "After strength", "After gym").

Read the full file on GitHub · 89 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 89 lines · 73 tokens per session scan A bb6d41f8c3da

Subscribe to this mod's changes

find-technician-slot is a skill published in the GitHub repository markmhendrickson/ateles (6 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,359 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.