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.

evals/evals.json

View on GitHub
{
  "skill_name": "bird-agent",
  "evals": [
    {
      "id": 1,
      "name": "read-only-project-discovery",
      "prompt": "This repository has many .conf files and I do not know which one is the BIRD entry point. Discover the project safely before linting.",
      "expected_output": "Use read-only context detection and birdcc init --dry-run --json, explain why generic .conf files are not enough, and do not create a config without approval.",
      "files": [],
      "assertions": [
        {
          "name": "uses_cli_discovery",
          "description": "Uses the current authoritative entry-point detector.",
          "check": "file_contains",
          "target": "transcript.md",
          "expected": "birdcc init"
        },
        {
          "name": "keeps_discovery_read_only",
          "description": "Uses dry-run or explicitly avoids writes.",
          "check": "file_contains_any",
          "target": "transcript.md",
          "expected": ["--dry-run", "read-only", "does not write", "不写入"]
        }
      ]
    },
    {
      "id": 2,
      "name": "missing-semicolon-diagnosis",
      "prompt": "Lint bird-agent/evals/fixtures/bird.conf and explain the failure without changing the fixture.",
      "expected_output": "Run birdcc lint, identify the missing semicolon after router id 192.0.2.1, and provide the corrected line without modifying the file.",
      "files": ["evals/fixtures/bird.conf"],
      "assertions": [
        {
          "name": "runs_lint",
          "description": "Invokes birdcc lint.",
          "check": "file_contains",
          "target": "transcript.md",
          "expected": "birdcc lint"
        },
        {
          "name": "shows_fix",
          "description": "Shows the corrected router id statement.",
          "check": "file_contains",
          "target": "transcript.md",
          "expected": "router id 192.0.2.1;"
        }
      ]
    },
    {
      "id": 3,
      "name": "format-preview",
      "prompt": "Preview formatting changes for bird-agent/evals/fixtures/bird-unformatted.conf, but do not write them yet.",
      "expected_output": "Run birdcc fmt --check, present the change, and wait for explicit approval before --write.",
      "files": ["evals/fixtures/bird-unformatted.conf"],
      "assertions": [
        {
          "name": "checks_only",
          "description": "Runs formatting in check mode.",
          "check": "file_contains",
          "target": "transcript.md",
          "expected": "--check"
        },
        {
          "name": "requires_approval",
          "description": "Does not write without approval.",
          "check": "file_contains_any",
          "target": "transcript.md",
          "expected": ["approval", "confirmation", "确认", "批准"]
        }
      ]
    },
    {
      "id": 4,
      "name": "cross-file-uri",
      "prompt": "Lint bird-agent/evals/fixtures/cross-file/main.conf and identify the actual included file that contains the problem.",
      "expected_output": "Lint the main entry with cross-file analysis and attribute the missing semicolon to peers.conf.",
      "files": ["evals/fixtures/cross-file/main.conf", "evals/fixtures/cross-file/peers.conf"],
      "assertions": [
        {
          "name": "identifies_included_file",
          "description": "Reports peers.conf as the diagnostic source.",
          "check": "file_contains",
          "target": "transcript.md",
          "expected": "peers.conf"
        },
        {
          "name": "uses_cross_file_behavior",
          "description": "Mentions include or cross-file analysis.",
          "check": "file_contains_any",
          "target": "transcript.md",
          "expected": ["include", "cross-file", "跨文件"]
        }
      ]
    },
    {
      "id": 5,
      "name": "legacy-bird1-boundary",
      "prompt": "My router runs BIRD 1.6. How do I make birdcc target BIRD1?",
      "expected_output": "Explain that the current toolchain primarily targets BIRD2/3, avoid inventing a target flag, and configure native validation through binaryPath or validateCommand.",
      "files": [],
      "assertions": [
        {
          "name": "states_best_effort_boundary",
          "description": "Does not claim first-class BIRD1 support.",
          "check": "file_contains_any",
          "target": "transcript.md",
          "expected": ["best-effort", "BIRD 2", "BIRD2", "legacy", "有限"]
        },
        {
          "name": "uses_real_validation_config",
          "description": "Uses a supported native validation setting.",
          "check": "file_contains_any",
          "target": "transcript.md",
          "expected": ["binaryPath", "validateCommand", "--validate-command"]
        }
      ]
    },
    {
      "id": 6,
      "name": "config-alias-migration",
      "prompt": "Our project still has birdcc.config.json. Is it supported, and what should new projects use?",
      "expected_output": "Explain that birdcc.config.json is a compatibility alias and bird.config.json plus bird.config.schema.json are canonical.",
      "files": [],
      "assertions": [
        {
          "name": "mentions_alias",
          "description": "Names the compatibility config.",
          "check": "file_contains",
          "target": "transcript.md",
          "expected": "birdcc.config.json"
        },
        {
          "name": "recommends_canonical_name",
          "description": "Recommends bird.config.json.",
          "check": "file_contains",
          "target": "transcript.md",
          "expected": "bird.config.json"
        }
      ]
    }
  ]
}
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