project-setup skill
scriptsInitializes qualitative research projects by establishing philosophical foundations and creating a structured folder hierarchy.
- GitHub stars
- 21
- Files
- 5
- Last commit
- Nov 6, 2026
- License
- —
- Allowed tools
- —
What does the project-setup skill do?
project-setup initializes qualitative research projects by establishing philosophical foundations and creating a structured folder hierarchy.
Summary generated from the skill's SKILL.md.
About the project-setup skill
Establishing philosophical foundations and organizing research files is what this skill enables for qualitative researchers. It assists users in defining their epistemic stance and ontology through a Socratic dialogue process before building the necessary technical infrastructure. An agent should load this tool when a user wants to start a new study, initialize a project, or configure their research stance.
The skill produces a complete sandwich methodology folder hierarchy, including directories for manual coding, memos, and theoretical integration. It generates a config.json file based on the researcher's dialogue responses and initializes a reflexivity journal. Users can choose between a Full Setup for deep philosophical exploration or a Quick Start that applies default settings like the Gioia/Systematic Interpretivist tradition. The process relies on specific scripts such as create-structure.js and generate-config.js to build the project environment.
What an agent can do with it
- 1Initialize a new research projectStart a new qualitative study by establishing its philosophical foundations and folder structure.
- 2Define epistemic stance via dialogueEngage in a Socratic onboarding process to determine your ontology and relationship with AI.
- 3Rapidly configure research defaultsSet up a project quickly using predefined interpretivist settings.
- 4Verify project readinessCheck if the research project setup is complete and meets required standards.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the project-setup skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the project-setup skill in Plugin
/plugin marketplace add linxule/interpretive-orchestration /plugin install interpretive-orchestration@interpretive-orchestration
Install the project-setup skill in Claude Code
~/.claude/skills/project-setup/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/project-setup ~/.claude/skills/project-setupInstall the project-setup skill in Claude Code (project)
.claude/skills/project-setup/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/project-setup .claude/skills/project-setupInstall the project-setup skill in Codex
~/.agents/skills/project-setup/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/project-setup ~/.agents/skills/project-setupInstall the project-setup skill in Gemini CLI
~/.gemini/skills/project-setup/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/project-setup ~/.gemini/skills/project-setupInstall the project-setup skill in Claude.ai
npx degit linxule/interpretive-orchestration/plugin/skills/project-setup project-setup && zip -r project-setup.zip project-setup # claude.ai → Customize → Skills → + → Create skill → Upload a skill → project-setup.zip
Automated checks
Ran Nov 16, 2026Full report →Not verified yet. A skill needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablelinxule/interpretive-orchestration/plugin/skills/project-setup is public and reachablegithub.com/linxule/interpretive-orchestration/tree/HEAD/plug ↗Pass
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit 2026-11-06github.com/linxule/interpretive-orchestration/commits ↗Pass
- No download-and-run or credential theft in scripts3 scripts read; no download-and-run, remote eval, base64 execution or credential uploadPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/linxule/interpretive-orchestration/blob/HEAD/plug ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/linxule/interpretive-orchestration/blob/HEAD/plug ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 162 linesgithub.com/linxule/interpretive-orchestration/blob/HEAD/plug ↗Pass
SKILL.md
View on GitHubScript paths:
${CLAUDE_PLUGIN_ROOT}below is this plugin's root folder, two levels above this skill's own folder. Claude Code fills it in. If you see it unfilled, still starting with a dollar sign (as in Codex, Copilot CLI or Kimi Code), put that folder's absolute path in its place before you run a command.
project-setup
Initialize qualitative research projects with epistemic partnership at the core. This skill guides researchers through philosophical foundation establishment via Socratic dialogue, then creates the project infrastructure.
When to Use
Use this skill when:
- User wants to start a new qualitative research project
- User mentions "initialize", "setup", "new project", or "getting started"
- User asks about establishing philosophical foundations
- User needs to configure their epistemic stance
Capabilities
- Socratic Onboarding - Guide researchers through 5 key philosophical questions
- Project Structure Creation - Create the sandwich methodology folder hierarchy
- Configuration Generation - Generate config.json from dialogue responses
- Partnership Agreement - Establish mutual commitments
Two Modes
Full Setup (15 min) - Recommended
Complete Socratic dialogue exploring:
- What is "data" to you? (ontology)
- When you code, you are...? (epistemology)
- Your role as researcher? (methodology)
- How do you view AI? (relationship)
- Stage 1 status? (sandwich methodology)
Quick Start (3 min)
Use sensible defaults (Gioia/Systematic Interpretivist):
- Ontology: interpretivist
- Epistemology: systematic_interpretation
- Tradition: gioia_corley
- AI Relationship: epistemic_partner
Quick Start still requires Stage 1 manual coding - no shortcuts to theoretical sensitivity!
Scripts
create-structure.js
Creates the project folder hierarchy:
project-name/
├── .interpretive-orchestration/
│ ├── config.json
│ ├── reflexivity-journal.md
│ ├── conversation-log.jsonl
│ └── decision-history.md
├── stage1-foundation/
│ ├── manual-codes/
│ └── memos/
├── stage2-collaboration/
│ ├── stream-a-theoretical/
│ ├── stream-b-empirical/
│ └── synthesis/
├── stage3-synthesis/
│ ├── evidence-tables/
│ └── theoretical-integration/
└── outputs/
Usage:
node "${CLAUDE_PLUGIN_ROOT}/skills/project-setup/scripts/create-structure.js" --project-path /path/to/project --project-name "My Research"
generate-config.js
Generates config.json from dialogue responses.
Usage:
node "${CLAUDE_PLUGIN_ROOT}/skills/project-setup/scripts/generate-config.js" \
--project-path /path/to/project \
--name "My Research" \
--research-question "How do..." \
--ontology interpretivist \
--epistemology systematic_interpretation \
--tradition gioia_corley \
--ai-relationship epistemic_partner
validate-setup.js
Validates project setup completeness.
Usage:
node "${CLAUDE_PLUGIN_ROOT}/skills/project-setup/scripts/validate-setup.js" --project-path /path/to/project
Returns: JSON with validation status and any missing components.
Dialogue Flow Example
Claude: Welcome to Interpretive Orchestration! Would you prefer:
[A] Full Setup (15 min) - Socratic exploration
[B] Quick Start (3 min) - Use defaults
User: A
Claude: Let's explore your philosophical foundations together.
Question 1: When you read research data, what are you encountering?
A) Objective facts waiting to be discovered
B) Meanings requiring systematic interpretation
C) Co-created realities with participants
D) Help me think about this
User: B
Claude: You've chosen a systematic interpretivist stance - aligning
with Gioia & Corley's approach. This means:
- We'll use language like "construct", "interpret", "build"
- AI helps you organize evidence; YOU construct meaning
- Focus on systematic procedures + theoretical sensitivity
Does "constructing understanding" feel right, or does
"discovering truth" feel more accurate?
[dialogue continues through all 5 questions]
Templates
This skill bundles these templates (moved from templates/ directory):
templates/epistemic-stance.md- Human-readable stance questionnairetemplates/config.schema.json- JSON schema for config validationtemplates/example-config.json- Example configuration file
Defense-in-Depth
While hooks enforce Stage 1 completion deterministically, this skill includes a pre-check:
Before proceeding to Stage 2 features, verify that
config.jsonshowsstage1_complete: trueanddocuments_manually_coded >= 10. If not, guide the researcher through Stage 1 instead of proceeding.
Output
After completion, creates:
- Project folder structure
.interpretive-orchestration/config.jsonwith researcher's stance.interpretive-orchestration/reflexivity-journal.mdinitialized- Welcome message with next steps based on Stage 1 status
Related
- Commands:
/qual-inittriggers this skill - Agents: None directly, but configuration affects all agents
- Hooks:
check-stage1-complete.jsenforces Stage 1 status - Other Skills:
gioia-methodology/for data structure templates
Files in this skill
5project-setup skill questions
How do I install the project-setup skill in Claude Code?
Run npx degit linxule/interpretive-orchestration/plugin/skills/project-setup ~/.claude/skills/project-setup. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the project-setup skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What does the project folder structure look like?
The skill creates a hierarchy including .interpretive-orchestration for configs and logs, stage1-foundation for manual coding, stage2-collaboration, stage3-synthesis, and an outputs folder.
Can I skip manual coding during the Quick Start?
No, even when using the Quick Start mode, manual coding for Stage 1 is still required to maintain theoretical sensitivity.