Acca Tracker

v1.0.0

Track football accumulator (acca) betting slips — parses slip photo or text, checks live scores every 15 minutes, and reports bet status (WINNING/LOST/PENDIN...

0· 74·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for svenmedina07-ship-it/acca-tracker.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Acca Tracker" (svenmedina07-ship-it/acca-tracker) from ClawHub.
Skill page: https://clawhub.ai/svenmedina07-ship-it/acca-tracker
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install acca-tracker

ClawHub CLI

Package manager switcher

npx clawhub@latest install acca-tracker
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the runtime instructions: parsing slips (vision/text), polling live scores, computing leg/acca status and cash-out estimates. No unrelated binaries, credentials, or config paths are requested.
Instruction Scope
Instructions remain within betting-tracking scope (vision_analyze, parsing, web_search, calls to TheSportsDB). The skill instructs creating recurring cron jobs (*/15 etc.) that run autonomously and perform network calls; this is expected for continuous tracking but is a behavioral scope the user should be aware of. It does not instruct reading arbitrary local files or environment variables.
Install Mechanism
No install spec and no code files — instruction-only skill. This minimizes on-disk risk; runtime actions depend on platform tools (vision_analyze, cronjob, web_search, execute_code) rather than installing third-party packages.
Credentials
Skill requests no environment variables, credentials, or config paths. The external-data access it requires (public score APIs / web searches) is proportionate to the stated function.
Persistence & Privilege
Skill does not set always:true and is user-invocable only, but it creates cronjobs that will run repeatedly and autonomously via the platform's cronjob tool. That persistent scheduling is reasonable for intended use but increases the window of autonomous network activity — platform cron permissions should be reviewed before enabling.
Assessment
This skill appears to do what it says: parse a bet slip and poll public score sources periodically. Things to consider before installing: (1) it will create recurring cron jobs that run autonomously and make network requests every 10–15 minutes — confirm you are comfortable with that behavior and any platform-level access the cronjob tool has; (2) you will upload photos of betting slips (which may contain personal info) — treat those images as sensitive; (3) it uses public live-score sources (TheSportsDB + web_search) and an example shows executing HTTP requests via code — there are no credentials requested, but network traffic will be sent to external services; (4) confirm the skill’s confirmation step (it shows the parsed slip and asks Start tracking?) is honored so jobs aren’t scheduled without explicit approval. If you want extra caution, ask the developer to (a) limit frequency or duration of cronjobs by default, (b) explicitly log where data is sent and retained, or (c) require per-user opt-in for persistent tracking.

Like a lobster shell, security has layers — review code before you run it.

accumulatorvk970tqrrng0rk31qktgxm933d184w2wybettingvk970tqrrng0rk31qktgxm933d184w2wyfootballvk970tqrrng0rk31qktgxm933d184w2wylatestvk970tqrrng0rk31qktgxm933d184w2wylive-scoresvk970tqrrng0rk31qktgxm933d184w2wysportsvk970tqrrng0rk31qktgxm933d184w2wy
74downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Acca Tracker — Football Accumulator Monitor

Track football accumulator (parlay) bets by monitoring live scores and reporting whether each leg is still alive. Works with any betting slip — photo, screenshot, or typed text.

When to Use

  • User shares a photo/screenshot of a betting slip (accumulator/parlay/bet builder)
  • User wants live score updates for their bets
  • User says "track my acca", "monitor my bet", "is my bet alive", "check my slip"

How It Works

User sends slip photo
  → Agent parses legs (vision_analyze or text extraction)
  → Agent creates a cron job (*/15 * * * *)
  → Cron searches live scores every 15 min
  → Cron delivers report: per-leg status + acca health
  → Auto-cleans up after all matches finish

Step 1: Parse the Slip

From a Photo

Use vision_analyze with the image and this question:

Extract all betting legs from this slip. For each leg return:
- Match (Team A vs Team B)
- Competition/League
- Date and kickoff time
- Bet type (exact wording from slip)
- Decimal odds

Also extract: total odds, stake amount, max return, any bonus info.

From Text

If user types their slip, extract the same fields. Normalize bet type wording to match the standard types in references/bet-types.md.

Step 2: Build the Slip Summary

After parsing, confirm with the user before starting tracking:

📋 PARSED SLIP — 5 legs

 1. Arsenal vs PSG (UCL, 21:00) — Arsenal W (1.55) — 64.5%
 2. Bayern vs Inter (UCL, 21:00) — Bayern W (1.40) — 71.4%
 3. Luton vs Northampton (L1, 20:45) — BTTS No (1.77) — 56.5%
 4. Wimbledon vs Stockport (L1, 20:45) — Stockport W (1.85) — 54.1%
 5. FSV Schöningen vs Lohne (RL, 18:00) — BTTS No (2.65) — 37.7% ⚠️

Stake: €10 | Combined odds: 21.04 | Max return: €210.40
Riskiest leg: #5 (37.7% implied)

Start tracking? (yes/no)

Calculate implied probability per leg: 1 / odds * 100. Flag any under 40% as ⚠️ gamble leg.

Step 3: Create the Cron Job

Use the cronjob tool:

action: create
name: acca-tracker-{short-id}
schedule: "*/15 * * * *"
repeat: 48
deliver: origin
prompt: {see template below}

Schedule Adjustments

ScenarioScheduleRepeat
Single match day*/15 * * * *48
High-stakes acca*/10 * * * *72
Multi-day (Tue + Wed)*/15 * * * *192
Tournament bracket0 */2 * * *84

Cron Prompt Template

You are tracking a football accumulator bet. Check live scores NOW and report.

SLIP DETAILS:
{paste all legs with bet types, odds, and win conditions}

Total odds: {total} | Stake: {stake} | Max return: {max_return}

INSTRUCTIONS:
1. For each match, web_search: "{Team A} vs {Team B} live score {date}"
2. Also try: "{Team A} {Team B} {competition} score today"
3. For each leg determine:
   - Current score
   - Match status: Not Started / Live (minute) / HT / FT / Postponed / Abandoned
   - Bet status: ✅ WON / ✅ WINNING / ⏳ PENDING / ❌ LOST / ❌ DEAD
4. Calculate overall acca status:
   - ALL SAFE ✅ = no legs lost
   - STILL ALIVE ⏳ = no legs lost, none confirmed won
   - ACCA DEAD ❌ = at least one leg LOST
5. If acca dead: name the killing leg, explain why
6. Calculate "legs alive / won / lost / pending / total"
7. If all FT: state "TRACKING COMPLETE" and summarize

REPORT FORMAT (code blocks only):
🏟️ ACCA LIVE REPORT — {time}

Leg | Match                          | Score | Status | Bet        | Result
----|--------------------------------|-------|--------|------------|----------
 1  | Team A vs Team B              | 2 - 0 | 67'    | Team A W   | ✅ WINNING

📊 1 winning / 0 won / 0 lost / 2 pending (3 total)
💰 ⏳ STILL ALIVE

DATA: If no score found, say so explicitly. Never guess scores.
If 2+ hours past kickoff with no data: "unverified — likely finished"

Step 4: Report States

All Alive

🏟️ ACCA LIVE — 21:34 CET

 1 | Arsenal vs PSG       | 1 - 0 | 55' | Arsenal W | ✅ WINNING
 2 | Bayern vs Inter      | 0 - 0 | 55' | Bayern W  | ⏳ PENDING
 3 | Luton vs Northampton | 0 - 0 | 55' | BTTS No   | ✅ WINNING

📊 1 winning / 0 won / 0 lost / 2 pending
💰 ⏳ STILL ALIVE

Acca Dead

🏟️ ACCA LIVE — 22:18 CET

 1 | Arsenal vs PSG       | 2 - 1 | 78' | Arsenal W | ✅ WINNING
 2 | Bayern vs Inter      | 1 - 2 | 78' | Bayern W  | ❌ DEAD
 3 | Luton vs Northampton | 0 - 0 | 78' | BTTS No   | ✅ WINNING

📊 1 winning / 0 won / 1 dead / 1 pending
❌ ACCA DEAD — Leg 2 killed it (Bayern losing 1-2)

Remaining matches still playing — updating for interest.

Final — Won

🏟️ ACCA FINAL — 23:45 CET — 🎉🎉🎉

 1 | Arsenal vs PSG       | 2 - 1 | FT | Arsenal W | ✅ WON
 2 | Bayern vs Inter      | 3 - 1 | FT | Bayern W  | ✅ WON
 3 | Luton vs Northampton | 0 - 0 | FT | BTTS No   | ✅ WON

📊 3/3 LEGS WON
💰 ACCA WON — Stake: €10 | Return: €210.40

Tracking complete.

Cash-Out Context

When some legs won and others pending, estimate cash-out value:

Won legs combined odds: 1.55 × 1.40 = 2.17
Remaining legs implied probability: 0.565 × 0.541 × 0.377 = 0.115
Estimated value: €10 × 2.17 × 0.115 = €2.49
Cash-out range: ~€2.00 – €3.50 (rough estimate)

Only include when: at least 1 leg WON, at least 1 PENDING, acca NOT dead. Always frame as "estimated".

Data Source Strategy

See references/data-sources.md for full tier system and search patterns.

Quick reference:

  • Major leagues: BBC, ESPN, Google scores (near real-time)
  • Second tier: Sky Sports, Sofascore (5-10 min lag)
  • Low tier: TheSportsDB, Wikipedia (HT/FT only)
  • No data found: State explicitly, never guess

Bet Types

See references/bet-types.md for the full list of 18+ bet types with scoring logic, decision tree, and edge cases (void, ET, red cards, handicaps).

Step 5: Cleanup

  • After all matches FT, deliver final summary then stop
  • Auto-ends after repeat count
  • User can say "stop tracking" to remove cron early
  • Multi-day accas: increase repeat to 192

Limitations

  • 15-min intervals — goals missed between checks, not real-time
  • Low-tier leagues — limited coverage, may only get HT/FT
  • JS-rendered sites — Flashscore/Sofascore can't be scraped directly
  • Bookmaker-specific rules — some bet types vary by bookmaker
  • Telegram delivery may fail — "Topic_closed" errors can block cron delivery even on active topics. Reports still generate at ~/.hermes/cron/output/{job_id}/.md. Workaround: read output files directly, or deliver to main chat without thread ID.

Tips

  • Always confirm slip with user before starting
  • Include team nicknames in search queries
  • When acca dies, keep tracking for interest
  • Flag "near misses" (hit post, disallowed goal) if mentioned in results
  • Name each cron differently for multi-slip support

Comments

Loading comments...