Baby Connect Logger
v1.0.0ActiveCampaign CRM integration for lead management, deal tracking, and email automation. Use for syncing demo leads, managing clinic sales pipeline, and triggering follow-up sequences.
⭐ 1· 2.2k·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The SKILL.md, README, and sample JSON all describe an ActiveCampaign CRM integration and require the 'activecampaign' CLI plus ACTIVECAMPAIGN_URL and ACTIVECAMPAIGN_API_KEY — that matches the declared functionality. However, the registry-level name ('Baby Connect Logger') and the skill content (ActiveCampaign) do not match and the Source/Homepage fields are empty, which is an incoherence in metadata that should be verified.
Instruction Scope
Runtime instructions are limited to using the ActiveCampaign CLI, creating a ~/.config/activecampaign directory, and storing or exporting the ActiveCampaign URL and API key. This stays within the stated purpose. Minor scope notes: the instructions show writing the API key to a plaintext file via echo (and exporting it in shell) — this is common for CLI tools but has security implications (shell history, file permissions) that the user should mitigate.
Install Mechanism
No install spec is provided (instruction-only), so nothing is silently downloaded or written by the skill. The user must already have or install the 'activecampaign' CLI themselves; this is lower risk than an install that fetches arbitrary code.
Credentials
The only required environment items are ACTIVECAMPAIGN_URL and ACTIVECAMPAIGN_API_KEY, which are directly necessary for ActiveCampaign API access. No unrelated credentials, unusual config paths, or extra secrets are requested.
Persistence & Privilege
The skill does not request always:true or any elevated persistence. It is user-invocable and can be invoked autonomously (platform default), which is expected for a skill of this type.
Assessment
Before installing: verify the skill's origin (registry name 'Baby Connect Logger' doesn't match the ActiveCampaign content) — prefer a well-known repo or publisher. Confirm where the 'activecampaign' CLI comes from and inspect its source or package before installing. When providing your ActiveCampaign API key, prefer using environment variables or a config file with strict file permissions (chmod 600); avoid leaving keys in shell history. Use a limited-scope API key if ActiveCampaign supports it and rotate the key after testing. If you need stronger assurance, request a homepage or repository URL from the publisher and review the CLI or any code they provide.Like a lobster shell, security has layers — review code before you run it.
latestvk979ppng0tnakg4v4amspst3k1808ff0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📧 Clawdis
Binsactivecampaign
EnvACTIVECAMPAIGN_URL, ACTIVECAMPAIGN_API_KEY