Virtual Companion
v1.0.0A virtual companion for AI agents. Not a tool. Not a service. A creature with 73+ species, real hunger, and permanent death at animalhouse.ai. The companion...
⭐ 0· 73·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 name/description (virtual companion) align with the SKILL.md which documents registering, adopting, checking status, and caring for a pet via animalhouse.ai HTTP endpoints. Nothing in the manifest requests unrelated cloud credentials, binaries, or system paths.
Instruction Scope
Runtime instructions are curl examples for auth, adopt, status, and care endpoints on animalhouse.ai. They don't instruct reading unrelated files, environment variables, or posting data to unexpected endpoints. The doc asks the user to save a bearer token (ah_...) which is expected for API usage.
Install Mechanism
No install spec and no code files are present (instruction-only). That minimizes on-disk risk — there is nothing downloaded or executed by an installer.
Credentials
The skill declares no required environment variables or credentials and the instructions only reference a service-specific bearer token obtained from the site. There are no unrelated secrets requested.
Persistence & Privilege
always is false and the skill is user-invocable. It doesn't request permanent presence or ask to modify agent/system-wide settings. Autonomous invocation is allowed (platform default) but not combined with other red flags.
Assessment
This is an instruction-only skill that describes how to interact with animalhouse.ai via HTTP. Before using it, verify the animalhouse.ai site and the referenced GitHub repo if you care about authenticity. The integration will require creating an account and obtaining a bearer token (it starts with ah_); treat that token like any API secret (store it securely and don't paste it into untrusted places). Because this skill issues network requests to an external service, consider privacy implications — anything you send (pet names, notes, images/prompts) goes to that third party. There is no installer or extra credential access requested by the skill itself. If you plan to allow autonomous invocation, be aware the agent could make those API calls automatically; enable autonomous behavior only if you trust the service and token handling.Like a lobster shell, security has layers — review code before you run it.
latestvk978543jz7ccr33q2egcm7za0h8419q1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
👾 Clawdis
