cultural-review
This skill provides comprehensive guidance for reviewing code, features, and content for cultural sensitivity and Indigenous data sovereignty compliance.
What this skill does
# Cultural Review Skill
This skill provides comprehensive guidance for reviewing code, features, and content for cultural sensitivity and Indigenous data sovereignty compliance.
## OCAP Framework Reference
### Ownership
**Requirement**: Storytellers maintain ownership of their narratives
**Check for**:
- [ ] Story ownership tracked via `author_id` and `storyteller_id`
- [ ] Both author and storyteller have control rights
- [ ] Ownership cannot be transferred without consent
- [ ] Community collective ownership respected
### Control
**Requirement**: Users decide who accesses their stories
**Check for**:
- [ ] Privacy levels properly enforced (public/community/org/private)
- [ ] Users can revoke access at any time
- [ ] Distribution requires explicit consent
- [ ] Bulk revocation available ("Pull All")
### Access
**Requirement**: Tiered access based on cultural sensitivity
**Check for**:
- [ ] Sensitivity levels correctly implemented
- [ ] Elder approval workflow for high/sacred content
- [ ] Community membership verification where required
- [ ] Access audit trail maintained
### Possession
**Requirement**: Data can be exported or deleted anytime
**Check for**:
- [ ] Data export functionality (GDPR Article 20)
- [ ] Full deletion/anonymization (GDPR Article 17)
- [ ] No data lock-in or artificial barriers
- [ ] Portable data format (JSON)
## Sensitivity Level Guidelines
### Standard
- General stories, no restrictions
- Can be embedded externally
- Public sharing allowed
### Medium
- Some cultural context important
- May require community membership
- External sharing needs approval
### High
- Significant cultural value
- Elder review before sharing
- Limited distribution options
- No unauthorized embedding
### Sacred/Restricted
- Protected traditional knowledge
- Elder approval mandatory
- NO external distribution ever
- May have viewing time/place restrictions
## Code Review Checklist
### API Endpoints
```
□ Authentication required (unless public embed)
□ Authorization checks ownership/permissions
□ Sensitivity level verified before action
□ Elder approval status checked for high/sacred
□ Audit log created for significant actions
□ Consent verified before distribution
□ Revocation cascades properly
```
### UI Components
```
□ Cultural indicators are respectful
□ Sensitivity badges are clear
□ Elder approval status prominent
□ Consent status visible
□ Privacy level clearly shown
□ Revocation controls accessible
□ Trauma-informed animations (gentle)
□ Language is inclusive
```
### Database Operations
```
□ Tenant isolation maintained
□ Ownership fields populated
□ Consent fields checked
□ Audit trail created
□ Soft delete preferred over hard delete
□ Anonymization preserves audit trail
```
## Red Flags
### Immediate Action Required
- External distribution of sacred content
- Missing consent verification
- Broken revocation cascade
- Elder approval bypassed
- Tenant isolation breached
### Needs Improvement
- Missing audit logging
- Hard delete without anonymization
- Unclear sensitivity indicators
- Missing ownership checks
- No bulk revocation option
## Approval Workflow
### Standard Content
1. Author creates story
2. Consent captured
3. Ready for distribution
### Medium Sensitivity
1. Author creates story
2. Cultural context added
3. Consent captured
4. Community review (optional)
5. Ready for limited distribution
### High Sensitivity
1. Author creates story
2. Cultural context added
3. Consent captured
4. Elder review requested
5. Elder approves/requests changes
6. Limited distribution (no embedding)
### Sacred Content
1. Author creates story
2. Cultural context added
3. Consent captured
4. Elder review mandatory
5. Elder approval required
6. Platform-only access
7. Never distributed externally
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.