[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75DQQM9FE7HMXQJESHCV9N2":3,"skill-same:01M75DQQM9FE7HMXQJESHCV9N2":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M75DQQM9FE7HMXQJESHCV9N2","metra",null,"Chicago Metra commuter rail — real-time train arrivals, vehicle tracking, service alerts, and schedule info for all 11 Metra lines serving the Chicago metropolitan area. Use when the user asks about Metra trains, Chicago commuter rail, or specific Metra lines and stations.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbrianleach\u002Fmetra\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: metra\ndescription: Chicago Metra commuter rail — real-time train arrivals, vehicle tracking, service alerts, and schedule info for all 11 Metra lines serving the Chicago metropolitan area. Use when the user asks about Metra trains, Chicago commuter rail, or specific Metra lines and stations.\nhomepage: \"https:\u002F\u002Fgithub.com\u002Fbrianleach\u002Fmetra-skill\"\nlicense: MIT\nmetadata:\n  clawhub:\n    emoji: \"🚂\"\n    tags: [transit, chicago, metra, transportation, commuter-rail, train, schedule]\n    requires:\n      bins: [\"node\", \"unzip\"]\n      env: [\"METRA_API_KEY\"]\n    files: [\"scripts\u002Fmetra.mjs\", \"scripts\u002Fgtfs-realtime.proto\"]\n    install:\n      - id: npm-deps\n        kind: shell\n        command: \"npm install --prefix $SKILL_DIR\"\n        label: \"Install Node.js dependencies (protobufjs)\"\n---\n\n# Chicago Metra Commuter Rail\n\nReal-time Chicago Metra commuter rail data — train arrivals (GTFS-RT protobuf), vehicle positions, service alerts, schedule info, and fare calculation for all 11 Metra lines serving the six-county northeastern Illinois region. Requires a free API key for all feeds.\n\n## When to Use\n\n- User asks about Metra, Chicago commuter rail, or commuter trains in Chicago\n- User asks \"when is the next train\" in a Chicago suburban context\n- User mentions specific Metra lines: BNSF, UP-N, UP-NW, UP-W, MD-N, MD-W, ME (Metra Electric), RI (Rock Island), NCS, HC (Heritage Corridor), SWS (SouthWest Service)\n- User mentions specific Metra stations: Union Station, Ogilvie, Millennium Station, LaSalle Street, Naperville, Aurora, Downers Grove, Evanston, Highland Park, etc.\n- User asks about Metra service alerts, delays, or construction\n- User asks about Metra fares, zones, monthly passes, Ventra\n- User asks about Chicago train schedules (distinguish from CTA \"L\" trains — Metra is commuter rail)\n\n### When NOT to Use\n\n- User asks about CTA trains (the \"L\"), CTA buses, or Pace buses — those are separate systems\n- User asks about Amtrak long-distance trains at Union Station\n\n## Data Sources\n\nMetra uses standard GTFS-RT protobuf feeds served from a single base URL with Bearer token authentication. No proprietary extensions — clean standard GTFS-RT.\n\n### GTFS Realtime Feeds (Protobuf, requires `METRA_API_KEY`)\n\nGet a free key at: https:\u002F\u002Fmetra.com\u002Fdevelopers\n\n| Feed | Endpoint | Description |\n|------|----------|-------------|\n| Trip Updates | `GET \u002Fgtfs\u002Fpublic\u002Ftripupdates` | Real-time arrival\u002Fdeparture predictions |\n| Vehicle Positions | `GET \u002Fgtfs\u002Fpublic\u002Fpositions` | GPS locations of active trains |\n| Alerts | `GET \u002Fgtfs\u002Fpublic\u002Falerts` | Service alerts, delays, construction notices |\n\nBase URL: `https:\u002F\u002Fgtfspublic.metrarr.com`\n\nAuthentication: `Authorization: Bearer {METRA_API_KEY}` header.\n\nData updates every 30 seconds. No need to poll more frequently.\n\n### GTFS Static Feed\n\n| Feed | URL |\n|------|-----|\n| GTFS Static (zip) | `https:\u002F\u002Fschedules.metrarail.com\u002Fgtfs\u002Fschedule.zip` |\n| Published timestamp | `https:\u002F\u002Fschedules.metrarail.com\u002Fgtfs\u002Fpublished.txt` |\n\nStatic schedule updates regularly (sometimes within 24 hours). New scheduled updates publish at 3:00 AM.\n\n### Important Notes from Metra\n\n- If realtime data is unavailable for a trip, assume the static schedule is correct\n- Vehicle positions may drop when trains are underground or at terminals (GPS loss)\n- Trip updates may be provided hours in advance for annulled or added trains\n- If an alert is in the feed, it's active; if it's not, it's no longer active (regardless of active_period)\n\n## Implementation\n\n### Script: `scripts\u002Fmetra.mjs`\n\nMain entry point. Supports these commands:\n\n```bash\n# Train arrivals\nnode scripts\u002Fmetra.mjs arrivals --station \"Union Station\"\nnode scripts\u002Fmetra.mjs arrivals --station \"Naperville\" --line BNSF\nnode scripts\u002Fmetra.mjs arrivals --station \"Ogilvie\"\nnode scripts\u002Fmetra.mjs arrivals --station \"Millennium Station\" --line ME\n\n# Vehicle tracking\nnode scripts\u002Fmetra.mjs vehicles --line BNSF\nnode scripts\u002Fmetra.mjs vehicles --line UP-N\nnode scripts\u002Fmetra.mjs vehicles --line ME\n\n# Service alerts\nnode scripts\u002Fmetra.mjs alerts\nnode scripts\u002Fmetra.mjs alerts --line BNSF\nnode scripts\u002Fmetra.mjs alerts --line RI\n\n# Routes and stops\nnode scripts\u002Fmetra.mjs routes\nnode scripts\u002Fmetra.mjs stops --search \"downers grove\"\nnode scripts\u002Fmetra.mjs stops --line BNSF\nnode scripts\u002Fmetra.mjs stops --near 41.8781,-87.6298\nnode scripts\u002Fmetra.mjs route-info --line UP-NW\n\n# Fares\nnode scripts\u002Fmetra.mjs fares\nnode scripts\u002Fmetra.mjs fares --from \"Union Station\" --to \"Naperville\"\n\n# Schedule\nnode scripts\u002Fmetra.mjs schedule --station \"Naperville\"\nnode scripts\u002Fmetra.mjs schedule --station \"Ogilvie\" --line UP-N\n\n# Maintenance\nnode scripts\u002Fmetra.mjs refresh-gtfs\n```\n\n### Setup: API Key\n\nAll Metra feeds require authentication:\n\n1. Register for a free key at https:\u002F\u002Fmetra.com\u002Fdevelopers\n2. Set environment variable: `METRA_API_KEY`\n\n### Setup: GTFS Static Data\n\nOn first use, run `node scripts\u002Fmetra.mjs refresh-gtfs` to download and extract the static GTFS data (routes, stops, schedules) to `~\u002F.metra\u002Fgtfs\u002F`. Refresh periodically or when Metra updates their schedule.\n\n### Metra Lines Reference\n\n| Line Code | Line Name | Color | Downtown Terminal | Outer Terminal |\n|-----------|-----------|-------|-------------------|----------------|\n| BNSF | BNSF Railway | Orange | Union Station (CUS) | Aurora |\n| ME | Metra Electric | Teal | Millennium Station | University Park \u002F South Chicago \u002F Blue Island |\n| HC | Heritage Corridor | Purple | Union Station (CUS) | Joliet |\n| MD-N | Milwaukee District North | Light Green | Union Station (CUS) | Fox Lake |\n| MD-W | Milwaukee District West | Light Green | Union Station (CUS) | Elburn \u002F Big Timber |\n| NCS | North Central Service | Gold | Union Station (CUS) | Antioch |\n| RI | Rock Island | Red | LaSalle Street Station | Joliet |\n| SWS | SouthWest Service | Dark Purple | Union Station (CUS) | Manhattan |\n| UP-N | Union Pacific North | Dark Green | Ogilvie Transportation Center (OTC) | Kenosha |\n| UP-NW | Union Pacific Northwest | Blue | Ogilvie Transportation Center (OTC) | Harvard \u002F McHenry |\n| UP-W | Union Pacific West | Blue | Ogilvie Transportation Center (OTC) | Elburn |\n\n### Downtown Terminal Stations\n\n- **Chicago Union Station (CUS)** — Zone 1 — BNSF, HC, MD-N, MD-W, NCS, SWS\n- **Ogilvie Transportation Center (OTC)** — Zone 1 — UP-N, UP-NW, UP-W\n- **LaSalle Street Station** — Zone 1 — RI\n- **Millennium Station** — Zone 1 — ME\n\n### Metra Fares Reference (4-Zone System, effective Feb 2024)\n\n| Ticket Type | Zones 1-2 | Zones 1-2-3 | Zones 1-2-3-4 | Zones 2-3-4 (no downtown) |\n|-------------|-----------|-------------|---------------|---------------------------|\n| One-Way | $3.75 | $5.50 | $6.75 | $3.75 |\n| Day Pass | $7.50 | $11.00 | $13.50 | $7.50 |\n| Day Pass 5-Pack | $35.75 | $52.25 | $64.25 | $35.75 |\n| Monthly Pass | $75.00 | $110.00 | $135.00 | $75.00 |\n\nSpecial Passes:\n- Saturday\u002FSunday\u002FHoliday Day Pass: $7.00 (systemwide)\n- Weekend Pass (Ventra app only): $10.00 (systemwide)\n- Regional Connect Pass (with Monthly): $30.00 (adds CTA + Pace)\n- Onboard Surcharge (cash on train): $5.00\n\nMonthly Passes are valid for unlimited rides on weekdays between selected zones and systemwide on weekends.\n\n### Tips for Users\n\n- Metra uses **inbound** (toward downtown Chicago) and **outbound** (away from downtown) for directions\n- Train numbers matter — Metra riders often know their train by number (e.g., \"the 7:42 BNSF\" or \"Train 1252\")\n- Different lines use different downtown terminals — always note which terminal\n- Peak trains run during rush hours; off-peak and weekend service is less frequent\n- If real-time data is unavailable, the schedule command shows static times\n- Use `--line` to filter by specific Metra line code (BNSF, UP-N, etc.)\n\n### Error Handling\n\n- If `METRA_API_KEY` is not set, all commands print a helpful message with the signup URL\n- Invalid station names show \"No matching station found\" with a suggestion to use stops --search\n- No real-time data available → fall back to static schedule with a note\n- Network errors produce friendly messages\n- GPS dropout for vehicle positions → note that train may be underground or at terminal\n\n### Response Formatting\n\nWhen presenting transit info to the user:\n- Lead with the most actionable info (next arrival time, active alerts)\n- Show line name AND train number (e.g., \"BNSF Train 1252 inbound\")\n- Show times in 12-hour format with AM\u002FPM\n- For arrivals: show both real-time ETA and scheduled time when available\n- Always note the downtown terminal for the line\n- If there are active service alerts for the line being queried, mention them\n\n## External Endpoints\n\n| Endpoint | Data Sent | Data Received |\n|----------|-----------|---------------|\n| `gtfspublic.metrarr.com\u002Fgtfs\u002Fpublic\u002Ftripupdates` | API key (Bearer header, HTTPS) | Trip updates (Protobuf) |\n| `gtfspublic.metrarr.com\u002Fgtfs\u002Fpublic\u002Fpositions` | API key (Bearer header, HTTPS) | Vehicle positions (Protobuf) |\n| `gtfspublic.metrarr.com\u002Fgtfs\u002Fpublic\u002Falerts` | API key (Bearer header, HTTPS) | Service alerts (Protobuf) |\n| `schedules.metrarail.com\u002Fgtfs\u002Fschedule.zip` | None (GET only) | GTFS static data (ZIP) |\n| `schedules.metrarail.com\u002Fgtfs\u002Fpublished.txt` | None (GET only) | Schedule publish timestamp (text) |\n\nAll API calls use HTTPS. The API key is passed as a Bearer token in the Authorization header. No other user data is transmitted.\n\n## Security & Privacy\n\n- **API key required** — All GTFS-RT feeds require a free developer key passed as a Bearer token in the Authorization header\n- **No user data transmitted** — Requests contain only the API key; no personal information\n- **Local storage only** — GTFS static data is cached locally at `~\u002F.metra\u002Fgtfs\u002F`; no data is written elsewhere\n- **No telemetry** — This skill does not phone home or collect usage data\n- **Input handling** — Stop names and route IDs from user input are used only for local filtering, never interpolated into shell commands\n\n## Trust Statement\n\nThis skill reads publicly available transit data from Metra's official GTFS-RT feeds. The API key is used only for Metra API authentication. The skill does not access, store, or transmit any personal information beyond the API key configured by the user.\n","# Chicago Metra Commuter Rail\n\nReal-time Chicago Metra commuter rail data — train arrivals (GTFS-RT protobuf), vehicle positions, service alerts, schedule info, and fare calculation for all 11 Metra lines serving the six-county northeastern Illinois region. Requires a free API key for all feeds.\n\n## When to Use\n\n- User asks about Metra, Chicago commuter rail, or commuter trains in Chicago\n- User asks \"when is the next train\" in a Chicago suburban context\n- User mentions specific Metra lines: BNSF, UP-N, UP-NW, UP-W, MD-N, MD-W, ME (Metra Electric), RI (Rock Island), NCS, HC (Heritage Corridor), SWS (SouthWest Service)\n- User mentions specific Metra stations: Union Station, Ogilvie, Millennium Station, LaSalle Street, Naperville, Aurora, Downers Grove, Evanston, Highland Park, etc.\n- User asks about Metra service alerts, delays, or construction\n- User asks about Metra fares, zones, monthly passes, Ventra\n- User asks about Chicago train schedules (distinguish from CTA \"L\" trains — Metra is commuter rail)\n\n### When NOT to Use\n\n- User asks about CTA trains (the \"L\"), CTA buses, or Pace buses — those are separate systems\n- User asks about Amtrak long-distance trains at Union Station\n\n## Data Sources\n\nMetra uses standard GTFS-RT protobuf feeds served from a single base URL with Bearer token authentication. No proprietary extensions — clean standard GTFS-RT.\n\n### GTFS Realtime Feeds (Protobuf, requires `METRA_API_KEY`)\n\nGet a free key at: https:\u002F\u002Fmetra.com\u002Fdevelopers\n\n| Feed | Endpoint | Description |\n|------|----------|-------------|\n| Trip Updates | `GET \u002Fgtfs\u002Fpublic\u002Ftripupdates` | Real-time arrival\u002Fdeparture predictions |\n| Vehicle Positions | `GET \u002Fgtfs\u002Fpublic\u002Fpositions` | GPS locations of active trains |\n| Alerts | `GET \u002Fgtfs\u002Fpublic\u002Falerts` | Service alerts, delays, construction notices |\n\nBase URL: `https:\u002F\u002Fgtfspublic.metrarr.com`\n\nAuthentication: `Authorization: Bearer {METRA_API_KEY}` header.\n\nData updates every 30 seconds. No need to poll more frequently.\n\n### GTFS Static Feed\n\n| Feed | URL |\n|------|-----|\n| GTFS Static (zip) | `https:\u002F\u002Fschedules.metrarail.com\u002Fgtfs\u002Fschedule.zip` |\n| Published timestamp | `https:\u002F\u002Fschedules.metrarail.com\u002Fgtfs\u002Fpublished.txt` |\n\nStatic schedule updates regularly (sometimes within 24 hours). New scheduled updates publish at 3:00 AM.\n\n### Important Notes from Metra\n\n- If realtime data is unavailable for a trip, assume the static schedule is correct\n- Vehicle positions may drop when trains are underground or at terminals (GPS loss)\n- Trip updates may be provided hours in advance for annulled or added trains\n- If an alert is in the feed, it's active; if it's not, it's no longer active (regardless of active_period)\n\n## Implementation\n\n### Script: `scripts\u002Fmetra.mjs`\n\nMain entry point. Supports these commands:\n\n```bash\n# Train arrivals\nnode scripts\u002Fmetra.mjs arrivals --station \"Union Station\"\nnode scripts\u002Fmetra.mjs arrivals --station \"Naperville\" --line BNSF\nnode scripts\u002Fmetra.mjs arrivals --station \"Ogilvie\"\nnode scripts\u002Fmetra.mjs arrivals --station \"Millennium Station\" --line ME\n\n# Vehicle tracking\nnode scripts\u002Fmetra.mjs vehicles --line BNSF\nnode scripts\u002Fmetra.mjs vehicles --line UP-N\nnode scripts\u002Fmetra.mjs vehicles --line ME\n\n# Service alerts\nnode scripts\u002Fmetra.mjs alerts\nnode scripts\u002Fmetra.mjs alerts --line BNSF\nnode scripts\u002Fmetra.mjs alerts --line RI\n\n# Routes and stops\nnode scripts\u002Fmetra.mjs routes\nnode scripts\u002Fmetra.mjs stops --search \"downers grove\"\nnode scripts\u002Fmetra.mjs stops --line BNSF\nnode scripts\u002Fmetra.mjs stops --near 41.8781,-87.6298\nnode scripts\u002Fmetra.mjs route-info --line UP-NW\n\n# Fares\nnode scripts\u002Fmetra.mjs fares\nnode scripts\u002Fmetra.mjs fares --from \"Union Station\" --to \"Naperville\"\n\n# Schedule\nnode scripts\u002Fmetra.mjs schedule --station \"Naperville\"\nnode scripts\u002Fmetra.mjs schedule --station \"Ogilvie\" --line UP-N\n\n# Maintenance\nnode scripts\u002Fmetra.mjs refresh-gtfs\n```\n\n### Setup: API Key\n\nAll Metra feeds require authentication:\n\n1. Register for a free key at https:\u002F\u002Fmetra.com\u002Fdevelopers\n2. Set environment variable: `METRA_API_KEY`\n\n### Setup: GTFS Static Data\n\nOn first use, run `node scripts\u002Fmetra.mjs refresh-gtfs` to download and extract the static GTFS data (routes, stops, schedules) to `~\u002F.metra\u002Fgtfs\u002F`. Refresh periodically or when Metra updates their schedule.\n\n### Metra Lines Reference\n\n| Line Code | Line Name | Color | Downtown Terminal | Outer Terminal |\n|-----------|-----------|-------|-------------------|----------------|\n| BNSF | BNSF Railway | Orange | Union Station (CUS) | Aurora |\n| ME | Metra Electric | Teal | Millennium Station | University Park \u002F South Chicago \u002F Blue Island |\n| HC | Heritage Corridor | Purple | Union Station (CUS) | Joliet |\n| MD-N | Milwaukee District North | Light Green | Union Station (CUS) | Fox Lake |\n| MD-W | Milwaukee District West | Light Green | Union Station (CUS) | Elburn \u002F Big Timber |\n| NCS | North Central Service | Gold | Union Station (CUS) | Antioch |\n| RI | Rock Island | Red | LaSalle Street Station | Joliet |\n| SWS | SouthWest Service | Dark Purple | Union Station (CUS) | Manhattan |\n| UP-N | Union Pacific North | Dark Green | Ogilvie Transportation Center (OTC) | Kenosha |\n| UP-NW | Union Pacific Northwest | Blue | Ogilvie Transportation Center (OTC) | Harvard \u002F McHenry |\n| UP-W | Union Pacific West | Blue | Ogilvie Transportation Center (OTC) | Elburn |\n\n### Downtown Terminal Stations\n\n- **Chicago Union Station (CUS)** — Zone 1 — BNSF, HC, MD-N, MD-W, NCS, SWS\n- **Ogilvie Transportation Center (OTC)** — Zone 1 — UP-N, UP-NW, UP-W\n- **LaSalle Street Station** — Zone 1 — RI\n- **Millennium Station** — Zone 1 — ME\n\n### Metra Fares Reference (4-Zone System, effective Feb 2024)\n\n| Ticket Type | Zones 1-2 | Zones 1-2-3 | Zones 1-2-3-4 | Zones 2-3-4 (no downtown) |\n|-------------|-----------|-------------|---------------|---------------------------|\n| One-Way | $3.75 | $5.50 | $6.75 | $3.75 |\n| Day Pass | $7.50 | $11.00 | $13.50 | $7.50 |\n| Day Pass 5-Pack | $35.75 | $52.25 | $64.25 | $35.75 |\n| Monthly Pass | $75.00 | $110.00 | $135.00 | $75.00 |\n\nSpecial Passes:\n- Saturday\u002FSunday\u002FHoliday Day Pass: $7.00 (systemwide)\n- Weekend Pass (Ventra app only): $10.00 (systemwide)\n- Regional Connect Pass (with Monthly): $30.00 (adds CTA + Pace)\n- Onboard Surcharge (cash on train): $5.00\n\nMonthly Passes are valid for unlimited rides on weekdays between selected zones and systemwide on weekends.\n\n### Tips for Users\n\n- Metra uses **inbound** (toward downtown Chicago) and **outbound** (away from downtown) for directions\n- Train numbers matter — Metra riders often know their train by number (e.g., \"the 7:42 BNSF\" or \"Train 1252\")\n- Different lines use different downtown terminals — always note which terminal\n- Peak trains run during rush hours; off-peak and weekend service is less frequent\n- If real-time data is unavailable, the schedule command shows static times\n- Use `--line` to filter by specific Metra line code (BNSF, UP-N, etc.)\n\n### Error Handling\n\n- If `METRA_API_KEY` is not set, all commands print a helpful message with the signup URL\n- Invalid station names show \"No matching station found\" with a suggestion to use stops --search\n- No real-time data available → fall back to static schedule with a note\n- Network errors produce friendly messages\n- GPS dropout for vehicle positions → note that train may be underground or at terminal\n\n### Response Formatting\n\nWhen presenting transit info to the user:\n- Lead with the most actionable info (next arrival time, active alerts)\n- Show line name AND train number (e.g., \"BNSF Train 1252 inbound\")\n- Show times in 12-hour format with AM\u002FPM\n- For arrivals: show both real-time ETA and scheduled time when available\n- Always note the downtown terminal for the line\n- If there are active service alerts for the line being queried, mention them\n\n## External Endpoints\n\n| Endpoint | Data Sent | Data Received |\n|----------|-----------|---------------|\n| `gtfspublic.metrarr.com\u002Fgtfs\u002Fpublic\u002Ftripupdates` | API key (Bearer header, HTTPS) | Trip updates (Protobuf) |\n| `gtfspublic.metrarr.com\u002Fgtfs\u002Fpublic\u002Fpositions` | API key (Bearer header, HTTPS) | Vehicle positions (Protobuf) |\n| `gtfspublic.metrarr.com\u002Fgtfs\u002Fpublic\u002Falerts` | API key (Bearer header, HTTPS) | Service alerts (Protobuf) |\n| `schedules.metrarail.com\u002Fgtfs\u002Fschedule.zip` | None (GET only) | GTFS static data (ZIP) |\n| `schedules.metrarail.com\u002Fgtfs\u002Fpublished.txt` | None (GET only) | Schedule publish timestamp (text) |\n\nAll API calls use HTTPS. The API key is passed as a Bearer token in the Authorization header. No other user data is transmitted.\n\n## Security & Privacy\n\n- **API key required** — All GTFS-RT feeds require a free developer key passed as a Bearer token in the Authorization header\n- **No user data transmitted** — Requests contain only the API key; no personal information\n- **Local storage only** — GTFS static data is cached locally at `~\u002F.metra\u002Fgtfs\u002F`; no data is written elsewhere\n- **No telemetry** — This skill does not phone home or collect usage data\n- **Input handling** — Stop names and route IDs from user input are used only for local filtering, never interpolated into shell commands\n\n## Trust Statement\n\nThis skill reads publicly available transit data from Metra's official GTFS-RT feeds. The API key is used only for Metra API authentication. The skill does not access, store, or transmit any personal information beyond the API key configured by the user.\n",{"name":5,"license":15,"homepage":24,"metadata":25,"description":7},"https:\u002F\u002Fgithub.com\u002Fbrianleach\u002Fmetra-skill",{"clawhub":26},{"tags":27,"emoji":34,"files":35,"install":38,"requires":44},[28,29,5,30,31,32,33],"transit","chicago","transportation","commuter-rail","train","schedule","🚂",[36,37],"scripts\u002Fmetra.mjs","scripts\u002Fgtfs-realtime.proto",[39],{"id":40,"kind":41,"label":42,"command":43},"npm-deps","shell","Install Node.js dependencies (protobufjs)","npm install --prefix $SKILL_DIR",{"env":45,"bins":47},[46],"METRA_API_KEY",[48,49],"node","unzip","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fbrianleach\u002Fmetra",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill metra",{"tool":65,"command":66},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill metra",{"tool":68,"command":69},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill metra","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbrianleach\u002Fmetra\u002FSKILL.md",true,[],[74,82,89,96,103,110],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":81},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":81},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":81},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":81},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":81},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]