Demo-Slap Highlight Skill

Generate MP4 highlights and fragmovies from CS2 demos.

This skill is designed for OpenClaw environments where background jobs, local helper scripts, and chat-aware delivery are available. It uses Python 3 scripts and the requests package for HTTP API access.

Expected runtime inputs:

• - Required: INLINECODE1
• Optional: INLINECODE2
• Optional deployment helper: INLINECODE3

Scripts

Run bundled scripts relative to the skill root, usually from scripts/.

Demo-Slap

Script	Purpose
INLINECODE5	List recent matches from Demo-Slap INLINECODE6
INLINECODE7

Try to resolve replay/demo URL from Demo-Slap match history by index; fail clearly if the API exposes only jobId |

| demo_slap_match_pick.py | Pick a Demo-Slap match by index and return structured match info including jobId | | demo_slap_analyze.py | Submit a demo for analysis, poll until done, output highlights JSON | | demo_slap_render.py | Render one or more highlights, poll until done, output clip URL | | demo_slap_common.py | Shared utilities (config, API calls, state) |

Leetify

Script	Purpose
INLINECODE14	List recent matches
INLINECODE15

Resolve replay URL by username + match index |

| leetify/leetify_save_id.py | Save username -> Steam64 ID mapping | | leetify/leetify_common.py | Shared Leetify utilities |

Match source selection

• - Prefer Leetify for recent match discovery when LEETIFY_API_KEY is available.
• If LEETIFY_API_KEY is not configured but DEMOSLAP_API_KEY is available, use Demo-Slap match history from /public-api/matches.
• Swagger: INLINECODE22
• Treat Demo-Slap match history as the fallback discovery path for listing matches and selecting an existing analyzed match or replay context before analyze/render.

Runtime files

Use these files as optional local runtime state during execution:

• - INLINECODE23
• INLINECODE24
• INLINECODE25
• INLINECODE26
• INLINECODE27

These files are runtime helpers for local operation and are not required to understand or inspect the skill package itself.

INLINECODE28 tracks the current operation:
CODEBLOCK0

Workflow

1. Find the match

Preferred path when LEETIFY_API_KEY is available: CODEBLOCK1

Fallback path when LEETIFY_API_KEY is missing but DEMOSLAP_API_KEY is available:

python3 scripts/demo_slap_matches.py [<USERNAME>] [--limit 10]

• - uses Demo-Slap INLINECODE32
• use the Demo-Slap swagger docs at https://api-doc.demo-slap.net/ if schema details are needed
• if <USERNAME> is provided and mapped, filter matches to that player's Steam ID when possible
• after the user picks a match, run:

python3 scripts/demo_slap_match_pick.py [<USERNAME>] --match-index <N>

• - treat the returned jobId as the primary handle for downstream Demo-Slap operations

2. Resolve replay URL

Preferred path when using Leetify: CODEBLOCK4

When using Demo-Slap fallback:

python3 scripts/demo_slap_match_pick.py [<USERNAME>] --match-index <N>

• - use the returned jobId as the selected match identifier
• if demoUrl is present, you may still use analyze-by-URL
• if demoUrl is absent, skip URL resolution and continue by API endpoints that accept the existing analyze INLINECODE39
• use GET /public-api/analyze/{jobId}/status and GET /public-api/analyze/{jobId}/data to inspect existing highlights
• if the user wants clips and highlights already exist, render directly from that INLINECODE42

3. Analyze in background

CODEBLOCK6

Run with exec(background: true) and keep the returned process/session id.

Optional deployment-specific watchdog pattern for OpenClaw environments:

• - Use a watchdog only when background analyze/render work benefits from periodic delivery checks.
• Reuse an existing deployment watchdog when available instead of assuming a new persistent scheduler entry is always needed.
• If a deployment chooses to create or enable a watchdog through the built-in cron tool, keep it scoped to the active run and disable it again after terminal delivery.
• A 2 minute interval is a reasonable default.
• Use scripts/demo_slap_watchdog.sh status|tail|job only as a local helper for inspecting runtime state, logs, or deployment-specific job references.
• Treat data/state.json and data/highlights.json as the source of truth during runtime.

Agent workflow:

1. 1. Choose the match source:

- Leetify if LEETIFY_API_KEY exists
- Demo-Slap /public-api/matches if LEETIFY_API_KEY is missing and DEMOSLAP_API_KEY exists

1. 2. If using Leetify, resolve the replay URL and run analyze
2. If using Demo-Slap fallback, pick a match and inspect the returned INLINECODE52
3. If the selected Demo-Slap match already has analyze data, continue by jobId instead of forcing analyze-by-URL
4. Use or enable a deployment watchdog only when long-running analyze/render work benefits from it
5. Launch analyze or render and save the returned process/session id when applicable
6. Let the watchdog deliver the result when a deployment uses one
7. Disable the watchdog again after terminal delivery

4. Render in background

CODEBLOCK7

Run with exec(background: true) and keep the returned process/session id.

Optional deployment-specific watchdog pattern for OpenClaw environments:

• - Use a watchdog only when background analyze/render work benefits from periodic delivery checks.
• Reuse an existing deployment watchdog when available instead of assuming a new persistent scheduler entry is always needed.
• If a deployment chooses to create or enable a watchdog through the built-in cron tool, keep it scoped to the active run and disable it again after terminal delivery.
• A 2 minute interval is a reasonable default.
• Use scripts/demo_slap_watchdog.sh status|tail|job only as a local helper for inspecting runtime state, logs, or deployment-specific job references.
• Treat data/state.json and data/highlights.json as the source of truth during runtime.

Agent workflow:

1. 1. Enable or reuse a deployment watchdog only when needed for the active run
2. Launch render and save the returned process/session id
3. Poll process output for the Estimated finish: line and tell the user the ETA if present
4. Let the watchdog deliver the result when one is in use
5. Disable the watchdog again after terminal delivery

Critical: set <CHAT_ID> from inbound metadata of the originating request. Treat hardcoded chat identifiers as local examples only, not as a reusable default.

5. Check status

Read data/state.json.

Setup

Map username to Steam ID

CODEBLOCK8

Configure API keys

Prefer environment variables:

• - DEMOSLAP_API_KEY - required
• INLINECODE63 - optional, only for Leetify-backed match discovery
• INLINECODE64 - optional deployment-specific helper for watchdog inspection scripts

Source selection rules:

• - If LEETIFY_API_KEY exists, use Leetify for match discovery.
• If LEETIFY_API_KEY is absent but DEMOSLAP_API_KEY exists, use Demo-Slap /public-api/matches for match discovery.
• INLINECODE69 is always required for analyze/render.

Optional local fallback for controlled self-hosted setups: put them in data/config.json.

Support

For access and support, please join our Discord community: https://discord.gg/8nfh26W9wQ