skills.rest
FRIKKern
FRIKKernCOMMUNITY
Explore all skills by this author →
GitHub

doey-scaffy-mcp

Orchestrate per-team MCP server instances for Scaffy template tooling across workers.

6|2|Updated Mar 15, 2026
Search Tags:#automation#templates#cli#mcp#doey#scaffy
One-click install
npx skills add https://github.com/FRIKKern/doey --skill doey-scaffy-mcp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doey-scaffy-mcp
Source: https://github.com/FRIKKern/doey/tree/main/.claude/skills/doey-scaffy-mcp
Command: npx skills add https://github.com/FRIKKern/doey --skill doey-scaffy-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawn the Doey Scaffy MCP server to enable workers to drive the Scaffy template engine via tool calls. This simplifies managing and validating scaffy templates across a distributed worker pool.

Core Features & Use Cases

  • MCP lifecycle integration: The skill parses the mcp_servers config from the frontmatter and launches per-pane MCP servers for each team.
  • Per-team isolation: Each team gets its own doey-scaffy MCP process to avoid cross-team conflicts and data leakage.
  • Automatic cleanup: Teardown removes MCP processes and runtime config when a team is killed or detached.

Quick Start

Load this skill and start a team to automatically spawn the doey-scaffy MCP server for scaffy template operations.

Frequently Asked Questions about doey-scaffy-mcp

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

FAQPage Schema
How do I run isolated MCP server instances for parallel CLI template tasks?▼

Running isolated MCP server instances for parallel CLI template tasks requires parsing mcp_servers frontmatter config to spawn per-team processes, avoiding cross-team data leakage. This skill automates that lifecycle management across distributed workers in multi-pane environments.

How do I automate teardown for MCP server processes when a worker team stops?▼

Automating teardown for MCP server processes when a worker team stops is handled via automatic cleanup that removes MCP runtime configs and processes upon team detachment or termination, preventing orphaned instances from lingering in the environment.

Does Doey work with Scaffy template tooling for distributed worker pools?▼

Doey works with Scaffy template tooling for distributed worker pools by spawning dedicated MCP servers that enable workers to drive the Scaffy template engine via tool calls, simplifying template management and validation across the pool.

What's the best way to prevent cross-team conflicts when scaffolding templates simultaneously?▼

Preventing cross-team conflicts when scaffolding templates simultaneously is best achieved through per-team isolation, where each team receives its own dedicated MCP process to ensure operations remain independent and data does not leak between teams.

How do I spawn an MCP server from frontmatter configuration for automation tasks?▼

Spawning an MCP server from frontmatter configuration for automation tasks involves parsing the mcp_servers config block to automatically launch per-pane MCP instances, allowing workers to execute scaffy template operations immediately upon team creation.

Related Skills

Explore More Software Engineering Skills→
FRIKKernFRIKKern
6

doey-mcp-example

Declare MCP server dependencies in skill frontmatter for per-team isolation.

Community
Advanced
FRIKKernFRIKKern
6

doey-scaffy-validate

Validate .scaffy templates for syntax and structural integrity.

Community
Intermediate
FRIKKernFRIKKern
6

doey-status

View and report real-time statuses of Doey workers across tmux panes.

Community
Intermediate
Human-Frontier-Labs-IncHuman-Frontier-Labs-Inc

flow-nexus-neural

Train and deploy neural networks across distributed E2B sandboxes.

Official
Advanced