ClawHub

In Person Prospecting Route Planner

v1.0.0

Plan a Hub-and-Spoke in-person prospecting route for a field sales day — mapping drop-by prospect visits around preset appointments to eliminate random drivi...

⭐ 0· 15·0 current·0 all-time
byHung Quoc To@quochungto
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
The name/description (hub-and-spoke in-person route planning) matches the SKILL.md: it expects preset appointments, a prospect list with addresses, and driving time and produces a route sheet. No unrelated binaries, environment variables, or external credentials are requested.
ℹ
Instruction Scope
The SKILL.md directs the agent to look for and read files in a document/map directory (appointments.csv, prospect-list.csv, calendar exports) and to produce route-sheet-{date}.md. Reading those files is in-scope for routing. One caveat: mapping/routing typically requires address geocoding or a routing API; the skill does not declare any mapping API credentials. If the skill attempts to call external mapping services at runtime, the user should expect it to request explicit access or API keys.
✓
Install Mechanism
No install spec and no code files — instruction-only. This is lowest-risk from an install perspective (nothing is downloaded or written during install).
✓
Credentials
The skill requests no environment variables, no credentials, and no config paths. Its need to read local prospect/calendar files is proportional to its purpose. There are no unexplained secret requests.
✓
Persistence & Privilege
Flags show no always:true and default autonomous invocation is allowed (normal). The skill does not request persistent system-wide privileges or to modify other skills.
Assessment
This skill appears coherent and does what it says: read your day's appointments and prospect list, then produce a Hub-and-Spoke route sheet. Before installing/running: (1) confirm you want the agent to read files from the specified directory (appointments/prospect CSVs) because these contain addresses and PII; (2) be ready to provide addresses or a calendar export manually if you prefer not to give file access; (3) expect that accurate routing may require geocoding or a mapping/routing API — the skill doesn't declare API credentials, so if it asks to call an external mapping service, require an explicit prompt and only provide minimal API keys if you trust the endpoint; (4) review the produced route-sheet for sensitive data before sharing. If you want higher assurance, open the full SKILL.md and scan for any instructions that call external endpoints or request unexpected files, and ask the skill author how geocoding/routing is implemented.

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

bdrvk97737fgh8yvqk2237ww3dkvk5851cz8bookforgevk97737fgh8yvqk2237ww3dkvk5851cz8field-salesvk97737fgh8yvqk2237ww3dkvk5851cz8in-personvk97737fgh8yvqk2237ww3dkvk5851cz8latestvk97737fgh8yvqk2237ww3dkvk5851cz8prospectingvk97737fgh8yvqk2237ww3dkvk5851cz8salesvk97737fgh8yvqk2237ww3dkvk5851cz8sdrvk97737fgh8yvqk2237ww3dkvk5851cz8territory-managementvk97737fgh8yvqk2237ww3dkvk5851cz8

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📚 Clawdis

Comments