← ClaudeAtlas

boost-installlisted

Use this skill when the user wants to install Laravel Boost (laravel/boost) in a Laravel project — the MCP server that gives AI agents direct Laravel tooling like database-schema, tinker, list-routes, and search-docs. Triggers on "/boost-install", "install laravel boost", "set up boost mcp", "add the laravel mcp server", "give claude database access for this project". Walks through composer install + php artisan boost:install + verifies MCP registration, with user permission at each step.
PDX-Apps/bench · ★ 0 · AI & Automation · score 72
Install: claude install-skill PDX-Apps/bench
# /boost-install Installs Laravel Boost in a Laravel project and verifies its MCP server is registered with Claude Code. Asks user permission before each step that modifies the project, package list, or settings. ## Usage ``` /boost-install # interactive, default behavior /boost-install --laravel-root=PATH # explicit Laravel root (monorepos) /boost-install --no-mcp # composer require + boost:install only, # skip the post-install MCP verification /boost-install --no-claude-md # don't append a Boost section to CLAUDE.md ``` ## What this skill does 1. **Resolve the Laravel root**. Try in order: - `--laravel-root=PATH` if provided - Project root (if `composer.json` is there) - Read CLAUDE.md for a documented Laravel path (e.g., `apps/api/`) - Ask the user if ambiguous 2. **Check the current state** (read-only, no permission needed): - Is `laravel/boost` already in `composer.json`? - Is `boost.php` config / `.mcp.json` MCP entry already present? - If everything's already set up, report and exit early. 3. **Delegate to `boost-installer` agent** with the resolved context. The agent walks through each install step, asking permission via natural-language prompts before running anything that modifies the project. 4. **Report back** what was installed, what was skipped, and what the user should do next (typically: restart Claude Code so the MCP server con