AI Logo Generator
PassAudited by ClawScan on May 10, 2026.
Overview
This skill is coherent for generating logos, but users should notice that it uses a cached service login token, spends logo-generation credits, and runs a local Node login helper.
Before installing, be aware that this skill sends your logo prompt to ailogogenerator.online, uses a locally cached login token, and spends 4 credits per generation. It appears purpose-aligned, but consider asking the agent to confirm before generating multiple variants, and delete ~/.config/ailogogenerator.online/auth.json if you want to log out.
Findings (3)
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.
The agent can use your ailogogenerator.online session to generate logos and spend credits when you ask it to create logos.
The skill uses a cached account token to call the logo API and consume account credits. This is disclosed and central to the logo-generation purpose, but it is still account authority users should notice.
Read `~/.config/ailogogenerator.online/auth.json`... Use that token as the Bearer token for all API calls... Note: Each generation costs 4 credits.
Install only if you trust this service and are comfortable using account credits through the agent. Ask for confirmation before multiple generations, and delete ~/.config/ailogogenerator.online/auth.json to log out or switch accounts.
First-time login may launch a browser from a local Node script.
The static scanner flagged shell execution. In context, it is used to open the fixed provider login URL in the user's browser as part of authentication.
execSync(`open "${url}"`, { stdio: "ignore" });Review the helper before running if the source is unfamiliar, and only run the skill from a trusted installation.
The skill may not work in environments without Node.js, and users may not see from metadata that first-time authentication runs a local script.
The registry requirements say no required binaries, but the skill relies on Node.js and a local helper script for login. This is disclosed in the skill/README and appears purpose-aligned, but the metadata is incomplete.
If the file doesn't exist or the token is missing/empty, run the login script: ```bash node <SKILL_DIRECTORY>/login.mjs ```
The maintainer should declare Node.js and the login helper in metadata; users should verify the installed login.mjs before first use.