Agent Skills durchsuchen

Sortieren nach

13+ Ergebnisse

autoreview

Quelleopenclaw/openclaw/.agents/skills/autoreview/SKILL.md

Aktualisiert2026-07-31

Pre-commit/ship code review: Codex default; optional Claude or Pi.

acp-router

Quelleopenclaw/openclaw/extensions/acpx/skills/acp-router/SKILL.md

Aktualisiert2026-08-24

Route plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-driven sessions ("telephone game" flow). For coding-agent thread requests, read this skill first, then use only `sessions_spawn` for thread creation. Codex chat binding defaults to the native Codex app-server plugin unless ACP is explicit or background spawn needs ACP.

coding-agent

Quelleopenclaw/openclaw/skills/coding-agent/SKILL.md

Aktualisiert2026-07-29

Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.

crabbox

Quelleopenclaw/openclaw/.agents/skills/crabbox/SKILL.md

Aktualisiert2026-08-17

Remote environment and isolation proof for OpenClaw: clean-machine E2E, untrusted code, package/install, live providers and channels, desktop, cross-OS, diagnostics, and cleanup.

openclaw-debugging

Quelleopenclaw/openclaw/.agents/skills/openclaw-debugging/SKILL.md

Aktualisiert2026-08-16

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored sessions, transcripts, and attachments as evidence.

node-connect

Quelleopenclaw/openclaw/skills/node-connect/SKILL.md

Aktualisiert2026-08-14

Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.

receiving-code-review

Quelleobra/superpowers/skills/receiving-code-review/SKILL.md

Aktualisiert2026-07-24

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation