What makes Demo Slap notable?

1.2K downloads. Trust evidence available

How should Demo Slap be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Demo Slap

Generate CS2 highlights and fragmovies from demos using the Demo-Slap API, with optional Leetify integration and Demo-Slap match history fallback to select r...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 11, 2026

Version

0.1.4

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 11, 2026
Latest release: 0.1.4release · observed Mar 15, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s170dx4nw2adr8scv090bb28dd84pbe2:demo-slap

Install using `clawhub skill install s170dx4nw2adr8scv090bb28dd84pbe2:demo-slap` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/jeminay/demo-slap before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-jeminay-demo-slap/snapshot"

Documentation

CLAWHUB

63,344 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: demo-slap
description: Generate CS2 highlights and fragmovies from demos using the Demo-Slap API, with optional Leetify integration and Demo-Slap match history fallback to select recent matches. Use when a user asks to record a highlight, render a clip, make a fragmovie, clip a round, or turn a CS2 demo into MP4 video.
metadata:
  {
    "openclaw": {
      "requires": {
        "env": ["DEMOSLAP_API_KEY"],
        "bins": ["python3", "openclaw"]
      }
    }
  }
---

# 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: `DEMOSLAP_API_KEY`
- Optional: `LEETIFY_API_KEY`
- Optional deployment helper: `DEMO_SLAP_WATCHDOG_JOB_ID`

## Scripts

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

### Demo-Slap
| Script | Purpose |
|--------|---------|
| `demo_slap_matches.py` | List recent matches from Demo-Slap `/public-api/matches` |
| `demo_slap_resolve.py` | 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 |
|--------|---------|
| `leetify/leetify_matches.py` | List recent matches |
| `leetify/leetify_resolve.py` | 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: `https://api-doc.demo-slap.net/`
- 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:
- `data/state.json`
- `data/highlights.json`
- `data/history.log`
- `data/steam_ids.json`
- `data/config.json`

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

`state.json` tracks the current operation:
```json
{
  "status": "idle|analyzing|rendering|done|error",
  "job_id": "...",
  "render_job_id": "...",
  "chat_id": "telegram:182314856",
  "clip_urls": {"highlight_id": "https://..."},
  "pro

_meta.json

{
  "ownerId": "kn73589k2rv646tm107cp6d90s81g7xy",
  "slug": "demo-slap",
  "version": "0.1.4",
  "publishedAt": 1773552433100
}

scripts/demo_slap_task.md

# demo-slap task workflow

Recommended OpenClaw runtime pattern:

- do not manage the watchdog through shell cron commands
- prefer OpenClaw's built-in cron tool when a deployment chooses to enable or disable a watchdog for a live run
- treat watchdog configuration and any job id as deployment-specific, not globally hardcoded
- when used, `DEMO_SLAP_WATCHDOG_JOB_ID` should be supplied by the deployment rather than embedded in the skill
- use the shell helper only for local inspection of state/log/job references:

```bash
scripts/demo_slap_watchdog.sh status
scripts/demo_slap_watchdog.sh tail
scripts/demo_slap_watchdog.sh job
```

Suggested runtime workflow for assistants:
1. Before analyze/render -> `cron.update(jobId=<watchdog>, enabled=true)` when a deployment watchdog is being used
2. Start analyze/render
3. Let the watchdog inspect state on a reasonable interval such as every 2 minutes
4. After successful delivery or terminal error -> `cron.update(jobId=<watchdog>, enabled=false)` when the deployment watchdog was enabled for that run

skill-card.md

## Description:

Generate CS2 highlights and fragmovies from demos using the Demo-Slap API, with optional Leetify integration and Demo-Slap match history fallback for recent match selection.

This skill is ready for commercial/non-commercial use.

## Publisher:

[jeminay](https://clawhub.ai/user/jeminay)

### License/Terms of Use:

MIT-0

## Use Case:

External users and developers use this skill in OpenClaw environments to select CS2 matches, analyze demos, render highlight clips or fragmovies, and deliver MP4 clip URLs.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: Sensitive API keys or runtime data may be kept in local configuration or data files.

Mitigation: Prefer environment-injected API keys, restrict access to the data directory, and avoid storing secrets in data/config.json.

Risk: Untrusted job, chat, and clip data can be published into OpenClaw system events.

Mitigation: Use typed events or validated and redacted fields before enabling automatic delivery actions.

Risk: Background watchdog jobs can continue beyond the intended render or analysis run if left enabled.

Mitigation: Avoid watchdog jobs when possible; when needed, scope them to the active run and disable them after terminal delivery or error.

## Reference(s):

- [Demo Slap on ClawHub](https://clawhub.ai/jeminay/skills/demo-slap)
- [Demo-Slap API Swagger](https://api-doc.demo-slap.net/)
- [Demo-Slap API](https://api.demo-slap.net)
- [Leetify Public API](https://api-public.cs-prod.leetify.com)

## Skill Output:

**Output Type(s):** [text, markdown, shell commands, configuration, JSON, files]

**Output Format:** [Markdown guidance with inline shell commands, JSON script output, runtime state files, and MP4 clip URLs]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Requires DEMOSLAP_API_KEY; can use LEETIFY_API_KEY for match discovery and OpenClaw for background notification workflows.]

## Skill Version(s):

0.1.4 (source: server release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.