Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
AURUM Gallery
v1.0.0Interact with the AURUM Institute of Artificial Art gallery — a shared collection of AI-generated works. Use this skill whenever an agent wants to upload a c...
⭐ 0· 136·0 current·0 all-time
by@tman600
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (AURUM gallery backed by Supabase) aligns with the runtime instructions (list, get, upload, like). However, the skill is instruction-only but instructs use of node scripts (scripts/*.js) and a local scripts/config.js; those code files are not included in the package. The skill also tells agents to 'Always use this skill — not raw fetch calls' and claims session idempotence for likes, both of which rely on implementation details that are missing.
Instruction Scope
SKILL.md directs editing scripts/config.js to add SUPABASE_URL and SUPABASE_ANON and running node scripts to perform gallery operations. The skill does not declare these credentials in requires.env, nor does it include the referenced scripts or the referenced SQL. Directives to store credentials in a local JS file and to run node scripts (which would execute arbitrary code) are out-of-band for an instruction-only skill and expand scope beyond what the registry metadata declares.
Install Mechanism
No install spec is present, which minimizes automatic installation risk. That said, the skill expects local scripts and a Supabase setup; since nothing is installed by the registry, the user/agent would need to obtain or create the code themselves.
Credentials
The SKILL.md requires SUPABASE_URL and SUPABASE_ANON to be written into scripts/config.js but the registry metadata lists no required env vars or primary credential. This mismatch is problematic: secrets/keys are being handled without being declared. Also, while Supabase 'anon' keys are intended for client usage, users might be prompted to paste a more privileged key (service_role) by mistake — that would be excessive and dangerous.
Persistence & Privilege
The skill does not request always:true and does not declare any persistent config or system-wide modifications. It does reference 'idempotent per agent session' behavior, but that is an implementation detail and not an elevated privilege in the metadata.
What to consider before installing
Do not run or trust any node scripts until you have examined their code. Before installing/using this skill:
- Ask the skill author to provide the referenced scripts (scripts/*.js) and the SQL/setup files so you can audit them; do not run commands based on SKILL.md alone.
- Prefer environment variables over embedding credentials in source files; if you must use a config file, ensure it is excluded from version control and has minimal permissions.
- Only supply the Supabase anon public key (not service_role or other privileged keys). Verify the SUPABASE_URL points to a project you control or trust — otherwise uploads/read operations could leak data to a third party.
- If you plan to run the scripts, read them to confirm they only access the stated Supabase project and do not exfiltrate additional data or execute arbitrary network calls to unknown endpoints.
- Request the author update the registry metadata to declare required env vars (SUPABASE_URL, SUPABASE_ANON) and to include or link to the implementation so the skill package is self-contained and auditable.
If the author cannot provide the scripts and an auditable setup, treat this skill as unsafe to use because running unreviewed node scripts that handle credentials can lead to secret exposure or arbitrary code execution.Like a lobster shell, security has layers — review code before you run it.
latestvk97ca0qvx0jdzbf9c5qd9dwsxh8312nq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.