npx claudepluginhub richfrem/agent-plugins-skills --plugin agent-scaffoldersThis skill is limited to using the following tools:
acceptance-criteria.mdevals/evals.jsonevals/results.tsvfallback-tree.mdreferences/acceptance-criteria.mdreferences/authentication.mdreferences/examples/http-server.jsonreferences/examples/sse-server.jsonreferences/examples/stdio-server.jsonreferences/fallback-tree.mdreferences/hitl-interaction-design.mdreferences/pattern-decision-matrix.mdreferences/patterns/action-forcing-output-with-deadline-attribution.mdreferences/patterns/adversarial-objectivity-constraint.mdreferences/patterns/anti-pattern-vaccination.mdreferences/patterns/anti-symptom-triage.mdreferences/patterns/artifact-embedded-execution-audit-trail.mdreferences/patterns/artifact-generation-xss-compliance-gate.mdreferences/patterns/artifact-lifecycle.mdreferences/patterns/artifact-state-interrogative-routing.mdExecutes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Follow the create-mcp-integration skill workflow to scaffold a new MCP server
integration for a Claude Code plugin.
$ARGUMENTS — optional MCP server name or service description (e.g. postgres,
github, slack). Omit to start with discovery.$ARGUMENTS names a server or service, use it to seed Phase 1 discovery.mcp.json entry and any supporting config.mcp.json server entry with full configuration (command/url, env vars, allowed tools)
and instructions for obtaining credentials and verifying the connection with /mcp.
$ARGUMENTS is empty: begin with server type selectionstreamable-http transport for new hosted integrations over SSE