sequenzy
v1.0.0Agent guide for operating Sequenzy. Use when Codex needs to authenticate, inspect identity, manage subscribers, send a transactional email, read delivery sta...
⭐ 0· 79·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's name and description match the SKILL.md: it documents authentication, subscriber management, transactional sends, and stats via the sequenzy CLI and API. Nothing in the files requests unrelated cloud credentials, system-level access, or unrelated binaries.
Instruction Scope
The runtime instructions tell an agent to use the sequenzy CLI, check SEQUENZY_API_KEY, and prefer inspection before mutation. They reference repository paths (packages/cli/...) as the source of truth and mention reading/storing keys in Bun.secrets or local config. These references are reasonable for a CLI guide, but the skill does assume access to local CLI/config state and the project repo for authoritative command wiring; it does not instruct exfiltration or access to unrelated files.
Install Mechanism
No install spec or code is included (instruction-only), so nothing is downloaded or written to disk by the skill itself. This is the lowest-risk install posture.
Credentials
The documentation references SEQUENZY_API_KEY, SEQUENZY_API_URL, and SEQUENZY_APP_URL as the expected environment variables for using the CLI, but the registry metadata declares no required env vars. This is a minor metadata omission: the referenced env vars are directly relevant to the skill's purpose and not excessive or unrelated.
Persistence & Privilege
The skill does not request always:true and is user-invocable. It does not modify other skills or request persistent elevated privileges. Autonomous invocation is allowed by default but is not combined with other red flags here.
Assessment
This is a documentation-only guide for the Sequenzy CLI and appears coherent. Before installing/using it: (1) confirm you have the sequenzy CLI available or plan to use the API (the guide assumes local CLI/config access); (2) only provide SEQUENZY_API_KEY to the agent or environment if you trust the agent/session—do not paste secrets into chat; (3) be aware the guide may read local CLI config or Bun.secrets if you use sequenzy login; (4) if a workflow is unsupported in the CLI, follow the guide's advice and use the dashboard or direct API instead. The main actionable fix would be to update the skill metadata to declare SEQUENZY_API_KEY/SEQUENZY_API_URL as expected env vars so the registry and docs align.Like a lobster shell, security has layers — review code before you run it.
latestvk9714ebyknhsw7stjz5f1d9q1s83cya7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.