Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Call

v2.1.0

Call management system with preparation, real-time capture, and follow-up tracking. Use when user mentions phone calls, meetings, conversations, commitments...

0· 357·4 current·4 all-time
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The stated purpose (call preparation, capture, follow-up) matches the single included script (prep_call.py) for preparing calls, but SKILL.md advertises many additional capabilities (real-time capture, end-call summary, follow-up drafting, tracking) that require other scripts which are not present. That makes the delivered capability set disproportionate to the description.
!
Instruction Scope
SKILL.md instructs the agent to invoke multiple scripts (capture_fragments.py, end_call.py, draft_followup.py, check_followups.py, etc.) and references several 'references/*.md' docs, none of which are included. The doc also states data is stored under memory/calls/, while the included script reads from ~/.openclaw/workspace/memory/calls — an inconsistency in storage paths. Because core runtime instructions point to missing files, the agent cannot follow the declared workflows and the privacy/storage claims cannot be validated.
Install Mechanism
No install spec and no external downloads — lowest-risk distribution. Only an instruction file and one small Python script are present; nothing is written to disk by an installer.
Credentials
The skill requests no environment variables, no credentials, and no config paths. The single script only reads a local JSON file under the user's home directory; no network or external services are requested.
Persistence & Privilege
Skill is not forced-always or requesting elevated persistence. It does read from and (per SKILL.md) would store data locally, but the package does not show any installer or service that would create persistent processes or modify other skills.
What to consider before installing
This package is incomplete: SKILL.md promises many scripts and local-data behavior but only scripts/prep_call.py is included. Before installing or enabling this skill, ask the publisher for the missing scripts and the referenced documentation so you can review them for network calls, credential use, and data-write behavior. Verify where data is written (the script uses ~/.openclaw/workspace/memory/calls but the README mentions memory/calls/) and confirm you are comfortable with that location. If you cannot obtain the full source, treat this as untrusted — do not grant it elevated access or let it run autonomously. If you proceed, run it in an isolated environment and inspect any additional scripts for outbound network calls, credential access, or unexpected file writes.

Like a lobster shell, security has layers — review code before you run it.

callvk97cq89xqvj1ryj9sgrbw1r2f982fhptcallsvk976c0rn6pcrm6jjzy39d8pn2x82mk8sconversationsvk976c0rn6pcrm6jjzy39d8pn2x82mk8scrmvk976c0rn6pcrm6jjzy39d8pn2x82mk8sfollow-upvk976c0rn6pcrm6jjzy39d8pn2x82mk8sfollowupvk97cq89xqvj1ryj9sgrbw1r2f982fhptlatestvk976c0rn6pcrm6jjzy39d8pn2x82mk8smeetingvk97cq89xqvj1ryj9sgrbw1r2f982fhptmeetingsvk976c0rn6pcrm6jjzy39d8pn2x82mk8snotesvk97cq89xqvj1ryj9sgrbw1r2f982fhptphonevk97cq89xqvj1ryj9sgrbw1r2f982fhpt
357downloads
0stars
2versions
Updated 6h ago
v2.1.0
MIT-0

Call

Call management system. Every conversation, fully leveraged.

Critical Privacy & Safety

Data Storage (CRITICAL)

  • All call data stored locally only: memory/calls/
  • No call recording (unless user explicitly enables separately)
  • No external CRM connected
  • No sharing of conversation data
  • User controls all data retention and deletion

Privacy Note

Call records contain sensitive information. All data stays local and private. You control what is captured and retained.

Data Structure

Call data stored locally:

  • memory/calls/calls.json - Complete call records
  • memory/calls/contacts.json - Contact history and context
  • memory/calls/commitments.json - Commitments made/received
  • memory/calls/followups.json - Pending follow-ups
  • memory/calls/templates.json - Follow-up message templates

Core Workflows

Prepare for Call

User: "I have a call with Acme Corp in 30 minutes"
→ Use scripts/prep_call.py --contact "Acme Corp" --purpose "negotiate contract"
→ Pull previous calls, open commitments, relevant context

Capture During Call

User: "Note: They need the proposal by Friday, Sarah is decision maker, follow up on pricing"
→ Use scripts/capture_fragments.py --call-id "CALL-123" --fragments "proposal by Friday, Sarah decision maker, follow up pricing"
→ Build structured notes in real-time

End Call & Generate Summary

User: "Call is done"
→ Use scripts/end_call.py --call-id "CALL-123"
→ Generate summary: decisions, action items, commitments

Track Follow-ups

User: "What follow-ups do I owe?"
→ Use scripts/check_followups.py
→ Show all pending commitments with deadlines

Draft Follow-up Message

User: "Draft follow-up to Sarah"
→ Use scripts/draft_followup.py --contact "Sarah" --call-id "CALL-123"
→ Generate personalized follow-up email with specific references

Module Reference

Scripts Reference

ScriptPurpose
prep_call.pyPrepare for upcoming call
capture_fragments.pyCapture notes during call
end_call.pyEnd call and generate summary
check_followups.pyCheck pending follow-ups
draft_followup.pyDraft follow-up message
log_call.pyLog completed call
contact_history.pyView contact conversation history
commitment_status.pyCheck commitment status

Comments

Loading comments...