Skip to main content

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.

Datos de origen

Repositorio
agentenatalie/everything-capture-openclaw-plugin
Última actividad en el origen
3 de abril de 2026 a las 02:10
Idioma detectado de SKILL.md
inglés
Estrellas
0
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
Everything Capture OpenClaw
description
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.
version
0.1.0
# 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
Ver en GitHub