Rugbyclaw

Rugby scores, fixtures, and results for OpenClaw.

Prerequisites

Install the rugbyclaw CLI:

npm install -g rugbyclaw

If global install is unavailable, use:

npx -y rugbyclaw@latest --version

No API key is required (free mode uses a proxy with limits).

Recommended setup:

rugbyclaw start rugbyclaw status --json

For non-interactive agent setup, prefer:

rugbyclaw start --yes --tz America/New_York --mode proxy --agent

If direct mode is required, pass key from env:

rugbyclaw start --yes --mode direct --api-key-env API_SPORTS_KEY

The setup flow can:

• Keep you on free mode (default) or let you add an API key (optional)

• Let you select favorite leagues (free mode is limited to default leagues)

• Optionally pick favorite teams

• Set your timezone

Commands

Use these CLI commands with --json for structured output:

User Query Command

"Rugby scores" / "What's happening in rugby?" rugbyclaw scores --json

"Top 14 fixtures" / "Upcoming matches" rugbyclaw fixtures [league] --json

"Recent results" / "Who won?" rugbyclaw results [league] --json

"Toulouse next match" / "When do they play?" rugbyclaw team next <name> --json

"How did Toulouse do?" / "Last result" rugbyclaw team last <name> --json

"Find team Racing" rugbyclaw team search <query> --json

League Slugs

• top14 — French Top 14

• premiership — English Premiership

• urc — United Rugby Championship

• champions_cup — Champions Cup

• challenge_cup — Challenge Cup

• six_nations — Six Nations

• super_rugby — Super Rugby Pacific

• pro_d2 — Pro D2

Response Style

When presenting match results, use the personality-driven summaries from the JSON output.

Keep responses casual and fun:

• For wins: "Toulouse demolished Racing 38-12. Absolute clinic."

• For close matches: "Heart attack rugby. Toulouse takes it 24-22."

• For losses: "Ugh. So close. Toulouse falls 18-21."

Use emoji sparingly (🏉 for scores, 🔥 for big wins).

Proactive Notifications

The skill supports proactive notifications via cron:

Weekly digest (Monday 9am)

rugbyclaw notify --weekly --json

Day-before and hour-before reminders

rugbyclaw notify --daily --json

Live score updates (poll during match windows)

rugbyclaw notify --live --json

Each returns a JSON array of notifications to send to the user.

For strict automation, use --agent (one-line envelope with ok , exit_code , error_type , data , trace_id ).

Bootstrap quickly for OpenClaw:

rugbyclaw openclaw init --agent

Calendar Export

To add a match to calendar:

rugbyclaw calendar <match_id> --stdout

This outputs an .ics file the user can import into any calendar app.

Error Handling

If commands fail, JSON output includes:

• ok: false

• error

• exit_code

• error_type

Common issues:

• "Rate limit exceeded" — Wait a bit, or add an API key for higher limits

• "No matches found" — Check league slug or try different search

Agent Setup Checklist

If you're unsure how Rugbyclaw is configured, run:

rugbyclaw status --json

Then:

• If mode is proxy , stick to default leagues and keep calls minimal.

• If the user's timezone is known, prefer passing --tz <IANA> (example: --tz America/New_York ) for consistent dates/times.

• Prefer scores --json , fixtures --json , results --json , team ... --json for structured output.

• Team search is scoped to Rugby Union teams in effective_leagues (to avoid irrelevant matches).

• Run rugbyclaw doctor --json once before long workflows; if proxy/API checks fail, stop and surface the fix.

• For fail-fast automation, use rugbyclaw doctor --json --strict .

• Treat time_confidence: "pending" as unconfirmed kickoff data and say so clearly.

Examples

User: "Rugby scores" Agent: Runs rugbyclaw scores --json , presents today's matches

User: "When does Toulouse play next?" Agent: Runs rugbyclaw team next toulouse --json , presents next fixture

User: "How did Racing do?" Agent: Runs rugbyclaw team last racing --json , presents result with personality summary