bird-agentlisted

Use this skill for BIRD (BIRD1/2/3) routing daemon configuration work: files named bird.conf, bird2.conf, bird3.conf, or bird6.conf; pasted snippets with BIRD syntax like protocol, filter, function, table, local as, neighbor, route, prefix, bgp_path, community, import, export; and requests about linting, formatting, bird -p validation, cross-file includes, or BIRD keywords/commands. For editor plugin installation use birdcc-installer; for GitHub Actions use birdcc-cicd. Trigger even if the user doesn't say "BIRD" explicitly. Do NOT trigger for Cisco, Juniper, FRR, nginx, bird biology, or "bird" outside a BIRD routing context.
bird-chinese-community/BIRD-skills · ★ 0 · Code & Development · score 76

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

# BIRD Config Agent Skill Help users write, validate, format, and understand BIRD (BIRD1/2/3) routing daemon configuration files by orchestrating the BIRD-LSP toolchain and related BIRD documentation. ## When to use this skill - The user opens, edits, or asks about a file named `bird.conf`, `bird2.conf`, `bird3.conf`, `bird6.conf`, or any `.conf` file that contains BIRD routing syntax. - The user mentions BIRD, BIRD2, BIRD3, BGP, OSPF, RIP, RADV, Static, Kernel, Device, Perf, RPKI, Babel, Aggregator, or MRT protocols in a configuration context. - The user reports a syntax error, diagnostic, or wants to format a BIRD configuration. - The user wants to know what a BIRD keyword, function, filter, protocol, or CLI command does. - The user shares a BIRD configuration snippet and asks for review, optimization, or explanation. > For editor plugin installation, use the `birdcc-installer` skill. For GitHub Actions or CI/CD, > use the `birdcc-cicd` skill. ## Core principles 1. **Prefer the BIRD-LSP toolchain over ad-hoc text manipulation.** The toolchain provides parser-backed diagnostics, formatter-safe output, and `bird -p` runtime validation. Use `scripts/detect_bird_context.py` to discover config files and `scripts/run_birdcc.py` to run commands reliably. 2. **Support every editor equally.** Whether the user is in VSCode, Vim, Neovim, IDEA, OpenCode, Cursor, or a plain terminal, route them through the same CLI-based workflow. 3. **Version awareness.** BIRD1, B