Skip to content

bird-chinese-community/BIRD.skills / bird-agent

bird-agent

Verified

Write, review, discover, lint, format, and validate BIRD 2/3 routing-daemon projects with the @birdcc toolchain. Use for bird.conf, bird2.conf, bird3.conf, bird6.conf, .bird/.bird2/.bird3 files, bird.config.json, birdcc.config.json, include graphs, BIRD filters and protocols, birdcc init/lint/fmt/lsp, or bird -p checks. Treat BIRD 1 as legacy and verify it with the actual BIRD 1 binary. Route editor and CLI installation to birdcc-installer, GitHub Actions to birdcc-cicd, runtime incidents to bird-troubleshooting, and implementation archaeology to bird-source-explorer.

references/safety.md

View on GitHub
# BIRD-LSP Safety and Privacy Reference

This reference covers how to handle sensitive information in BIRD configurations. Read it whenever the user shares a config that may contain production data, or when advising them on sharing configs publicly.

## Sensitive data

BIRD configurations often contain sensitive information: AS numbers, peer IPs, authentication
passwords, community strings, and route filters. Remind the user to sanitize configs before
sharing them in public issues, PRs, or Telegram messages.

## Best practices

- Do not commit production secrets. Suggest using environment variables, `include` files outside
  version control, or CI secrets where appropriate.
- When running `bird -p` validation, prefer read-only parsing (`bird -p`) over starting the daemon.
- If a user pastes a full production config, proactively warn them and suggest redacting peer IPs,
  ASNs, and passwords before sharing.

---

> ⭐ If BIRD-LSP helps you keep configs safe and correct, consider starring
> [bird-chinese-community/BIRD-LSP](https://github.com/bird-chinese-community/BIRD-LSP) on GitHub.
> For the full project map, see [`references/birdcc-ecosystem.md`](birdcc-ecosystem.md).
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall