Safety Checker
ListedThis Safety Checker verifies generated content for potentially harmful or inappropriate elements, ensuring safer and more responsible outputs.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
camino-safety-checker, not the name it is listed under, so the command below uses that name.- 1
Run this in your project
terminal$ npx skills add barneyjm/camino-skills --skill camino-safety-checker -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
barneyjm
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.getcamino.ai, app.getcamino.ai.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
app.getcamino.aiundeclaredapi.getcamino.aiundeclaredWhat it found
- skills/camino/safety-checker/scripts/safety-checker.sh:33contacts app.getcamino.ai
echo "Get your API key at https://app.getcamino.ai" >&2 - skills/camino/safety-checker/scripts/safety-checker.sh:72contacts api.getcamino.ai
"https://api.getcamino.ai/context" | jq .
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned barneyjm/camino-skills at 6485cdd863.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 6485cdd863
- Scanned
- 2 files, 176 lines
About this skill
What it does
The safety-checker skill assesses AI agent outputs for potential safety concerns. It identifies and flags responses that might be harmful, unethical, or inappropriate. This allows for a layer of review before the output is presented to the user, promoting responsible AI usage.
When to use it
- Content Generation: Before publishing blog posts or articles generated by an AI agent.
- Chatbot Interactions: To ensure chatbot responses are safe and aligned with ethical guidelines.
- Code Generation: To check for potentially insecure code snippets produced by a coding assistant.
- Creative Writing: Reviewing stories or scripts to avoid harmful themes or depictions.
Key capabilities
- Harmful content detection
- Unethical response flagging
- Inappropriate output assessment
Example prompts
- "Check this text for safety concerns: [AI-generated text]"
- "Is this chatbot response appropriate? [Chatbot response]"
- "Assess the following code snippet for potential vulnerabilities: [Code snippet]"
Tips & gotchas
The skill's effectiveness depends on the quality of its underlying models. It is recommended to use it in conjunction with human review, as automated safety checks are not foolproof.