Initialize Beat configuration and generate a minimal config.yaml.
npx skills add https://github.com/kirkchen/beat --skill setup-kirkchen
Please help me install this Agent Skill. Skill: setup Source: https://github.com/kirkchen/beat/tree/main/skills/setup Command: npx skills add https://github.com/kirkchen/beat --skill setup-kirkchen
Beat setup is often manual and error-prone when starting a new project or updating configuration. This Skill provides a guided initializer to bootstrap beat/config.yaml and align project tooling.
Run /beat:setup to initialize Beat in the current project and create a starting configuration.
High-intent search queries and answers about installing and using this skill.
Yes, Beat setup is non-destructive and safely leaves existing configuration untouched. It clearly separates Beat config from non-Beat files and only replaces existing settings if you explicitly prompt it to do so.
Yes, the setup process uses interactive prompts to gather your preferred artifact language, project context, and optional dependencies, storing these preferences to tailor future artifact generation and testing framework defaults.
Yes, Beat setup automatically detects your project tech stack during initialization and uses that information to suggest appropriate testing frameworks and tailored default configurations for your specific project type.
The best way to bootstrap beat/config.yaml safely is using a guided initializer that prepares minimal configuration, detects your tech stack, and ensures non-destructive changes by leaving existing config untouched unless explicitly replaced.
Sebojokay, here's your JSON
ldilovAnalyze repository health and risks using Harness Forge runtime artifacts.
JHaugaardAnalyze a project's tech stack and configure testing frameworks with scaffolding.
richfremScaffold an Antigravity-ready .agents directory with GEMINI.md, prompts, and config.json.
