provision

Provision project services, credentials, permissions, and preflight validation workflows.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/mckissinger/keel --skill provision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provision
Source: https://github.com/mckissinger/keel/tree/main/skills/provision
Command: npx skills add https://github.com/mckissinger/keel --skill provision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents autonomous development runs from stalling due to missing credentials, unprepared services, permission prompts, and incomplete environment validation.

Core Features & Use Cases

  • Environment Contract Execution: Sets up project services, CLI authentication, development resources, environment variables, and required permissions from the project's architecture specification.
  • Preflight Validation: Verifies credentials, command allowlists, feedback loops, branch protections, and service readiness before unattended execution begins.
  • Use Case: Prepare a new application workspace for a multi-milestone autonomous build so later implementation runs can proceed without avoidable setup interruptions.

Quick Start

Use the provision skill to configure the project environment from its environment contract and finish with a passing preflight check.

Frequently Asked Questions about provision

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

FAQPage Schema
How do I prepare a project environment for autonomous builds without stalling on missing credentials?

Environment preparation for autonomous builds requires provisioning required services, credentials, permissions, and validation workflows beforehand. You execute environment contracts and run preflight checks to establish a verified unattended execution foundation.

What is an environment contract and when do I need it for unattended execution?

An environment contract is a project architecture specification defining required services, CLI authentication, development resources, and permissions. You need it for kickoff sessions, brownfield adoption, and feature additions introducing new development resources.

How do I run preflight validation checks for autonomous development runs?

Preflight validation verifies credentials, command allowlists, feedback loops, branch protections, and service readiness before unattended execution begins. You run these checks after provisioning services to ensure the environment is fully prepared.

Can I use provisioning for brownfield adoption and existing feature additions?

Yes, provisioning applies to brownfield adoption and later feature additions that introduce new development resources or services. It configures CLI authentication, environment variables, and required permissions from the project's architecture specification.

Why does my autonomous build stall on permission prompts during unattended execution?

Autonomous builds stall when missing credentials, unprepared services, and permission prompts interrupt execution. Provisioning establishes command allowlists and permission policies beforehand to prevent these avoidable setup interruptions.

What's the best way to configure command allowlists and branch protections for autonomous software builds?

The best way is executing an environment contract that defines permission policies and command inventories, followed by a preflight check. This verifies branch protections and command allowlists to establish a verified unattended execution foundation.