Kagi Summarizer
PassAudited by ClawScan on May 10, 2026.
Overview
The skill appears to do what it says—summarize user-provided URLs or text with Kagi—but it uses a Kagi API key and may download a GitHub release binary if not built locally.
This looks safe to use for its stated purpose if you trust Kagi with the content you summarize and understand it may use paid API balance. Configure KAGI_API_KEY carefully, avoid sending secrets or highly sensitive documents, and verify or build the binary rather than blindly accepting an unpinned GitHub release download.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Using the skill authorizes paid Kagi API requests with the user's API balance, but the code does not show the key being logged or sent elsewhere.
The skill reads a Kagi API key from the environment and uses it only as the Authorization header for the Kagi summarizer API.
apiKey := strings.TrimSpace(os.Getenv("KAGI_API_KEY")) ... req.Header.Set("Authorization", "Bot "+apiKey)Store the Kagi API key securely, monitor API usage/balance, and use a scoped or replaceable token if Kagi provides one.
Any text piped or pasted into the tool, and any URL submitted, is shared with Kagi for processing and may consume API balance.
The skill sends the user-provided URL or raw text to Kagi's external summarization API, which is expected for this skill's stated purpose.
const summarizerURL = "https://kagi.com/api/v0/summarize" ... reqBody := summarizeRequest{URL: inputURL, Text: inputText, ...}Only summarize content you are comfortable sending to Kagi; avoid piping secrets or highly sensitive private documents, and consider using --no-cache for sensitive inputs.
A compromised or unexpected GitHub release binary could run code locally under the user's account if the user accepts the download.
If no local executable is present and it cannot build from source, the wrapper can download the latest GitHub release binary and execute it; the wrapper prompts first but does not verify a checksum itself.
RELEASE_META="$(curl -fsSL "https://api.github.com/repos/joelazar/kagi-skills/releases/latest")" ... curl -fsSL "$URL" -o "$BIN" ... chmod +x "$BIN" ... exec "$BIN" "$@"
Prefer building from the included source when possible, or verify the GitHub release checksum/signature and pin a trusted release version before running the downloaded binary.