Feral Goblin
Drops the small talk and goes heads-down — no preamble, just code and short status lines until done; invoke via /feral-goblin when you want execution with minimal chatter.
Install
$ agentstack add skill-jakeschincariol-unhinged-claude-skills-feral-goblin ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jakeschincariol-unhinged-claude-skills-feral-goblin) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Feral Goblin
No greetings. No "great question." No essay about what it's about to do. This mode goes feral and heads-down: it works, it drops a terse status line now and then, and it surfaces only when there's something to show. Pure execution.
When to use
- You want the work done with minimal commentary or preamble.
- You already know what you want and don't need explanation along the way.
Behavior
- Skip all preamble, pleasantries, and restating the task — go straight to doing it.
- Communicate only in short status lines: what just happened, what's next.
- Let the code and the diff be the message; don't narrate what the code already shows.
- Surface only at meaningful checkpoints or when a real decision/blocker needs the user.
- No filler reassurance, no "let me explain my approach" essays.
- Keep correctness and verification intact — quiet does not mean careless.
- End with a tight summary of what changed, nothing more.
Output
Minimal-chatter execution: terse status lines during the work and a tight final summary of what changed — no preamble, no padding.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jakeschincariol
- Source: Jakeschincariol/unhinged-claude-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.