{
  "markdown": "# Buildkite Skills\n\nThe official Buildkite skills for Claude Code, Cursor, and other AI coding\nagents. Install them into your agent of choice so it can generate correct\npipeline YAML, run `bk` and `buildkite-agent` CLI commands, call the API,\nconfigure agents, and run preflight builds.\n\n## Installation\n\n```bash\nnpx skills add buildkite/skills\n```\n\nSee [skills.sh](https://skills.sh) for supported agents and options.\n\n### Claude Code\n\nAdd the marketplace and install the plugin:\n\n```\n/plugin marketplace add buildkite/skills\n/plugin install buildkite@buildkite-skills\n```\n\n### Cursor\n\nSearch for **Buildkite Skills** in the Cursor Marketplace, or run `/add-plugin` and search for \"Buildkite\".\n\n### Kiro\n\nRecommended (one install): add the Buildkite **power** in the Powers panel, pointing at\n`github.com/buildkite/skills`. The root `POWER.md`, `mcp.json`, and `steering/`\ntogether give Kiro the Buildkite MCP server plus all six workflows (pipelines,\nmigration, preflight, agent-runtime, CLI, API), loaded automatically when relevant.\n\nAlternatively, install individual workflows as Kiro **skills** via the Skills panel —\neach `skills/buildkite-*/` directory already conforms to the open Agent Skills standard.\n\n### Manual\n\nCopy skill directories into your agent's skills folder:\n\n```bash\n# Claude Code\nmkdir -p .claude/skills\ncp -r skills/buildkite-pipelines .claude/skills/\ncp -r skills/buildkite-preflight .claude/skills/\ncp -r skills/buildkite-agent-runtime .claude/skills/\ncp -r skills/buildkite-cli .claude/skills/\ncp -r skills/buildkite-api .claude/skills/\ncp -r skills/buildkite-migration .claude/skills/\n\n# Cursor\nmkdir -p .cursor/skills\ncp -r skills/buildkite-pipelines .cursor/skills/\ncp -r skills/buildkite-preflight .cursor/skills/\ncp -r skills/buildkite-agent-runtime .cursor/skills/\ncp -r skills/buildkite-cli .cursor/skills/\ncp -r skills/buildkite-api .cursor/skills/\ncp -r skills/buildkite-migration .cursor/skills/\n```\n\n## Skills\n\n### Journey Skills\n\nSkills organized by what you are trying to accomplish.\n\n| Skill | Directory | Description |\n|-------|-----------|-------------|\n| **Pipelines** | [skills/buildkite-pipelines/](skills/buildkite-pipelines/SKILL.md) | Pipeline YAML, step types, plugins, caching, parallelism, dynamic pipelines, matrix builds, artifacts, hooks |\n| **Migration** | [skills/buildkite-migration/](skills/buildkite-migration/SKILL.md) | CI migration planning, converting from GitHub Actions, Jenkins, CircleCI, Bitbucket Pipelines, GitLab CI using `bk pipeline convert` |\n\n### Cross-Cutting Skills\n\nSkills needed across all journeys.\n\n| Skill | Directory | Description |\n|-------|-----------|-------------|\n| **Preflight** | [skills/buildkite-preflight/](skills/buildkite-preflight/SKILL.md) | `bk preflight` runs a CI build against local uncommitted changes |\n| **Agent Runtime** | [skills/buildkite-agent-runtime/](skills/buildkite-agent-runtime/SKILL.md) | `buildkite-agent` subcommands inside running job steps — annotate, artifact, meta-data, pipeline upload, OIDC, locks |\n| **CLI** | [skills/buildkite-cli/](skills/buildkite-cli/SKILL.md) | `bk` commands for builds, jobs, pipelines, secrets, artifacts, and auth |\n| **API** | [skills/buildkite-api/](skills/buildkite-api/SKILL.md) | REST API, GraphQL API, webhooks, authentication, pagination |\n\n## How Skills Differ from Docs\n\nBuildkite docs at [buildkite.com/docs](https://buildkite.com/docs) are the canonical\nreference for what Buildkite features exist and how they work.\n\nSkills serve a different purpose: they encode **expertise**. Where docs explain every\noption, skills teach agents the right defaults, common patterns, and mistakes to avoid.\nA skill captures the judgment an experienced Buildkite user applies — which step type to\nreach for, how to structure a dynamic pipeline, when to use OIDC instead of static tokens.\n\nIn practice this means:\n- Skills assume the agent already understands YAML, CI/CD concepts, and general programming\n- SKILL.md files focus on quick starts, recommended patterns, and pitfall tables — not exhaustive option lists\n- Detailed reference material lives in `references/` subdirectories, loaded only when needed\n- Skills link to Buildkite docs rather than reproducing them\n\nFor more on content strategy, see [CONVENTIONS.md](CONVENTIONS.md).\n\n## Contributing\n\n1. Read [CONVENTIONS.md](CONVENTIONS.md) — frontmatter format, section order, style rules, skill boundaries, quality checklist\n2. Review an existing complete skill as a quality benchmark (e.g. `skills/buildkite-pipelines/SKILL.md`)\n3. Check the boundary table in CONVENTIONS.md — each topic is owned by exactly one skill\n4. Write your skill following the section order and style rules\n\n## Documentation\n\nFull Buildkite docs at [buildkite.com/docs](https://buildkite.com/docs).\n\n## License\n\n[MIT](LICENSE)\n",
  "bytes": 4810,
  "sha": "fa16a6e0dcbf1c7402c31710ce8b157ddcf343339ee4abb32efc3c1c82101390",
  "repo_slug": "buildkite/skills",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_buildkite_skills_buildkite_7df802fa/readme"
}