Neckr0ik Newsletter Manager
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This looks like a legitimate newsletter tool, but it can send AI-written emails to all subscribers and asks for platform API keys without clear approval or scope guardrails.
Install only if you intend to let the agent help manage real newsletters. Use limited-scope platform credentials, review generated content manually, send tests first, and require explicit confirmation before any broadcast to subscribers.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken or low-quality AI-generated newsletter could be sent to an entire subscriber list, affecting reputation and customers.
The documented default send workflow broadcasts a draft to all subscribers, and the artifacts do not state that the agent must obtain explicit review or confirmation before bulk delivery of AI-generated content.
# Send to all subscribers neckr0ik-newsletter-manager send --id draft-123
Require explicit user approval and content review before any send action; default to test sends or limited segments before sending to all subscribers.
The provided keys may allow actions on newsletter accounts, including sending mail or managing subscribers, depending on the provider permissions.
These commands ask users to provide provider account credentials for newsletter platforms, while the registry metadata declares no primary credential or required environment variables.
neckr0ik-newsletter-manager config set beehiiv.api_key <key> neckr0ik-newsletter-manager config set convertkit.api_key <key> neckr0ik-newsletter-manager config set convertkit.api_secret <secret>
Use least-privilege API keys where possible, avoid sharing production credentials unless necessary, and revoke keys if you stop using the skill.
Users may not know exactly how the documented command is installed, verified, or kept updated.
The artifacts do not provide a clear source or install mechanism even though the documentation describes a CLI and the package includes a script.
Source: unknown; Homepage: none; No install spec — this is an instruction-only skill.
Verify the script source before running it and confirm any local CLI wrapper or installation method yourself.
The skill may run local model commands and may fail or behave differently if Ollama or the named model is not installed.
The script invokes a local Ollama model process for AI content generation. This is purpose-aligned and does not use shell expansion, but it is an undeclared local runtime dependency.
subprocess.run(["ollama", "run", "llama3.2:latest", prompt], capture_output=True, text=True, timeout=60)
Install and trust Ollama separately if you intend to use the generation features, and review prompts before sending generated output.
Subscriber lists, drafts, analytics, and possibly platform settings may remain on disk after use.
The skill persists configuration, drafts, subscriber data, and analytics under a local application directory, which may include subscriber emails and newsletter business data.
self.config_file = self.config_dir / "config.json" self.drafts_dir = self.config_dir / "drafts" self.subscribers_dir = self.config_dir / "subscribers" self.analytics_dir = self.config_dir / "analytics"
Treat the local .newsletter-manager directory as sensitive, restrict filesystem access, and delete or back up stored data according to your privacy needs.