client-flow
v1.0.0Automated client onboarding and project lifecycle management. From a single message, creates Google Drive/Dropbox project folder structure, generates project...
⭐ 0· 690·1 current·1 all-time
byArik Tulchinsky@ariktulcha
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill's name and description (automated client onboarding across files, email, calendar, and task managers) match the SKILL.md instructions. It consistently describes creating folders, drafting/sending email, scheduling calendar events, creating tasks, and maintaining a registry. The skill does not claim or request unrelated capabilities.
Instruction Scope
Instructions stay on-task but assume availability of many external services (Google Drive via a 'gog' tool, Dropbox skill, Notion, email skill, Google Calendar/Outlook, multiple task managers, OpenClaw cron). The skill also instructs creating files on the local filesystem (default ~/Clients/) and saving the generated brief and registry. There is some ambiguity about explicit confirmation flows (it says 'with user confirmation' for sending email, but scheduling/creating resources may rely on connected skills' behaviors).
Install Mechanism
Instruction-only skill with no install spec and no code files. No packages or downloads are requested; risk from install mechanism is low.
Credentials
The skill declares no required environment variables or primary credential, which is consistent because it delegates actions to other skills/integrations. However, meaningful functionality (sending mail, creating Drive folders, scheduling calendar events, creating tasks) requires account access/credentials held by other connected skills — users should confirm which integrations the agent will actually use and what tokens/permissions those integrations have.
Persistence & Privilege
The skill is not always-enabled and does not request special persistent privileges. It does instruct maintaining a 'master client registry' (a file it will create/update), which is normal for a project-management skill but means it will write and persist client data locally or in connected storage.
Assessment
This skill appears to do what it says, but it orchestrates many external services. Before installing or invoking it: (1) confirm which connected integrations (email, Google Drive/Calendar, Dropbox, Notion, Todoist/Asana/ClickUp/Linear, GitHub, etc.) the agent will use and review their permission scopes; (2) verify that the skill will ask for your explicit confirmation before sending emails or creating calendar events; (3) if you don't want files written to disk, check and configure the local base path or disable local creation; (4) test with a dummy client/project first to see exact behavior; and (5) be aware the skill will persist a master client registry containing client/contact/project data — ensure you are comfortable with where that registry is stored and who can access it.Like a lobster shell, security has layers — review code before you run it.
latestvk97a1p0wb59nb54vfnqzpssnnn816fz1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🤝 Clawdis