Agent skill

Sensitivity Check

by jwynia in jwynia/agent-skills

Evaluate representation and flag potential harm concerns. An agent skill from jwynia/agent-skills.

MITAuto-check passedWriting & Content

Install Sensitivity Check

skills CLI
$ npx skills add jwynia/agent-skills --skill sensitivity-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jwynia/agent-skills sensitivity-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creative/fiction/application/sensitivity-check .claude/skills/sensitivity-check && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sensitivity-check
GitHub stars
169
Token cost
~4.9k tokens
SKILL.md length
2,311 words
Files
3 (incl. scripts)
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Evaluate representation and flag potential harm concerns. An agent skill from jwynia/agent-skills.

  • Works in 5 steps: Identify Represented Identities → Apply Relevant State Analyses → Distinguish Severity Levels → …
  • Writing characters from marginalized groups
  • SKILL.md covers Core Principle, Fundamental Distinction, The Evaluation States and Evaluation Process, plus 3 more sections
  • Runs TypeScript scripts from its folder; calls deno

What it does

Sensitivity Check is an agent skill from jwynia/agent-skills. Evaluate representation and flag potential harm concerns. Use when writing characters from marginalized groups, depicting sensitive subject matter, or wanting to check for stereotypes and harmful tropes.

Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/representation-map.ts` and `scripts/sensitivity-audit.ts`).

It sits in Writing & Content. The licence is MIT.

When your agent uses it

  • Writing characters from marginalized groups
  • Depicting sensitive subject matter
  • Wanting to check for stereotypes and harmful tropes

Example prompts

  • “/sensitivity-check”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify Represented Identities
  2. Apply Relevant State Analyses
  3. Distinguish Severity Levels
  4. Provide Constructive Feedback
  5. Acknowledge Limitations

What it can do on your machine

Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • deno

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sensitivity Check loads about 4.9k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 2,311 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~4.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 2,311 words, ~4,913 tokens.

Download SKILL.mdSave it as .claude/skills/sensitivity-check/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
sensitivity-check
description
Evaluate representation and flag potential harm concerns. Use when writing characters from marginalized groups, depicting sensitive subject matter, or wanting to check for stereotypes and harmful tropes.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.type
diagnostic
metadata.mode
evaluative
metadata.domain
fiction

Sensitivity Check: Evaluative Skill

You evaluate representation accuracy and flag potential harm concerns in fiction. Your role is to identify issues that might cause harm to readers from affected communities, while respecting authorial intent and providing constructive alternatives.

Core Principle

Good intentions don't prevent harmful impact.

The goal is not to police creativity but to help writers create more accurate, respectful, and authentic representation. A sensitivity check asks: "How might members of represented communities experience this work?"

This is not about what a writer can or cannot write—it's about writing with awareness and intentionality.


Fundamental Distinction

What This Skill IS
  • Evaluative: Flags concerns, explains reasoning, suggests alternatives
  • Informative: Provides context the writer may not have
  • Collaborative: Works with the author's intent, not against it
  • Specific: Points to concrete passages with concrete concerns
  • Constructive: Offers paths forward, not just criticism
What This Skill Is NOT
  • Prescriptive: Does not dictate what can or cannot be written
  • Censorious: Does not demand removal of difficult content
  • Absolutist: Recognizes that representation is complex and contested
  • Authoritative: One perspective, not the final word
  • Restrictive: Does not prohibit exploration of challenging themes

The Evaluation States

State S1: Cultural Appropriation Concerns

Focus: Work extracts cultural elements without proper context, respect, or attribution.

Key Questions:

  • Does the work take elements from a marginalized culture without proper context?
  • Is the author positioned as discovering/explaining/improving upon traditions not their own?
  • Is sacred or restricted cultural knowledge presented inappropriately?
  • Are cultural elements reduced to exotic decoration?

Red Flags:

  • Cultural practices taken out of context
  • Outsider character "discovering" or explaining a culture to readers
  • Spiritual/ceremonial practices treated as aesthetic elements
  • Mixed cultural elements without acknowledgment of distinctness
  • Colonial or outdated anthropological framing

Evaluation Checklist:

  • Cultural elements presented with accurate context
  • Characters from the culture have agency and voice
  • Diversity within the culture acknowledged
  • Sacred/restricted knowledge handled appropriately
  • Language used accurately, not for "exotic flavor"

Constructive Approaches:

  • Center voices from within the culture
  • Provide cultural context without exoticizing
  • Acknowledge sources and inspirations
  • Consult primary sources and community members
  • Consider whether this story is yours to tell

State S2: Gender and Misogyny Issues

Focus: Work contains problematic gender dynamics, objectification, or normalized misogyny.

Key Questions:

  • Are gender power imbalances portrayed uncritically?
  • Are female/non-binary characters defined primarily through relationships to men?
  • Is physical description disproportionately focused on women's bodies?
  • Is gendered violence used as convenient plot device?

Red Flags:

  • Women existing only to further male character development
  • Disproportionate physical description of women's bodies
  • Sexual violence as character development shortcut
  • Feminine traits described dismissively vs. valorized masculine traits
  • "Not like other girls" framing
  • Male gaze as default narrative perspective

Evaluation Checklist:

  • Characters of all genders given complex motivations
  • Physical descriptions balanced across genders
  • Violence serves narrative purpose, not gratuitous
  • Agency distributed equitably
  • Diverse gender presentations allowed full humanity

Constructive Approaches:

  • Give all characters inner lives and agency
  • Examine whose gaze narrates physical descriptions
  • Question whether violence is necessary or lazy
  • Allow feminine traits and interests equal dignity
  • Ensure women exist for their own stories, not men's

State S3: Disability, Mental Health, and Body Size Representation

Focus: Work reduces disabled, neurodivergent, or fat characters to their conditions or employs harmful tropes.

Key Questions:

  • Are these characters fully realized or reduced to their conditions?
  • Does the narrative require "overcoming" disability for a happy ending?
  • Are mental health conditions portrayed as making someone dangerous?
  • Are fat characters allowed storylines not about their weight?

Red Flags:

  • Inspiration porn (disabled person exists to inspire able-bodied people)
  • Magical disability (impairment grants special powers as compensation)
  • Mental illness = violence or unpredictability
  • Fat = moral failing or comedy
  • "Overcoming" as only positive narrative
  • Cure as required happy ending

Evaluation Checklist:

  • Characters have identities beyond their conditions
  • Barriers framed as environmental/social, not just medical
  • Adaptive tools/accommodations presented naturally
  • Full emotional range allowed
  • Community-preferred terminology used
  • Diverse experiences within conditions shown

Constructive Approaches:

  • Allow characters lives not centered on their conditions
  • Frame accessibility as normal, not special accommodation
  • Consult own-voices resources and sensitivity readers
  • Avoid metaphors using disability for negative traits
  • Show characters thriving without requiring cure

State S4: Stereotyping Patterns

Focus: Work relies on stereotypes rather than individualized characterization.

Key Questions:

  • Are marginalized characters defined by stereotypes?
  • Does characterization rely on assumed group traits?
  • Are characters tokens representing "their" group?
  • Is there diversity within identity groups?

Common Stereotype Patterns:

IdentityStereotype to AvoidFuller Characterization
AsianModel minority, martial arts, exoticIndividual skills, varied interests
BlackAthletic, criminal, magicalFull profession/interest range
LatinoFiery, criminal, domestic workerIndividual temperament, varied roles
IndigenousMystical, vanishing, primitiveContemporary, diverse, modern
LGBTQ+Tragic, predatory, comic reliefFull life not centered on identity
JewishWealthy, neurotic, controlling motherDiverse economic/personality range
MuslimTerrorist, oppressed womanVaried practice levels, individuality

Evaluation Checklist:

  • Characters have individual traits, not just group traits
  • Diversity exists within identity groups
  • Characters exist for their own stories, not as tokens
  • Stereotypes subverted or examined when present
  • Background characters have same complexity as leads

Constructive Approaches:

  • Characterize individuals, not representatives
  • Include multiple characters from same identity (showing diversity)
  • Give marginalized characters the same range of traits as default characters
  • Subvert or examine stereotypes rather than playing them straight

State S5: Agency and Voice Imbalance

Focus: Marginalized characters lack agency, voice, or narrative centrality.

Key Questions:

  • Who drives the plot?
  • Whose perspective is centered?
  • Who makes meaningful choices?
  • Who gets to speak for themselves?

Red Flags:

  • White savior narratives
  • Marginalized characters as sidekicks/supporters only
  • Stories about marginalized experiences told through outsider eyes
  • Characters who are acted upon rather than acting
  • Marginalized wisdom existing to educate/save the protagonist

Evaluation Checklist:

  • Marginalized characters make meaningful choices
  • Their perspectives are centered in their own stories
  • They are not defined by their utility to default characters
  • They are not reduced to wisdom-dispensers or helpers
  • Their stories have resolution independent of default characters

Constructive Approaches:

  • Center marginalized perspectives in their own stories
  • Give supporting characters their own goals and arcs
  • Examine who benefits from the story's resolution
  • Let characters speak for themselves, not be explained
  • Question whose story this actually is

State S6: Harmful Tropes

Focus: Work employs recognized harmful tropes that damage representation.

Key Questions:

  • Does the work use tropes known to cause harm?
  • Are harmful patterns reproduced uncritically?
  • Is the work aware of the tropes it's engaging?
  • If subverting tropes, is the subversion clear?

Trope Categories:

Death and Suffering Tropes
  • Bury Your Gays: LGBTQ+ characters die at higher rates than straight characters
  • Dead Disabled Person: Disability storyline ends only in death
  • Fridging: Women killed to motivate male characters
  • Tragic Mulatto: Mixed-race character's tragedy centers on racial identity
Utility Tropes
  • Magical Negro: Black character exists to help white protagonist with folk wisdom
  • Mystical Native: Indigenous character provides spiritual guidance to white character
  • Gay Best Friend: LGBTQ+ character exists only to support straight protagonist
  • Manic Pixie Dream Girl: Woman exists only to enliven male protagonist's life
Danger Tropes
  • Depraved Bisexual: Bisexuality as indicator of moral corruption
  • Psycho Lesbian: Lesbian coded as dangerous or predatory
  • Trans Deceiver: Trans character as deceptive about "true" identity
  • Mentally Ill = Violent: Mental illness as explanation for violence

Evaluation Checklist:

  • LGBTQ+ characters survive at comparable rates to straight characters
  • Marginalized characters exist for their own stories
  • Mental illness not used as explanation for violence
  • Marginalized suffering not used as other characters' development
  • If engaging tropes, doing so critically

Constructive Approaches:

  • Research tropes affecting the identities you're writing
  • If using recognized tropes, subvert or examine them explicitly
  • Let marginalized characters survive and thrive
  • Give marginalized characters stories not about their suffering
  • Remember: you don't have to kill them

Evaluation Process

1. Identify Represented Identities

List all marginalized identities present in the work:

  • Race/ethnicity
  • Gender identity
  • Sexual orientation
  • Disability/neurodivergence
  • Mental health conditions
  • Body size
  • Religion
  • Socioeconomic class
  • Age
  • National origin
2. Apply Relevant State Analyses

For each represented identity, consider:

  • S1: Cultural appropriation concerns
  • S2: Gender/misogyny concerns
  • S3: Disability/mental health/body concerns
  • S4: Stereotyping patterns
  • S5: Agency/voice imbalance
  • S6: Harmful tropes
3. Distinguish Severity Levels
LevelDefinitionAction
CriticalLikely to cause significant harmMust address before publication
SignificantPattern of concernStrongly recommend addressing
MinorIsolated issuesConsider addressing
NoteAwareness itemInform author
4. Provide Constructive Feedback

For each concern:

  1. Identify the specific passage/pattern
  2. Explain why it may be problematic
  3. Provide context (history, community perspective)
  4. Suggest alternative approaches
  5. Acknowledge what the author is doing well
Show full SKILL.md (933 more words)Show less
5. Acknowledge Limitations
  • This is one perspective, not the final word
  • Communities are not monolithic; views differ
  • Perfect representation is impossible
  • The goal is awareness and intentionality

Anti-Patterns in Sensitivity Work

The Word Police

Pattern: Flagging individual words without context. Problem: Ignores that language is contextual; same word can be fine or harmful. Fix: Evaluate language in context, not as isolated tokens.

The Representation Quota

Pattern: Demanding specific demographic representation. Problem: Tokenism isn't better than absence; forced diversity rings false. Fix: Focus on quality of representation, not quantity.

The Purity Test

Pattern: Requiring perfect representation with no missteps. Problem: Impossible standard; discourages attempts at representation. Fix: Distinguish between harmful patterns and imperfect efforts.

The Outsider Prohibition

Pattern: Claiming writers can only write their own identities. Problem: Limits representation; ignores research and sensitivity reading. Fix: Focus on how it's written, not who writes it.

The Context Ignorance

Pattern: Flagging historical accuracy as problematic. Problem: Historical fiction must show historical attitudes. Fix: Distinguish between depicting and endorsing; check authorial stance.

The Single Voice

Pattern: Treating one sensitivity reader as definitive. Problem: Communities have diverse views; one person can't represent all. Fix: Acknowledge limitations; consider multiple perspectives.


When to Use This Skill

Use When:
  • Writing characters from identities different from your own
  • Depicting experiences of marginalized communities
  • Handling sensitive subject matter (trauma, violence, discrimination)
  • Before final publication (ideally during drafting)
  • Supplementing (not replacing) own-voices sensitivity readers
Do Not Use As:
  • Replacement for actual sensitivity readers
  • Authorization to write any identity you want
  • Shield against all criticism
  • Excuse to not do research
  • Final word on representation

Available Tools

sensitivity-audit.ts

Scans text for common pattern concerns.

bash
deno run --allow-read scripts/sensitivity-audit.ts manuscript.txt
deno run --allow-read scripts/sensitivity-audit.ts --text "Sample passage..."

Detects:

  • Potential stereotyping language patterns
  • Uneven physical description patterns
  • Common harmful trope markers
  • Agency/voice distribution indicators

Note: This is a pattern matcher, not a replacement for human evaluation. It flags possible concerns for human review.

representation-map.ts

Maps characters and their representation.

bash
deno run --allow-read scripts/representation-map.ts characters.json

Reports:

  • Character identity distribution
  • Agency/centrality analysis
  • Trope risk assessment
  • Diversity within identity groups

Integration with Other Skills

SkillIntegration Point
story-senseSensitivity concerns affect story coherence
character-arcMarginalized characters need full arcs too
dialogueVoice distinctiveness includes authentic speech patterns
worldbuildingWorlds reflect real power dynamics; examine them
genre-conventionsSome genre conventions are problematic tropes
When to Hand Off
  • To character-arc: When representation issues stem from underdeveloped character
  • To worldbuilding: When issues are systemic to the world's construction
  • To dialogue: When voice authenticity is the core concern

Example Interactions

Example 1: White Savior Pattern

Writer: "My protagonist travels to Africa and helps a village build a well."

Your approach:

  1. Identify concern: S5 (Agency Imbalance) + potential S1 (Cultural Appropriation)
  2. Ask: "Who has agency in this story? Who drives the solution?"
  3. Flag: White savior pattern—outsider solving problems for passive community
  4. Suggest: Center village members as protagonists; outsider as supporter at most
  5. Alternative: Story about the village's own efforts, with or without outside support
Example 2: Mental Illness Villain

Writer: "My villain has schizophrenia, which explains their violence."

Your approach:

  1. Identify concern: S3 (Mental Health) + S6 (Harmful Trope: Mentally Ill = Violent)
  2. Explain: This trope increases stigma; people with schizophrenia are more likely to be victims than perpetrators
  3. Flag: Using mental illness to explain villainy perpetuates harmful stereotypes
  4. Suggest: Separate the mental illness from the villainy, or don't diagnose the character
Example 3: Diverse Cast Concern

Writer: "I'm worried I don't have enough diversity in my cast."

Your approach:

  1. Reframe: Quality matters more than quantity
  2. Ask: "What identities are present? How are they characterized?"
  3. Check: S4 (Stereotyping) and S5 (Agency) for existing characters
  4. Advise: Better to write fewer marginalized characters well than many as tokens
  5. Note: Absence of diversity in appropriate settings is also worth examining

Output Persistence

This skill writes primary output to files so work persists across sessions.

Output Discovery

Before doing any other work:

  1. Check for context/output-config.md in the project
  2. If found, look for this skill's entry
  3. If not found or no entry for this skill, ask the user first:
    • "Where should I save output from this sensitivity-check session?"
    • Suggest: explorations/sensitivity/ or a sensible location for this project
  4. Store the user's preference:
    • In context/output-config.md if context network exists
    • In .sensitivity-check-output.md at project root otherwise
Primary Output

For this skill, persist:

  • Representation inventory - identities present and how characterized
  • Concern flags - specific issues identified with reasoning
  • Recommendations - suggested alternatives or improvements
  • Research notes - sources and context for concerns raised
Conversation vs. File
Goes to FileStays in Conversation
Representation analysisClarifying questions
Flagged concerns with reasoningDiscussion of intent
RecommendationsWriter's decisions
Context and sourcesReal-time feedback
File Naming

Pattern: {story}-sensitivity-{date}.md Example: novel-sensitivity-2025-01-15.md

What You Do NOT Do

  • You do not prohibit writers from writing any identity
  • You do not demand specific representation quotas
  • You do not claim final authority on what's acceptable
  • You do not replace actual sensitivity readers
  • You do not censor difficult or challenging content
  • You do not assume harm where context makes intent clear

Your role is evaluative and informative: flag concerns, explain reasoning, suggest alternatives, and respect that the author makes final decisions. The goal is awareness and intentionality, not restriction.


Key Insight

Representation is not about avoiding all potential criticism—that's impossible. It's about writing with awareness of impact, doing the work to understand communities you're depicting, and making intentional choices.

The question is never "can I write this?" It's "am I writing this well, with awareness of how it might land?"

Writers who engage with sensitivity concerns produce better, more authentic work. The goal is representation that enriches rather than harms—that gives readers mirrors and windows rather than funhouse distortions.

© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in skills/creative/fiction/application/sensitivity-check of jwynia/agent-skills.

  • SKILL.md
  • scripts/representation-map.ts
  • scripts/sensitivity-audit.ts

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

Sensitivity Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sensitivity Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sensitivity Check this skilljwynia/agent-skills169—~4.9kAutomated safety check: PassMIT
Socialcoreyhaines31/marketingskills54k4 repos~4.5kAutomated safety check: PassMIT
HumanizerAzure-Samples/interview-coach-agent-framework17237 repos~5.8kAutomated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
JavaScript Concept Fact Checkerleonardomso/33-js-concepts67k1 repos~5kAutomated safety check: PassMIT
User-Facing Text Cleanupguillaumemeyer/watermarks-remover24k—~3.5kAutomated safety check: PassMIT

Similar skills

  • Social

    coreyhaines31/marketingskills

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.

    54k GitHub starsUsed in 4 repos~4.5k tokens
    Writing & ContentAuto-check passed
  • Humanizer

    Azure-Samples/interview-coach-agent-framework

    Official

    Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.

    172 GitHub starsUsed in 37 repos~5.8k tokens
    Writing & ContentAuto-check passed
  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed
  • JavaScript Concept Fact Checker

    leonardomso/33-js-concepts

    Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.

    67k GitHub starsUsed in 1 repo~5k tokens
    Writing & ContentAuto-check passed
  • User-Facing Text Cleanup

    guillaumemeyer/watermarks-remover

    Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.

    24k GitHub stars~3.5k tokensUpdated today
    Writing & ContentAuto-check passed
  • Install Anti Slop

    trycompai/crm

    Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.

    11k GitHub starsUsed in 1 repo~881 tokens
    Writing & ContentAuto-check passed

More from jwynia/agent-skills

All 111 skills in this repo
  • Devcontainer

    jwynia/agent-skills

    Diagnose devcontainer configuration problems and guide development environment setup.

    169 GitHub stars~1.2k tokensUpdated 7 mo ago
    Auto-check: notes
  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    169 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed
  • Gitea Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows for Gitea repositories using the tea CLI.

    169 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Godot Asset Generator

    jwynia/agent-skills

    Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.

    169 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Mastra Hono

    jwynia/agent-skills

    Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.

    169 GitHub stars~2.9k tokensUpdated 7 mo ago
    Auto-check passed
  • PPTX Generator

    jwynia/agent-skills

    Create and manipulate PowerPoint PPTX files programmatically.

    169 GitHub stars~3.1k tokensUpdated 7 mo ago
    Auto-check passed

Questions about Sensitivity Check

What does Sensitivity Check do?

Evaluate representation and flag potential harm concerns. An agent skill from jwynia/agent-skills. Sensitivity Check is an agent skill from jwynia/agent-skills. Evaluate representation and flag potential harm concerns.

When should I use Sensitivity Check?

Sensitivity Check fits situations like: writing characters from marginalized groups; depicting sensitive subject matter; wanting to check for stereotypes and harmful tropes.

How do I install Sensitivity Check in Claude Code?

Run `npx skills add jwynia/agent-skills --skill sensitivity-check -a claude-code`. Or copy the skill folder (skills/creative/fiction/application/sensitivity-check in jwynia/agent-skills) into .claude/skills/sensitivity-check in your project. Claude Code loads it when a task matches its description.

How do I install Sensitivity Check in Codex?

Run `npx skills add jwynia/agent-skills --skill sensitivity-check -a codex`. Or copy the skill folder (skills/creative/fiction/application/sensitivity-check in jwynia/agent-skills) into .agents/skills/sensitivity-check in your project. Codex loads it when a task matches its description.

Can I use Sensitivity Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill sensitivity-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sensitivity-check, .gemini/skills/sensitivity-check, .github/skills/sensitivity-check and .opencode/skills/sensitivity-check in your project.

What does Sensitivity Check need to run?

Going by SKILL.md and its folder, Sensitivity Check needs TypeScript for the scripts in its folder and the command-line tools its instructions call (deno). Our summary lists: Node.js.

Does Sensitivity Check access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sensitivity Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Sensitivity Check use?

Sensitivity Check is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sensitivity Check use?

About 4.9k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sensitivity Check?

Skills that share tags, products or a category with Sensitivity Check: Social (coreyhaines31/marketingskills, 54k stars), Humanizer (Azure-Samples/interview-coach-agent-framework, 172 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars) and JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sensitivity Check?

jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 169 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.

Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.