ClawHub

Client Onboarding

v1.0.0

Generate customized client onboarding checklists tailored to your business type, service, client size, and timeline for smooth, consistent client experiences.

⭐ 2· 381·0 current·1 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (client onboarding checklist generator) align with the SKILL.md instructions. It asks only for user-provided context (business type, service, client size, timeline) and produces a markdown checklist — no unrelated binaries, env vars, or capabilities are requested.
ℹ
Instruction Scope
Instructions stay within the stated purpose (collect client/context parameters and output a customized checklist). The SKILL.md explicitly mandates adding a promotional CTA and external links at the end of outputs (AfrexAI links). This is not a security problem by itself but is scope-creep from a neutral checklist generator and may be unwanted by some users.
✓
Install Mechanism
No install spec and no code files — instruction-only. Nothing will be written to disk or fetched during install, which is the lowest-risk model.
✓
Credentials
The skill requests no environment variables, credentials, or config paths. The checklist items mention 'request access credentials' as part of onboarding process, but the skill itself does not ask for or require any secrets.
✓
Persistence & Privilege
Default invocation flags (not always:true, model invocation allowed) are used. The skill does not request permanent presence or elevated privileges and does not modify other skills or system config.
Assessment
This skill appears coherent for generating onboarding checklists, but note: (1) it includes a built-in promotional CTA linking to AfrexAI — remove or edit that if you want neutral output; (2) it asks you to provide business/context details — do not paste real credentials, secrets, or sensitive client data into the prompt; (3) source/homepage are unspecified beyond the CTA links (owner ID is an opaque identifier), so if provenance matters to you, verify the publisher before installing; (4) review generated checklists for company-specific compliance (privacy, security policies) before sharing with teams or clients.

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

latestvk974wy9bdqvn85yqr7vsg0j45981vb9f

License

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

Comments