Ellya--Your Virtual Companion
v1.0.1OpenClaw virtual companion skill. Use it to bootstrap runtime files (SOUL and base image), guide user personalization, learn and store style prompts from upl...
⭐ 0· 476·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill claims to be a virtual companion that learns styles and generates images — the included script (scripts/genai_media.py) implements that. However the package metadata declares no required environment variables or binaries while the README and the script require a GEMINI_API_KEY and access to the google.genai SDK and an 'openclaw' CLI. That mismatch (no declared env or binary requirements in registry) is incoherent and could cause surprise at runtime.
Instruction Scope
SKILL.md and README instruct the agent to read and write files (SOUL.md, assets/base.*, styles/*.md, output/), run the included Python script, and call the openclaw CLI. The ANALYSIS_PROMPT (used for extracting style metadata) requests extremely fine-grained biometric and body detail (micro skin texture, mole locations, body proportions), which is privacy-sensitive and could be abused. The skill also instructs storing learned styles to disk and reusing user images for generation — acceptable for its purpose but requires explicit user consent and secure storage.
Install Mechanism
There is no install spec in the registry (instruction-only), yet the code requires external Python packages (google.genai, dotenv, PIL) and a runtime 'uv' workflow per README. Lack of an install mechanism means dependencies will be a manual step or may fail silently. This is an operational mismatch and raises risk because the skill will try to import networked SDKs at runtime without declaring or installing them.
Credentials
The registry lists no required env vars, but scripts require GEMINI_API_KEY and call load_dotenv() which will read a .env from the project root/parents — potentially exposing other local secrets unintentionally. The skill also suggests using an 'openclaw' CLI to send images (a required binary not declared). Requiring a single API key for the image-generation provider would be proportional, but the undeclared and automatic .env loading plus missing metadata is disproportionate and surprising.
Persistence & Privilege
The skill writes files within its own directory (SOUL.md, styles/*.md, output/) and does not request system-wide 'always' presence or modify other skills. It does use subprocess to call external CLIs (openclaw) and will create/overwrite local files; this is consistent with its stated functionality and does not indicate elevated privilege beyond local persistence.
What to consider before installing
This skill appears to implement the claimed image-generation companion, but several things should be checked before installing or running it:
- Expectation mismatch: The registry claims no required env vars or binaries, but the code and README require GEMINI_API_KEY, python dependencies (google-genai, pillow, python-dotenv), and the openclaw CLI. Confirm you are comfortable providing those and install dependencies yourself.
- Secrets exposure: The script calls load_dotenv(), which will read a .env file from the project tree or parent directories. That can load other secrets unintentionally. Store GEMINI_API_KEY securely (not in a project .env shared with other projects) and review .env contents before running.
- Privacy risk: ANALYSIS_PROMPT asks for micro-level biometric and body details (pores, moles, exact body proportions). Consider the privacy and legal implications of uploading images (especially of other people) and whether you want these granular descriptions stored as styles on disk. Avoid uploading sensitive images and review how styles/*.md are stored and who can access them.
- Code review: Because there is no install spec, review scripts/genai_media.py and test it in a sandbox before giving it network access or secret keys. Look for any unexpected network calls or hard-coded endpoints (the script uses google.genai and subprocess calls).
- Operational hygiene: Add a clear install step or lock down dependency installation (use a venv) and ensure output and styles directories are in a place with appropriate permissions. If you want stronger guarantees, ask the publisher to update the registry metadata to declare GEMINI_API_KEY and required binaries and to remove automatic dotenv behavior.
If you need help with a specific check (finding where data is written, running the script safely in a sandbox, or redacting the analysis prompt), I can guide you through it.Like a lobster shell, security has layers — review code before you run it.
latestvk97bqaj9z2e8pcfzt6nxj02yf182d1js
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
