gioia-methodology
This skill should be used when users are building or refining their Gioia data structure, mentions 'Gioia', 'data structure', 'themes', 'concepts', 'dimensions', '1st-order', '2nd-order', 'aggregate', or needs to validate/export their analytical hierarchy for publication.
What this skill does
# gioia-methodology
Gioia method data structure building and validation. Helps researchers construct the three-level hierarchy (1st-order concepts, 2nd-order themes, aggregate dimensions) with validation and export capabilities.
## When to Use
Use this skill when:
- User is building or refining their data structure
- User mentions "Gioia", "data structure", "themes", "concepts", "dimensions"
- User needs to validate their analytical hierarchy
- User wants to export their framework for publication
- User asks about 1st-order vs 2nd-order concepts
## The Three-Level Hierarchy
```
AGGREGATE DIMENSIONS (Level 3 - Most Abstract)
↑ Researcher theorizes
│
SECOND-ORDER THEMES (Level 2 - Intermediate)
↑ Researcher interprets and groups
│
FIRST-ORDER CONCEPTS (Level 1 - Most Concrete)
↑ Grounded in participant language
```
## Key Principles
1. **1st-Order Concepts** stay close to participant language
- Use informant terms when possible
- Example: "I had to do something about it" → NOT "Moral conviction"
2. **2nd-Order Themes** are YOUR interpretive constructions
- Group related 1st-order concepts
- Represent YOUR analytical abstraction
- Example: "Adaptive Routine Building"
3. **Aggregate Dimensions** are theoretical contributions
- Organize themes into overarching constructs
- Connect to literature
- Example: "Managing Chronic Uncertainty"
## Scripts
### validate-structure.js
Validates a Gioia data structure JSON file against the schema.
**Usage:**
```bash
node skills/gioia-methodology/scripts/validate-structure.js \
--structure-path /path/to/data-structure.json
```
**Checks:**
- Required fields present (id, name, definition)
- Three-level hierarchy maintained
- IDs follow naming convention (AD1_T1_C1)
- Example quotes include document_id and lines
**Returns:** JSON with validation status, errors, and suggestions.
### check-hierarchy.js
Analyzes hierarchy quality and methodological consistency.
**Usage:**
```bash
node skills/gioia-methodology/scripts/check-hierarchy.js \
--structure-path /path/to/data-structure.json
```
**Analyzes:**
- Concept distribution across themes (warns if <2 or >10 per theme)
- Theme distribution across dimensions (warns if <2 or >5 per dimension)
- Quote coverage (flags concepts without example quotes)
- Abstraction levels (checks if 1st-order concepts are too abstract)
**Returns:** JSON with hierarchy analysis and recommendations.
### export-structure.js
Exports data structure to publication-ready formats.
**Usage:**
```bash
node skills/gioia-methodology/scripts/export-structure.js \
--structure-path /path/to/data-structure.json \
--format markdown|table|latex
```
**Formats:**
- `markdown` - Formatted markdown for documentation
- `table` - Tab-separated values for Gioia display table
- `latex` - LaTeX tabular format for academic papers
## Templates
This skill bundles:
- `templates/gioia-structure-guide.md` - Human-readable methodology guide
- `templates/gioia-data-structure-template.json` - Starter template with examples
## Typical Counts
| Stage | Dimensions | Themes | Concepts |
|-------|------------|--------|----------|
| Stage 1 | 2-3 (tentative) | 8-12 | 30-50 |
| Stage 2 | 3-5 | 10-15 | 30-80 |
| Stage 3 | 3-5 (parsimonious) | 10-15 | Consolidated |
## Common Questions
### Q: Can concepts appear under multiple themes?
**Depends on your ontology:**
- Interpretivist: Usually assign to most appropriate theme
- Constructivist: May document multiple interpretations
- Use `/qual-examine-assumptions` if unsure
### Q: How do I know if my structure is complete?
**Signs of saturation:**
- New documents add quotes but not new concepts
- Themes feel stable and coherent
- Theoretical story is clear
### Q: When are 1st-order concepts too abstract?
**Test:** Would a participant recognize this language?
- "I had to do something" ✓ (their words)
- "Moral conviction" ✗ (your interpretation - move to 2nd-order)
## Examples
### Healthcare Example
```
Aggregate Dimension: Managing Chronic Uncertainty
├── Theme: Adaptive Routine Building
│ ├── "Selective symptom tracking"
│ ├── "Personalizing medical advice"
│ └── "Flexible routine adjustment"
└── Theme: Navigating Healthcare Systems
├── "Finding doctors who listen"
└── "Working around insurance barriers"
```
### Organizational Example
```
Aggregate Dimension: Navigating Leadership Paradoxes
├── Theme: Balancing Authenticity and Performance
│ ├── "Being yourself while playing the role"
│ ├── "Strategic vulnerability"
│ └── "Authentic but bounded"
└── Theme: Managing Competing Demands
├── "Satisficing across stakeholders"
└── "Prioritizing without alienating"
```
## Integration Points
- **@dialogical-coder** applies the data structure during coding
- **project-dashboard** skill shows concept/theme/dimension counts
- **deep-reasoning** skill helps with hierarchy decisions
## Related
- **Commands:** Structure referenced by all coding commands
- **Agents:** @dialogical-coder uses structure for systematic coding
- **Templates:** Moved from templates/ directory
- **Other Skills:** project-setup creates initial structure file
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.