setup-repo

Orchestrate repository onboarding phases for new developer machines.

125|42|Updated May 19, 2025
One-click install
npx skills add https://github.com/SocketDev/socket-mcp --skill setup-repo-socketdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-repo
Source: https://github.com/SocketDev/socket-mcp/tree/main/.claude/skills/fleet/setup-repo
Command: npx skills add https://github.com/SocketDev/socket-mcp --skill setup-repo-socketdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This onboarding wizard eliminates the manual, error-prone process of configuring a new developer machine and cloning a repository by orchestrating all setup tasks in a single flow.

Core Features & Use Cases

  • Orchestrates multiple setup phases (API token, OS keychain, shell rc bridge, native host, trusted publisher extension, security tools, and repo initialization) in a defined sequence.
  • Skips completed phases automatically and provides a clear summary at the end.
  • Supports per-phase execution and idempotent operations for safe re-runs.

Quick Start

Run the setup wizard to initialize a new developer machine by invoking /setup-repo after cloning the fleet repository.

Frequently Asked Questions about setup-repo

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

FAQPage Schema
How do I automate developer machine onboarding for a new repository clone?

Automated developer machine onboarding orchestrates all setup phases—API tokens, OS keychain integration, shell rc bridges, and security tools—in a single sequential flow. It eliminates manual configuration errors when preparing a fresh clone.

What is the best way to configure shell rc bridges and native messaging hosts during repo initialization?

Configuring shell rc bridges and native messaging hosts during repo initialization is handled automatically in sequence alongside other setup phases. The orchestration ensures each wiring step runs in order and skips if already completed.

Can I re-run repo setup safely if some onboarding phases were already completed?

Repo setup supports idempotent operations for safe re-runs. It automatically detects and skips already completed phases like API token setup or security tools installation, then reports a final summary of the current state.

Does repo onboarding automation handle OS keychain integration and trusted publisher extensions?

Repo onboarding automation explicitly handles OS keychain integration and trusted publisher extension loading. These phases are coordinated natively within the single orchestration flow alongside native messaging host installation.

What steps are required to initialize security tools on a fresh developer machine?

Initializing security tools on a fresh developer machine requires running the setup wizard after cloning the repository. The wizard coordinates installation sequentially with other phases, ensuring all security dependencies are configured correctly.

Why does repo initialization fail when running setup phases out of order?

Repo initialization requires strict phase sequencing because later steps like repo initialization depend on prior phases such as API token setup and shell rc bridge wiring. The orchestration enforces this order to prevent configuration failures.