# Everything Capture OpenClaw

> This skill should be used when the user asks to save a link into Everything Capture from OpenClaw clients such as QClaw, says "存这个链接", "帮我收进去", "导入这个链接", asks a pure text knowledge-base question in the same chat, or asks for Everything Capture item share links.

- Skill: `agentenatalie/everything-capture-openclaw` (Agent Skill)
- Install (CLI): `npx skillmds@latest add agentenatalie/everything-capture-openclaw`
- Raw SKILL.md: https://api.skillmd.com/api/skills/agentenatalie/everything-capture-openclaw/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: agentenatalie (https://skillmd.com/u/agentenatalie)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/agentenatalie/everything-capture-openclaw

---


# Everything Capture OpenClaw

Route OpenClaw client messages, including QClaw, into the Everything Capture cloud adapter with deterministic tool selection.

## Trigger Rules

Apply the following order:

1. If the user message contains any `http://` or `https://` URL, call `capture_content`.
2. If the user message has no URL and is a normal question, call `ask_knowledge_base`.
3. If the user explicitly asks for a share link for known local item ids, call `create_item_share_links`.

## Guardrails

- Treat any message that contains both a URL and additional commentary as `capture_content` only.
- Do not use `ask_knowledge_base` for mixed URL + question messages in the same turn.
- Keep replies short and operational.
- When `capture_content` returns `queued`, tell the user the item has entered the queue.
- When `capture_content` returns `processed`, include the read-only share link and the original URL when present.
- When `ask_knowledge_base` returns citations with `share_url`, include those links inline after the short answer.
- Do not invent share links. Only surface links returned by tools.

## Reply Shape

- Capture success:
  - Short status sentence
  - Read-only share link when present
  - Original source URL when present
- Ask success:
  - 1 short answer paragraph
  - 1 compact citation/link block when present
- Failure:
  - 1 short sentence naming the failure
  - No speculative recovery text beyond asking the user to retry later when the queue/job failed