Install
$ agentstack add skill-t3chnaztea-batocera-skills-template ✓ 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.
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
Batocera Yourskill
One or two sentences: what this skill covers and that it assumes the connection pattern, filesystem model, and safety doctrine from batocera-ops. Cross- reference sibling skills by name (batocera-roms, batocera-display, batocera-tuning, batocera-maintenance) rather than repeating their content.
Guidelines for a good Batocera skill
Delete this section in your real skill; it's guidance for authoring.
- Name:
batocera-, lowercase and hyphens only. The directory name
MUST equal the frontmatter name.
- Description: starts with "Use when…", lists concrete triggers and keywords,
ends with a "not for X, use Y" pointer. No workflow summary (an agent will follow the description instead of reading the body).
- Original prose only. Do not paste text from the Batocera wiki or other
docs — write the lesson in your own words and link the wiki as the canonical manual. Ship institutional knowledge the wiki doesn't have.
- Parameterize everything host-specific. Use
$BATOCERA_HOST, never a real
IP; read passwords from env; never commit tokens, credentials, MQTT secrets, or personal ROM/library specifics.
- Non-destructive doctrine. Prefer hide/move/append over delete/overwrite;
back up configs and gamelists before editing; never inject synthetic input.
- Verify against ground truth. Show the reader how to confirm the change
(read the generated config, launch + screenshot), not just make it.
- Keep
SKILL.mdunder ~500 lines. Push heavy detail intoreferences/*.mdand
reusable code into scripts/. Scripts should be --dry-run-first where they mutate, idempotent, and self-documenting in a header.
Overview
What this is and the core principle in 1–2 sentences.
When to use
Symptoms and situations (bullets). When NOT to use.
[Your sections]
Quick-reference tables, worked examples, the specific traps you learned. One excellent example beats five generic ones.
References
- [references/topic.md](references/topic.md) — heavy detail loaded on demand.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: t3chnaztea
- Source: t3chnaztea/batocera-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.