Add Calendly and my-contacts skill templates

Calendly skill teaches the agent to fetch scheduled events and invitee
details via the Calendly REST API using a Personal Access Token.

my-contacts skill provides contact lookup from a local JSON file,
enabling name-based WhatsApp messaging and phone/email lookups.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: sanchitmonga22

skills/calendly/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: calendly
+description: Calendly API for listing scheduled events and invitee details.
+homepage: https://developer.calendly.com
+metadata:
+  {
+    "openclaw":
+      {
+        "emoji": "📅",
+        "requires": { "env": ["CALENDLY_API_KEY"] },
+        "primaryEnv": "CALENDLY_API_KEY",
+      },
+  }
+---
+
+# calendly
+
+Use the Calendly API to list scheduled events, get event details, and fetch invitee information.
+Authentication uses a Personal Access Token (PAT) via the `CALENDLY_API_KEY` environment variable.
+
+Base URL: `https://api.calendly.com`
+
+## Setup
+
+1. Go to Calendly > Settings > Integrations > API & Webhooks.
+2. Click "Get a token now" and copy the PAT.
+3. The token is injected as `$CALENDLY_API_KEY`.
+
+## Step 1 — Get your user URI (needed for all other calls)
+
+```bash
+curl -s --request GET \
+  --url https://api.calendly.com/users/me \
+  --header "Authorization: Bearer $CALENDLY_API_KEY" \
+  --header 'Content-Type: application/json'
+```
+
+Response contains `resource.uri` (e.g. `https://api.calendly.com/users/AAAA...`) — use this as the `user` parameter for listing events.
+
+## Step 2 — List scheduled events
+
+```bash
+curl -s --request GET \
+  --url 'https://api.calendly.com/scheduled_events?user=USER_URI&min_start_time=2026-02-13T00:00:00.000000Z&max_start_time=2026-02-14T00:00:00.000000Z&status=active&sort=start_time:asc&count=20' \
+  --header "Authorization: Bearer $CALENDLY_API_KEY" \
+  --header 'Content-Type: application/json'
+```
+
+Replace `USER_URI` with the full URI from Step 1. Adjust `min_start_time` and `max_start_time` for the desired date range (ISO 8601 UTC).
+
+Response fields per event in `collection[]`:
+
+- `uri` — event URI (contains UUID)
+- `name` — event type name (e.g. "30 Minute Meeting")
+- `start_time` / `end_time` — ISO 8601 UTC
+- `status` — `active` or `canceled`
+- `location.type` and `location.location` — meeting location
+- `invitees_counter.total` — number of invitees
+- `event_guests[].email` — guest emails
+
+## Step 3 — Get invitees for a specific event
+
+Extract the event UUID from the event URI (last path segment), then:
+
+```bash
+curl -s --request GET \
+  --url 'https://api.calendly.com/scheduled_events/EVENT_UUID/invitees?status=active&count=20' \
+  --header "Authorization: Bearer $CALENDLY_API_KEY" \
+  --header 'Content-Type: application/json'
+```
+
+Response fields per invitee in `collection[]`:
+
+- `name` — invitee full name
+- `first_name` / `last_name`
+- `email` — invitee email
+- `status` — `active` or `canceled`
+- `timezone` — invitee timezone
+- `questions_and_answers[]` — custom question responses
+- `text_reminder_number` — phone number (if provided)
+- `cancel_url` / `reschedule_url` — links for the invitee
+
+## Step 4 — List event types (scheduling links)
+
+```bash
+curl -s --request GET \
+  --url 'https://api.calendly.com/event_types?user=USER_URI&active=true&count=20' \
+  --header "Authorization: Bearer $CALENDLY_API_KEY" \
+  --header 'Content-Type: application/json'
+```
+
+Response fields per event type in `collection[]`:
+
+- `uri` — event type URI
+- `name` — display name (e.g. "30 Minute Meeting")
+- `slug` — URL slug
+- `scheduling_url` — full booking link
+- `duration` — duration in minutes
+- `active` — whether this event type is active
+
+## Common workflows
+
+**Fetch today's meetings:**
+
+1. `GET /users/me` → extract `resource.uri`
+2. `GET /scheduled_events?user=<uri>&min_start_time=<today_start>&max_start_time=<today_end>&status=active`
+
+**Get details about who booked a meeting:**
+
+1. List events (above)
+2. For each event, `GET /scheduled_events/<uuid>/invitees`
+
+**Share a booking link:**
+
+1. `GET /event_types?user=<uri>&active=true`
+2. Use `scheduling_url` from the desired event type
+
+## Notes
+
+- All times are in UTC (ISO 8601 with microseconds: `2026-02-13T00:00:00.000000Z`).
+- The free plan supports reading events and invitees. Creating events via API requires a paid plan.
+- Pagination: if `pagination.next_page` is not null, fetch that URL for more results.
+- Rate limit: 100 requests per minute per token.
+- Always use `--header "Authorization: Bearer $CALENDLY_API_KEY"` for auth.

skills/my-contacts/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: my-contacts
+description: Look up contact information (phone, email, notes) from a local JSON file.
+metadata: { "openclaw": { "emoji": "📇", "always": true } }
+---
+
+# my-contacts
+
+Look up contact details from the local contacts file.
+
+## Usage
+
+Read the contacts file to find a person's phone number, email, or other details:
+
+```bash
+cat ~/.openclaw/skills/my-contacts/contacts.json
+```
+
+The file contains a JSON object with a `contacts` array. Each contact has:
+
+- `name` — full name
+- `phone` — phone number (with country code, e.g. +1...)
+- `email` — email address
+- `notes` — any extra context (relationship, company, etc.)
+
+## When to use
+
+- User asks "what's [name]'s phone number / email?"
+- User says "send a message to [name]" — look up their number first
+- User says "call [name]" or "text [name]"
+- User wants to send a WhatsApp message to a contact by name
+
+## Example
+
+If the user says "send a WhatsApp message to John", read the contacts file, find John's entry, and use his phone number.

skills/my-contacts/contacts.example.json

@@ -0,0 +1,16 @@
+{
+  "contacts": [
+    {
+      "name": "Jane Doe",
+      "phone": "+15551234567",
+      "email": "jane@example.com",
+      "notes": "Friend, works at Acme Corp"
+    },
+    {
+      "name": "John Smith",
+      "phone": "+15559876543",
+      "email": "john@example.com",
+      "notes": "College roommate"
+    }
+  ]
+}