Skip to content
TrustedSkillsbeta
Back to all skills

Sensitivity Check

Checked
jwynia·vlatest·other

This "Sensitivity Check" assesses generated content for potentially offensive or harmful language, promoting safer and more inclusive outputs.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jwynia/agent-skills --skill sensitivity-check --full-depth -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jwynia

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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 undeclared network calls: passed

    Makes no network calls.

    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.

  • 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 jwynia/agent-skills at e02ec7e226.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
e02ec7e226
Manifest
skills/creative/fiction/application/sensitivity-check/SKILL.md
Scanned
3 files, 1,245 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Sensitivity Check skill evaluates fictional content for potential harm concerns related to representation accuracy and cultural sensitivity. It identifies issues that might negatively impact readers from affected communities, while respecting the author's creative intent. The goal is not censorship but rather to provide constructive feedback and alternative approaches to promote more accurate, respectful, and authentic representations within a story. This skill focuses on identifying specific passages of concern and offering suggestions for improvement.

When to use it

  • When writing stories that depict cultures or communities different from your own.
  • To proactively identify potential issues with gender dynamics or portrayals of women/non-binary characters.
  • To ensure cultural elements are presented accurately and respectfully, avoiding appropriation or misrepresentation.
  • When exploring sensitive themes and wanting to be mindful of the potential impact on readers.

Key capabilities

  • Evaluative: Flags concerns and provides reasoning behind them.
  • Informative: Offers context related to potentially harmful representations.
  • Collaborative: Works with authorial intent, not against it.
  • Specific: Points to concrete passages with specific concerns.
  • Constructive: Suggests alternative approaches and paths forward.
  • Focuses on two evaluation states: Cultural Appropriation Concerns (S1) and Gender/Misogyny Issues (S2).

Example prompts

  • "Please evaluate this scene for potential cultural appropriation concerns."
  • "Can you review this character's portrayal and identify any problematic gender dynamics?"
  • "I want to ensure I’m representing [specific culture] respectfully in my story. Could you perform a sensitivity check on these passages?"

Tips & gotchas

  • This skill is not prescriptive; it does not dictate what can or cannot be written, but rather offers guidance and alternative perspectives.
  • The evaluation represents one perspective and isn't intended to be the final word on representation.
  • Consider centering voices from within the represented communities for a more comprehensive understanding.