mixseek-workspace-init

Create MixSeek workspace directories with configs, logs, and templates.

1|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/drillan/mixseek-plus --skill mixseek-workspace-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mixseek-workspace-init
Source: https://github.com/drillan/mixseek-plus/tree/main/.claude/skills/mixseek-workspace-init
Command: npx skills add https://github.com/drillan/mixseek-plus --skill mixseek-workspace-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill removes the manual setup work required to start a MixSeek project by creating the standard workspace folders, keeping configuration files organized, and guiding the user through the initial path and environment variable setup.

Core Features & Use Cases

  • Workspace Bootstrap: Creates the expected configs, logs, and templates directories for a new or existing MixSeek workspace.
  • Non-Destructive Setup: Preserves existing files and skips folders that already exist, making it safe to run on a live project directory.
  • Preset Installation: Copies default ClaudeCode preset files into the workspace so team settings can start from a working baseline.
  • Use Case: A developer starting a new MixSeek project can initialize the workspace, then immediately begin creating team, evaluator, and judgment configuration files in the right locations.

Quick Start

Ask me to initialize a MixSeek workspace in your chosen directory, and I will create the standard folder structure and copy the default presets without overwriting existing files.

Frequently Asked Questions about mixseek-workspace-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a MixSeek workspace directory structure for a new project?

Setting up a MixSeek workspace directory structure involves creating standard folders for configs, logs, and templates. This process uses a non-destructive Bash script to resolve the workspace path, create directories, and copy default ClaudeCode presets without overwriting existing files.

What is the best way to initialize project configuration files without overwriting existing setup?

To initialize project configuration files safely, use a non-destructive workspace setup script. It checks permissions and skips folders that already exist, preserving your current files while copying default presets into the newly created workspace directories.

Can I run a workspace bootstrap script on an existing MixSeek project directory?

Yes, you can run a workspace bootstrap script on an existing MixSeek project directory. The non-destructive Bash setup preserves existing files and only creates missing folders, making it safe to execute on live project paths.

What directory permissions are required to initialize a workspace using a Bash script?

Initializing a workspace using a Bash script requires write and execute permissions on the target directory. The script checks these permissions before resolving the workspace path and creating the required configs, logs, and templates folders.

How does preset installation work when bootstrapping a MixSeek workspace?

Preset installation during workspace bootstrapping copies default ClaudeCode preset files into the newly created directory structure. This provides a working baseline for team settings so you can immediately begin creating team, evaluator, and judgment configuration files.

Why should I use a standardized initialization script instead of manually creating project folders?

Using a standardized initialization script ensures your MixSeek workspace has the correct directory structure and baseline presets from the start. It removes manual setup work, keeps configuration files organized, and safely handles path and environment variable resolution.