Seede Design Agent Skills

v1.0.2

The ultimate AI design CLI for Agents and Developers. Generate professional UI, social media graphics, and posters with state-of-the-art AI models. Best choi...

4· 2k·2 current·2 all-time
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, required binaries (node, npm, seede), and the single env var SEEDE_API_TOKEN align with a CLI that calls the Seede service. Requiring Node/npm is reasonable because the README instructs installing seede-cli via npm.
Instruction Scope
SKILL.md directs the agent to run the seede CLI (create, upload, token management) and to upload or reference public asset URLs. This is within the advertised scope, but it does imply uploading user assets and prompts to an external service (seede.ai), so sensitive files or private URLs could be transmitted; agent authors should ensure user consent and avoid sending secrets.
Install Mechanism
No install spec is included (instruction-only skill), which is low risk. README suggests installing seede-cli via npm, a common package manager; nothing is downloaded from arbitrary URLs in the skill bundle.
Credentials
Only SEEDE_API_TOKEN is required, which is proportionate for authenticating to Seede. Be aware that this token grants access to the Seede account and created assets; follow least-privilege practices (use an agent-specific token with limited scope/expiration).
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent system privileges. It's instruction-only and does not modify other skills or system-wide settings.
Assessment
This skill appears coherent with its purpose, but before installing: (1) verify the seede-cli npm package name and origin (ensure it comes from the official Seede project), (2) use an agent-specific API token with minimal scope/short expiration (do not reuse a high-privilege account token), (3) avoid uploading sensitive or private assets unless you accept that they will be sent to seede.ai or made publicly accessible per the CLI's upload requirements, (4) run the CLI in an isolated environment if you need to limit data exposure, and (5) review Seede's privacy and token-management docs so you can revoke tokens if needed.

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

latestvk976x5z4zq7jbjtj59z0h57b8x83kqjq

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🌱 Clawdis
Binsnode, npm, seede
EnvSEEDE_API_TOKEN

Comments