init-project

Configure API keys and generate .mcp.json from a template.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Ariz0na45/business-os-lite --skill init-project-ariz0na45
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-project
Source: https://github.com/Ariz0na45/business-os-lite/tree/main/.claude/skills/init-project
Command: npx skills add https://github.com/Ariz0na45/business-os-lite --skill init-project-ariz0na45

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap the project by configuring API keys and generating the .mcp.json configuration from a template.

Core Features & Use Cases

  • Collect API keys from the user and validate required fields
  • Generate .mcp.json by replacing placeholders in the template
  • Validate prerequisites (bun) and ensure template presence

Quick Start

Bootstrap the project by collecting API keys and generating the .mcp.json from the template.

Frequently Asked Questions about init-project

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

FAQPage Schema
How do I bootstrap a new project with API keys and MCP config?

To set up environment variables and MCP config, this Skill reads your .env.example, collects missing API keys interactively, and writes the final .env and .mcp.json files. It validates prerequisites like bun before applying the template configuration.

How do I generate a .mcp.json file from a template automatically?

Generating a .mcp.json file is handled by replacing placeholders in your template with collected API keys. The Skill ensures the template exists and produces a completed configuration file for multiple services.

Do I need bun installed to configure environment variables and MCP readiness?

Yes, bun is a required prerequisite to configure environment variables and MCP readiness. The automation validates that bun is installed before proceeding with API key collection and configuration file generation.

What is the best way to automate initial project setup across multiple services?

Automating initial project setup across multiple services is best handled by a template-driven bootstrap process. This approach validates prerequisites, collects missing API keys, and writes both environment and MCP configuration files.

Why does project bootstrap require a .env.example file?

Project bootstrap requires a .env.example file because it serves as the template for validating required fields and collecting missing API key values. The resulting keys are then written to the final .env file.