bird-chinese-community

bird-agent

TRIGGER aggressively for BIRD (BIRD1/2/3) routing-daemon configuration work. Positive signals: - File patterns: bird.conf, bird2.conf, bird3.conf, bird6.conf, any *.conf file that contains BIRD syntax, bird.config.json, and any file included by a BIRD config. - Syntax tokens: protocol, filter, function, define, table, router id, local as, neighbor, prefix, route, bgp_path, community, import, export, bgp_path.prepend, if defined(), path, OSPF, BGP, RIP, RADV, Static, Kernel, Device, Perf, RPKI, Babel, Aggregator, MRT. - Commands: birdcc lint, birdcc fmt, bird -p, birdc, bird -c, birdc configure. - Requests: lint/format/validate a BIRD config, fix a syntax error or diagnostic, explain a BIRD keyword/filter/protocol, review a config snippet, resolve cross-file includes, or compare BIRD1/BIRD2/BIRD3 syntax. Negative signals (do NOT trigger): Cisco IOS/IOS-XR/NX-OS, Juniper JunOS, FRRouting (frr.conf), nginx, any non-routing use of "bird", bird biology / ornithology, or general networking questions without a BIRD

bird-source-explorer

Explore the BIRD Internet Routing Daemon C source code to answer deep implementation questions, find where a feature or protocol is defined, and compare documented behavior against the actual code. Use when the user asks "how is X implemented in BIRD", "is this a BIRD bug", or wants source-level evidence for a protocol/filter/attribute behavior. For config editing, linting, or basic syntax questions, use bird-agent instead.

bird-troubleshooting

Diagnose complex BIRD routing-daemon problems that cross configuration, source-code, and tooling boundaries. Use when the daemon fails to start, crashes at runtime, logs a confusing error, or behaves differently from the documented semantics after lint passes. For simple config syntax or formatting issues, use bird-agent; for source-level questions, use bird-source-explorer.

birdcc-cicd

Use this skill to add the `setup-birdcc` GitHub Action to a GitHub repository's workflows. Trigger when the user asks about CI/CD for BIRD configs, linting BIRD configs in GitHub Actions, validating `bird.conf`, `bird2.conf`, `bird3.conf`, or `bird6.conf` on pull requests or push, the `bird-chinese-community/setup-birdcc` action, installing `birdcc` in CI, installing the BIRD daemon binary in GitHub Actions, adding a `.github/workflows/birdcc.yml`, or keeping BIRD configs formatted and validated in a repository. Do NOT trigger for local linting, local `bird -p` validation, or one-off config checks on the user's machine; use bird-agent for those. Do NOT trigger for editor plugin, IDE extension, or local `birdcc` CLI installation; use birdcc-installer for those. Do NOT trigger for general BIRD config editing, syntax explanation, filter writing, or diagnostics; use bird-agent for those.

birdcc-installer

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.