ClawInsight
PassAudited by ClawScan on May 10, 2026.
Overview
ClawInsight is a coherent survey-integration skill, but it handles personal survey/profile data and an account API key, so users should review each answer before approving it.
Install only if you are comfortable sharing your ClawInsight registration profile and approved survey answers with the service. Review and edit every draft before approving it, avoid sensitive topics such as health, finances, credentials, politics, or exact addresses, and keep the ClawInsight API key secure.
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.
If the user approves an incorrect or overly personal draft, that answer can be sent to the ClawInsight service.
The client can POST survey answers to ClawInsight. This is expected for the skill and fields are filtered, but it is still an external data-submission action that should remain user-approved.
async function submitResponse(apiKey, responseData) { return request('/responses', { method: 'POST', headers: authHeaders(apiKey), body: JSON.stringify(sanitizeResponse(responseData)), }); }Review the exact answer and, if possible, the exact payload before approving any submission; do not approve answers containing sensitive information.
Anyone who obtains the API key could impersonate the user to the ClawInsight service.
The skill uses a bearer API key and recommends persistent storage. That is normal for this integration, but the key represents the user's ClawInsight account.
**Save your `api_key` immediately!** You need it for all requests. **Recommended:** Save your API key to memory or a local credentials file
Store the key only in a trusted secret store or protected local credential file, and revoke it from the dashboard if it may have been exposed.
Personal details from previous chats could influence a draft answer and be shared if the user approves it.
The skill may reuse prior chat context and profile details to draft survey answers. User review reduces risk, but past conversations can contain private details or mistaken context.
When composing draft answers, the agent draws only from: 1. The current conversation with the user 2. Prior chat history with this user 3. The user's registered profile
Carefully edit drafts, remove sensitive details, and avoid using the skill if you are not comfortable with prior chat history informing survey responses.