Clawdbot For Vcs
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill matches its VC-workflow purpose, but it asks for broad Gmail, Calendar, and Affinity access and can automatically mutate email and CRM records with unclear approval boundaries.
Review carefully before installing. If you use it, begin with read-only briefings and draft-only email handling. Do not allow automatic archiving, CRM writes, calendar changes, or scheduled runs until you have verified the rules, pinned the external CLI dependency, and confirmed where sensitive memos and notes will be stored.
Findings (6)
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.
A mistaken classification could hide an email from the inbox or create/update CRM records incorrectly.
This authorizes automated Gmail and Affinity mutations based on model classification, including archiving emails and changing CRM state, not just drafting messages.
When your AI checks email: ... If AUTO-RESPOND: Create draft + add to Affinity + archive
Start in report-only or draft-only mode, and require explicit confirmation before archiving emails, adding companies, setting deal stages, or writing notes to Affinity.
Anyone using this skill should understand that it can read and modify email state, access calendar data, and write to the CRM through the configured credentials.
The workflow requires privileged access to Gmail, Google Calendar, and Affinity CRM. This is expected for the stated purpose but gives the agent meaningful authority over business accounts.
You'll need to grant these scopes: ... https://www.googleapis.com/auth/gmail.modify ... https://www.googleapis.com/auth/calendar ... export AFFINITY_API_KEY="your_api_key_here"
Use the least-privileged accounts and API keys available, rotate keys if exposed, and confirm whether Affinity supports scoped or limited API access.
A future upstream change to the CLI could alter behavior for Gmail or Calendar access.
The setup installs a third-party CLI at the moving '@latest' version; the command is user-directed and purpose-aligned, but its provenance and version are not pinned.
go install github.com/martynsmith/gog@latest
Pin the CLI to a reviewed version, verify the project source, and install it in a controlled environment before granting OAuth access.
Sensitive deal materials may be retained in local files and CRM notes beyond the immediate task.
The workflow persists investment memo content locally and can sync it into Affinity notes, which may include sensitive founder, deal, and diligence information.
Memo saved to ~/memos/datacorp.md ... Push to Affinity? ... Memo added to Affinity as note
Define retention, sharing, and access rules for memos and notes; keep sensitive files in protected directories and avoid syncing confidential content unless intended.
Users may over-trust the skill as draft-only while it performs other account mutations automatically.
The safety framing suggests external actions require approval, but the workflow also describes automatic Affinity logging and email archiving, creating ambiguity about what the user is approving.
Your AI should be proactive but ask before acting externally. It reads, analyzes, and proposes — you approve and execute. ... If AUTO-RESPOND: Create draft + add to Affinity + archive
Clarify that CRM writes, calendar changes, label changes, and archiving are external actions, and require explicit user approval for each class of mutation by default.
The assistant could continue processing account data on a schedule after setup, including changing labels, archiving emails, or updating CRM entries.
The setup encourages recurring proactive operation. That is useful for daily briefings, but combined with Gmail and CRM mutation authority it needs clear enable/disable and approval controls.
Check email 2-4 times per day: Morning (9am) ... Midday (1pm) ... Afternoon (4pm) ... Evening (7pm) - optional
Keep scheduled automation disabled until tested, document how to stop it, and separate read-only briefings from mutation workflows.