ClawHub
Skill flagged — suspicious patterns detected

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

Customer Onboarding

v1.1.0

Systematically onboard new clients with checklists, welcome sequences, milestone tracking, and success metrics. Reduce churn by nailing the first 90 days.

⭐ 0· 695·0 current·0 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name and description match the SKILL.md: checklist generation, email sequences, kickoff agendas, success metrics, and risk flags. The skill requests no binaries, env vars, or installs that would be unrelated to onboarding.
ℹ
Instruction Scope
SKILL.md contains specific, scoped instructions for producing checklists, email sequences, agendas, metrics, and risk indicators. It does not instruct the agent to read system files, credentials, or external services. Note: 'Risk Detection' implies evaluating engagement signals (CRM, support tickets); the skill does not specify integrations or how data should be provided, so a user should avoid giving it direct access to production systems unless a clear integration mechanism is declared.
✓
Install Mechanism
No install spec and no code files — instruction-only — so nothing is downloaded or written to disk by the skill itself.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. That aligns with an instruction-only authoring/assistant skill that generates documents and checklists.
✓
Persistence & Privilege
always is false and there is no install that modifies agent configuration. Autonomous invocation is allowed (platform default) but the skill does not request elevated or persistent privileges.
Assessment
This skill appears internally consistent and safe as an instruction-only helper. Before using it with real client data or integrating it with your CRM/support tools, confirm how you will provide engagement or ticket data (prefer manual copy/paste or a vetted integration rather than handing over credentials). If you later find a version that adds an install step or requests API keys, review the requested permissions and integration endpoints closely (prefer OAuth or well-known APIs). Avoid sharing PII unless you trust how that data is stored and processed.

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

latestvk97f2kw0d0skzcm8y2qp4ja7yh8138kv

License

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

Comments