developer-setup

Automate developer workspace setup and GitHub automation missions.

1|Updated May 11, 2026
One-click install
npx skills add https://github.com/zeropoint-foundation/ironclaw --skill developer-setup-zeropoint-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer-setup
Source: https://github.com/zeropoint-foundation/ironclaw/tree/main/skills/developer-setup
Command: npx skills add https://github.com/zeropoint-foundation/ironclaw --skill developer-setup-zeropoint-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

One-time onboarding for the developer workflow that sets up the commitments workspace, registers per-repo projects, installs GitHub automation missions, and writes calibration memories. After completion, this skill is excluded from selection until the marker file is removed.

Core Features & Use Cases

  • Automates the full onboarding flow: workspace creation, mission installation, and project declarations.
  • Bootstraps per-repo workflows and calibration memories to accelerate onboarding and standardize practices.
  • Creates a completion marker to prevent re-running the setup.

Quick Start

Run the developer-setup to initialize your workspace and install all developer automation missions.

Frequently Asked Questions about developer-setup

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

FAQPage Schema
How do I automate developer workflow onboarding for a new GitHub repository?

Automating developer workflow onboarding requires running a setup process that configures the commitments workspace, registers repository projects, and installs GitHub automation missions. This bootstraps per-repo workflows and calibration memories to standardize practices with minimal manual configuration.

What is a calibration memory in developer workflow setup?

A calibration memory in developer workflow setup is a bootstrap record written during onboarding to accelerate team alignment. It standardizes per-repo workflows by persisting configuration details for future automated GitHub missions and project declarations.

Do I need a root SKILL.md structure before setting up GitHub automation missions?

Yes, configuring GitHub automation missions requires the root SKILL.md structure to be present in the workspace. This foundational file ensures the onboarding process can correctly register per-repo projects and write calibration memories before bootstrapping workflows.

Can I use developer setup automation for a small team or is it only for individual developers?

Developer setup automation applies to both individual developers and small teams looking to bootstrap repository registrations. It scales to configure shared commitments workspaces and install standardized GitHub automation missions across multiple per-repo projects efficiently.

Why does my developer workflow setup not run again after the first successful onboarding?

Developer workflow setup does not run again because it creates a completion marker file after onboarding finishes. This marker excludes the setup skill from future selection to prevent re-running workspace creation and mission installation unnecessarily.

What is the best way to re-run workspace onboarding after updating GitHub automation missions?

The best way to re-run workspace onboarding after updating GitHub automation missions is to remove the completion marker file. Deleting this marker re-enables the setup skill selection, allowing you to re-execute workspace creation and calibration memory generation.