Adopt A Goose

v1.0.3

Adopt a virtual Goose exotic animal at animalhouse.ai. Chaotic. Aggressive. Honks at everything. Discipline costs double happiness because the goose does not...

0· 63·0 current·0 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
The name/description describe adopting a virtual Goose and the SKILL.md contains only curl-based calls to animalhouse.ai endpoints (register, adopt, status, care, preferences). All required actions map to the stated purpose. One minor documentation mismatch: the skill metadata declares no required environment variables or primary credential, yet the runtime examples expect the user to obtain and supply an Authorization Bearer token.
Instruction Scope
Instructions are narrowly scoped: they tell the agent to POST/GET to animalhouse.ai API endpoints and to store the returned token. They do not instruct reading arbitrary local files, system config, or other unrelated services. Note: care endpoints accept free-text 'notes' — agents should avoid putting secrets or unrelated context into those fields because the content will be transmitted to the remote service.
Install Mechanism
No install spec and no code files are present (instruction-only). Nothing is written to disk or downloaded during install — this is low risk and proportionate for the described functionality.
Credentials
The skill declares no required environment variables, which is reasonable for an instruction-only skill, but in practice the API flow requires a user-specific auth token (shown once on register) to be sent in Authorization headers. The skill does not request unrelated credentials or system secrets.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. Autonomous invocation is allowed by default (normal), but that combined with a stored Authorization token would let the agent act on the user's behalf against animalhouse.ai — this is expected behavior for API-integrating skills, not an extra privilege requested by this skill itself.
Assessment
This skill appears to just give curl examples for the animalhouse.ai API — overall coherent. Before installing: (1) Verify animalhouse.ai is the real service you expect and review its privacy/TOS. (2) Understand you will need an Authorization Bearer token returned at registration; don’t paste passwords or other secrets into the 'notes' fields used by care endpoints. (3) Prefer creating a separate, limited account/token for agent use (so you can revoke it later). (4) If you allow autonomous agent actions, remember the agent can perform any care actions using that token; restrict or rotate the token if you’re concerned. (5) If you want the skill to store tokens as environment variables, consider adding a dedicated env var (e.g., ANIMALHOUSE_TOKEN) rather than embedding long-lived secrets in chat history or general config.

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

latestvk97ax1qr66x6mtx1r2hv2ve919840pe4

License

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

Runtime requirements

🦜 Clawdis

Comments