detect-stack

Identifies technology stacks by scanning manifests and source files, then installs matching Maestro skills and IDE configurations.

3|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/KeyValueSoftwareSystems/maestro --skill detect-stack-keyvaluesoftwaresystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-stack
Source: https://github.com/KeyValueSoftwareSystems/maestro/tree/main/skills/core/bootstrap/detect-stack
Command: npx skills add https://github.com/KeyValueSoftwareSystems/maestro --skill detect-stack-keyvaluesoftwaresystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort of configuring development environments by automatically identifying the technology stack of a repository and installing the necessary Maestro skills and agents.

Core Features & Use Cases

  • Automated Discovery: Scans project manifests and source files to identify languages and frameworks like Go, Python, React, or Rust.
  • Targeted Installation: Installs only the relevant stack-specific skills, keeping the workspace clean and focused.
  • Use Case: When onboarding a new developer to a multi-repo project, run this skill to instantly bootstrap the environment with the correct tooling for the specific backend and frontend frameworks in use.

Quick Start

Run the detect-stack skill to scan the current directory and install all matching technology-specific tools.

Frequently Asked Questions about detect-stack

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

FAQPage Schema
How do I automatically detect a project's technology stack from manifest files?

Stack detection works by scanning repository manifest files and source code patterns to identify frameworks like Go, Python, React, or Rust, then mapping those project signals to predefined stack tokens for automated environment bootstrapping.

Can I automatically install development tools based on detected codebase dependencies?

Yes, you can automate tool installation by mapping detected project dependencies to environment-specific Maestro skills and IDE configurations, ensuring consistent developer tooling without manual setup.

What is the best way to bootstrap a development environment for a multi-repo project?

Bootstrapping a multi-repo development environment is best achieved by running automated stack detection to scan the current directory and install only the matching technology-specific skills, keeping the workspace clean and focused.

Does stack detection work with both backend and frontend frameworks?

Yes, stack detection identifies both backend and frontend frameworks by scanning source files and manifests, allowing you to instantly configure the correct tooling for specific frameworks in use across a repository.

Why do I need to map project signals to predefined stack tokens?

Mapping project signals to predefined stack tokens is required to accurately match detected dependencies with environment-specific skills, ensuring the automated installation targets only the relevant technology-specific tools.

What are the limitations of automating IDE configuration through stack detection?

Automating IDE configuration through stack detection is limited to recognized manifest files and source code patterns; unidentified frameworks or custom dependencies lacking predefined stack tokens will not trigger automated installation.