skills/intercultural-discourse/SKILL.md
Cross-cultural communication frameworks for understanding discourse patterns across cultures
npx skillsauth add curiositech/windags-skills intercultural-discourseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When analyzing cross-cultural discourse, choose your approach:
Single Framework Analysis:
├─ If: Simple, low-stakes interaction with power symmetry
├─ If: Time-constrained preliminary analysis needed
└─ Use: Standard conversation analysis coding only
Layered Framework Analysis:
├─ If: Power asymmetry present (teacher/student, expert/novice)
├─ If: Cultural backgrounds differ significantly
├─ If: Previous single-framework analysis felt incomplete
└─ Use: Sequential application of 2-3 frameworks, preserve contradictions
Emergent Cultural Analysis:
├─ If: Patterns seem culturally specific but unclear which concepts apply
├─ If: Standard coding produces suspiciously clean results
└─ Use: Data-driven cultural pattern identification first, then framework application
Foregrounded Cultural Analysis:
├─ If: Specific cultural concept suspected (e.g., face-saving, hierarchy respect)
├─ If: Behavior looks like "failure" but participants seem comfortable
└─ Use: Apply cultural lens first, then check against other frameworks
Observed smooth interaction →
├─ Low power distance context?
│ ├─ Yes → Likely genuine comprehension
│ └─ No → Test for hidden breakdown
└─ High power distance context?
├─ Check for minimal responses, quick agreements
├─ Look for topic avoidance patterns
└─ If present → Assume hidden breakdown until proven otherwise
Have existing relevant data? →
├─ Collected for different question?
│ ├─ Contextual notes preserved? → Revisit data
│ └─ Only transcripts remain? → Consider recollection
├─ Same question, different framework needed?
│ └─ Always revisit with new framework
└─ No existing data? → New collection required
Detection Rule: If failure/repair rates < 5% in cross-cultural or hierarchical interaction Symptoms: Clean transcripts, high agreement rates, minimal back-and-forth Diagnosis: Mistaking compliance for comprehension; hidden breakdown present Fix: Apply face-sensitive breakdown detection; look for acceptance without elaboration
Detection Rule: If only one analytical framework applied and results feel definitive Symptoms: Overly clean patterns, no analytical contradictions, quick conclusions Diagnosis: Surface-level coding masquerading as complete analysis Fix: Apply second framework; document tensions between interpretations
Detection Rule: If silence/minimal response coded as disengagement or failure Symptoms: Pathologizing culturally appropriate communication styles Diagnosis: Applying Western discourse norms as universal standards Fix: Research participant cultural background; reframe "problems" as competent strategies
Detection Rule: If interviewee responses are short, "correct," but lack elaboration Symptoms: Participant optimizing for accuracy rather than disclosure Diagnosis: Primary knower inversion not established; participant thinks they're being tested Fix: Reframe elicitation to position participant as expert; signal data-gathering not evaluation
Detection Rule: If multiple frameworks forced into single "master interpretation" Symptoms: Analytical contradictions glossed over or ignored Diagnosis: Treating frameworks as redundant routes to same truth Fix: Document contradictions as findings; preserve multiple valid interpretations
Initial Single-Framework Analysis:
Red Flag Recognition:
Layered Reanalysis Process:
Layer 1 - Power Dynamics Check:
Layer 2 - Cultural Framework (Sam Ruam - Thai Composure):
Layer 3 - Hidden Breakdown Detection:
Final Multi-Lens Interpretation:
Scenario: Doctor-patient interaction, patient from hierarchical culture
Decision Path Applied:
Step 1 - Surface Analysis:
Step 2 - Hidden Breakdown Check:
Step 3 - Cultural Reframe:
Outcome: Revealed systematic comprehension gaps hidden by culturally appropriate response patterns
Analysis complete when ALL conditions met:
This skill is NOT for:
active-listening or cultural-sensitivity for live interactionconversation-analysis for basic discourse patternscrisis-communication for urgent clarity needsquick-cultural-scan for fast cultural context checkstherapeutic-communication for healing-focused dialogueformal-discourse-analysis for institutional talkinterview-methodology for commercial contextsDelegate when:
Complexity threshold: If interaction involves fewer than 3 of these factors, use simpler tools:
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.