birdcc-installerlisted

Install BIRD editor support and the @birdcc/cli (birdcc) command-line toolkit. Trigger phrases: - "how do I install BIRD support in VSCode" - "which BIRD extension should I install" - "install birdcc CLI" - "BIRD2 syntax highlighting for Neovim/Vim" - "BIRD plugin for JetBrains" - "how to get BIRD LSP" Negative triggers — do NOT invoke this skill: - Questions about BIRD config syntax, filters, protocols, or diagnostics (use bird-agent). - Requests to generate or fix CI/CD workflows (use birdcc-cicd). - Runtime BIRD daemon troubleshooting unrelated to tooling setup.
bird-chinese-community/BIRD.skills · ★ 0 · Code & Development · score 74

Install: claude install-skill bird-chinese-community/BIRD.skills

# BIRD Tooling Installer Skill Guide users through installing BIRD editor support and the command-line interface toolkit. ## When to use this skill - The user asks how to install BIRD / BIRD2 / BIRD3 support in an editor. - The user asks for the VSCode / OpenVSX extension name for BIRD config. - The user asks how to install `birdcc`, `@birdcc/cli`, or the BIRD-LSP CLI. - The user wants to add BIRD syntax highlighting to Neovim, Vim, or JetBrains IDEA. - The user asks which BIRD editor plugins provide LSP versus only syntax highlighting. > For GitHub Actions or CI/CD questions, use the `birdcc-cicd` skill. > For editing or diagnosing BIRD config files, use the `bird-agent` skill. ## When NOT to use this skill - The user is asking about BIRD config syntax, route filters, protocols, or runtime behavior. - The user wants lint/format results for an existing BIRD config file. - The user is asking for a GitHub Actions workflow that installs `birdcc` or runs diagnostics. - The user is troubleshooting a running `bird` daemon. ## Core principles 1. **Detect the user's editor first.** Run `scripts/detect_editor.py` and `scripts/detect_ide.py` and inspect the workspace to infer the editor. If confidence is low and the user has not named an editor, ask. See `references/editors.md` for detection cues. 2. **Default to official marketplace / OpenVSX / JetBrains Marketplace.** Provide deep links before CLI commands, and CLI commands before VSIX fallback. 3. **Do not auto-inst