cultural-appropriation-handwringer
Critical analysis of cultural appropriation discourse. Use when teaching about distinguishing genuine respect issues from performative concern, or examining when cultural criticism becomes counterproductive.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- cultural-appropriation-handwringer
- license
- MIT
- metadata
- { "exposes": "performative-activism", "category": "parody", "educational": true }
- description
- Critical analysis of cultural appropriation discourse. Use when teaching about distinguishing genuine respect issues from performative concern, or examining when cultural criticism becomes counterproductive.
03 SKILL.md 正文
Cultural Appropriation Handwringer
Educational guide to evaluating cultural appropriation claims critically and distinguishing substance from performance.
Overview
This skill teaches critical evaluation of cultural appropriation discourse, distinguishing genuine respect issues from performative outrage, while maintaining focus on what actually helps affected communities.
The Spectrum
Genuine Appropriation (Real Issues)
Exploitation:
- Profiting from culture while members face discrimination
- Example: White musician gets rich from blues while Black artists were barred from venues
- Problem: Economic exploitation + erasure of origins
Sacred Items:
- Religious/ceremonial items as fashion
- Example: Native American war bonnets at music festivals
- Problem: Deep disrespect of sacred traditions
Mockery:
- Stereotyping for entertainment
- Example: Blackface, "Indian" Halloween costumes with stereotypes
- Problem: Dehumanization and historical oppression
These are real issues with real harm.
Performative Handwringing (Often Counterproductive)
Red flags:
- Outsiders more offended than culture members
- Preventing genuine appreciation and learning
- Food/cooking declared off-limits
- Ignoring actual community voices
- Purity tests about who can do what
Examples of excess:
- "You can't cook tacos unless you're Mexican"
- Banning yoga unless you're Indian
- Attacking people for wearing kimonos (when Japanese welcome it)
- Calling appreciation "theft"
Problem: Prevents cultural exchange that communities often WANT
Critical Questions
1. Who is speaking?
- Members of affected culture?
- Or outside "allies" speaking over them?
- Listen to actual community voices
2. Is there exploitation?
- Profiting while culture members are marginalized?
- Giving credit and compensation?
- Power dynamics involved?
3. What's the actual harm?
- Concrete harm (economic, social)?
- Or symbolic/theoretical harm?
- Scale matters for prioritization
4. What would help?
- Does the proposed solution actually benefit the community?
- Or just make complainant feel righteous?
- Focus on outcomes, not performances
Case Studies
Sushi Chef Controversy
Claim: Non-Japanese shouldn't make sushi
Japanese response: "Please make sushi! We want our food shared!"
Lesson: Actual community wanted cultural exchange
Handwringers: Were speaking over Japanese voices
Yoga Debate
Claim: Yoga by non-Indians is appropriation
Indian response: Mixed - many happy to share, some concerned about commercialization
Nuance: Commercial exploitation ≠ personal practice
Lesson: It's complicated, listen to affected voices
Kimono Try-On Event
Claim: Museum kimono event is appropriation
Japanese response: "This is cultural appreciation, we support it"
Protesters: Were majority non-Japanese
Lesson: Outrage culture can override actual cultural voices
The Paradox
Performative anti-appropriation can be:
- More silencing than the "appropriation"
- Speaking over the very voices it claims to protect
- Creating barriers the culture doesn't want
- Reducing everything to oppression framework
Real respect means:
- Actually listening to affected communities
- Not assuming you know better than they do
- Accepting when they say "we want to share this"
- Focusing on material conditions over symbolism
Distinguishing Criticism Types
Criticism Worth Heeding
"This sacred item shouldn't be a Halloween costume"
- Specific, clear harm
- Raised by community members
- Addresses genuine disrespect
- Solution: Don't use sacred items for fashion
Criticism to Question
"No one can cook ethnic food outside their ethnicity"
- Overly broad
- Often from outside the culture
- Prevents learning and appreciation
- Contradicts what many communities want
- Solution: Cook food, give credit, be respectful
The Actual Problems
Real issues in cultural dynamics:
- Economic exploitation
- Erasure of origins
- Ongoing discrimination
- Power imbalances
- Historical injustices
Symbolic issues:
- Who wears what
- Who cooks what
- Who practices what
Focus energy on: Economic and political justice, not symbolism policing
Educational Use
Use this skill to:
- Teach critical evaluation of social claims
- Distinguish substance from performance
- Center actual affected voices
- Understand power dynamics
- Recognize when "activism" becomes counterproductive
The Balance
Real cultural respect involves:
- Listening to affected communities
- Giving credit and compensation
- Avoiding sacred items and mockery
- Recognizing power dynamics
- Also: Allowing cultural exchange and appreciation when communities welcome it
Not helpful:
- Outsiders being offended on others' behalf
- Speaking over actual community voices
- Performative purity tests
- Preventing harmless exchange
Note: This skill promotes genuine respect and listening to affected communities, while critiquing performative activism that speaks over those communities.
04 同仓库更多 Skills
Docs Research
Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).
wrappee-drift
Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API/docs, not training-data memory) and against comparable/competing wrappers. Trigger when the user says "wrappee drift" followed by a repo name, "capability audit" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth/archive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's/competitors' actual current capabilities.
modules
暂无简介
mcp-standards
Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI/CD workflows.
webapp-cua-test
Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR "Connected" wait, sidebar nav walk) for a fleet MCP server repo under D:\Dev\repos. Trigger when the user says "cua webapp test" or "webapp clickthrough" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill / cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).
ship
Final release gate for a fleet MCP server repo under D:\Dev\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says "ship it", "ship" followed by a repo name, "release" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix/nsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.