skill-terraformer

Detect project tech stacks from package.json and install missing skills from skills.sh.

Updated Apr 11, 2025
One-click install
npx skills add https://github.com/pabloimrik17/monolab --skill skill-terraformer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-terraformer
Source: https://github.com/pabloimrik17/monolab/tree/main/claude-plugins/experiments/skills/skill-terraformer
Command: npx skills add https://github.com/pabloimrik17/monolab --skill skill-terraformer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly assess a project's technology stack at session start by inspecting root project files and signals, then automates installing required skills from a centralized skills.sh repository.

Core Features & Use Cases

  • Detects frontend and backend stacks by examining package.json, project structure, and manifest details.
  • Maps detected signals to applicable skills and orchestrates their installation from skills.sh.
  • Ensures postinstall persistence to maintain skills across fresh installs.

Quick Start

Ask it to detect your project's stack and install any missing skills from skills.sh.

Frequently Asked Questions about skill-terraformer

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

FAQPage Schema
How do I automatically detect a project's tech stack and install missing skills?

To automatically detect a project's tech stack and install missing skills, you need a tool that reads root package.json signals to classify frontend and backend stacks, then orchestrates installation commands from skills.sh. This ensures postinstall persistence across fresh environments.

How does package.json stack detection work for TypeScript frontend projects?

Package.json stack detection works by reading root project files and manifest details to identify TypeScript frontend signals. These signals are mapped to curated skill manifests, enabling automatic installation of applicable missing skills from the central repository.

Can I use automated skill installation with multi-stack project structures?

Yes, automated skill installation applies to frontend and multi-stack project structures. The detection mechanism examines root package.json and related project signals to identify applicable skills across different stacks within the same project environment.

What is the best way to ensure postinstall persistence for project automation skills?

The best way to ensure postinstall persistence for project automation skills is to orchestrate installation commands through a tool that maps detected stack signals to skills.sh and configures persistence during the postinstall phase automatically.

Why does my CLI detect-stack process fail to identify applicable skills?

A CLI detect-stack process fails to identify applicable skills when root package.json files lack recognizable manifest signals or the project structure does not match the curated skill mappings required for orchestration.