skills.rest
moonzff
moonzffCOMMUNITY
Explore all skills by this author →
GitHub

dual-environment-workflow

Selects runtime, profile, and MCP path for Windows and WSL2 tasks.

1|Updated May 6, 2026
Search Tags:#browser automation#mcp#token optimization#windows#wsl2#workflow routing#runtime selection
One-click install
npx skills add https://github.com/moonzff/Codex_up --skill dual-environment-workflow-moonzff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dual-environment-workflow
Source: https://github.com/moonzff/Codex_up/tree/main/02-project-reference/analyses/skills/dual-environment-workflow
Command: npx skills add https://github.com/moonzff/Codex_up --skill dual-environment-workflow-moonzff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working across Windows and WSL2 often causes mixed-runtime drift, wasted tokens, and inconsistent tooling choices. This Skill provides a decision workflow that picks one primary runtime, the lowest-cost profile, and the right MCP server before work begins. ## Core Features & Use Cases - Runtime Routing: Classifies tasks as Windows-first, WSL2-first, or dual, then commits to one primary runtime to avoid mid-task switching. - Profile Selection: Maps tasks to cost-tiered profiles (lean, quick, deep, review, research, debug, design, automation) to control token usage. - MCP Guidance: Routes structured file IO to filesystem, library docs to context7, and browser automation to playwright or chrome-devtools, preferring plain shell when simpler. - Use Case: Before debugging a failing browser flow, use this Skill to choose WSL2 as the runtime, the debug profile, and chrome-devtools for network inspection. ## Quick Start Use the dual-environment workflow to decide the runtime, profile, and MCP path for this task before starting.

Frequently Asked Questions about dual-environment-workflow

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

FAQPage Schema
How do I decide between Windows and WSL2 for a coding task?▼

Classify the task as Windows-first, WSL2-first, or dual, then commit to one primary runtime. Use WSL2 for MCP, browser automation, package management, and Linux tooling; use Windows for host-only integrations or legacy projects already stable there.

What profile should I use to reduce token usage?▼

Use the lean profile for skimming, diff review, quick lookups, and token-saving triage, or quick for small code and ops tasks. Reserve deep, research, and debug profiles for multi-file or investigative work.

When should I use MCP servers instead of shell commands?▼

Choose MCP only when it materially improves structure or reliability, such as filesystem for structured file operations, context7 for library docs, or playwright for browser automation. Prefer plain shell commands when they are simpler and lower-risk.

Playwright vs chrome-devtools for browser automation?▼

Use playwright as the preferred path for dependable browser automation. Switch to chrome-devtools when you need deeper inspection of page state, network requests, or performance that Playwright cannot provide.

Can I switch between Windows and WSL2 mid-task?▼

Avoid bouncing between runtimes mid-task unless the work clearly has separate host-specific and Linux-specific steps. Pick one primary runtime upfront and state it explicitly before starting.

Related Skills

Explore More Software Engineering Skills→
louzhengshuailouzhengshuai

deepscientist-windows-wsl-setup

Set up DeepScientist on Windows with WSL2 and Codex authentication.

Community
Advanced
argenargen
1

decision-record

Documents decisions with rationale and alternatives for future reference.

Community
Advanced
Luqman-Ud-DinLuqman-Ud-Din

qa-preflight

Verify QA audit environment readiness before browser-driven audits.

Community
Advanced
harperaaharperaa
30

setup-windows

Automate BastionClaw setup on Windows with WSL2 and Docker/Podman.

Community
Advanced