Use when working with ANY Concourse CI task: writing pipelines, configuring resources, building images with oci-build-task, troubleshooting failing jobs, migrating from legacy patterns, or optimizing CI/CD. Triggers on: Concourse, pipeline, fly CLI, resource type, oci-build-task, set_pipeline, concourse.yml.
From concourse-cinpx claudepluginhub netresearch/claude-code-marketplace --plugin concourse-ciThis skill is limited to using the following tools:
checkpoints.yamlexamples/basic-pipeline.ymlexamples/docker-build.ymlexamples/modern-ci-cd.ymlexamples/multi-branch.ymlexamples/vars-template.ymlreferences/best-practices.mdreferences/core-concepts.mdreferences/pipeline-syntax.mdreferences/resource-types-catalog.mdreferences/resources-guide.mdscripts/validate-pipeline.shSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides agent creation for Claude Code plugins with file templates, frontmatter specs (name, description, model), triggering examples, system prompts, and best practices.
Expert guidance for writing, refactoring, and optimizing Concourse CI pipelines (v8.0+).
oci-build-task| Task | Modern (Recommended) | Legacy (Avoid) |
|---|---|---|
| Building images | oci-build-task + registry-image | docker-image resource |
| Multi-env deploys | across step modifier | Duplicate jobs per env |
| Dynamic pipelines | set_pipeline + instanced pipelines | Manual pipeline duplication |
| Notification symbols | UTF-8 characters (e.g. \u2714 for checkmark, \u274c for X) | HTML entities (e.g. ✓, ✗) |
| Resource styling | Always use icon: property | No icon |
Pipelines consist of resources (external versioned artifacts), jobs (sequences of steps), and optional groups (UI organization). All execution runs in containers.
Key step types: get, put, task, set_pipeline, in_parallel, do, try, load_var. Job hooks: on_success, on_failure, on_error, on_abort, ensure. Note: on_failure (non-zero exit) differs from on_error (infrastructure crash/OOM) -- handle both. Use fly execute to test tasks locally.
See references/core-concepts.md for step types table, lifecycle hooks, and fly CLI essentials.
clean_tags: true, separate read/write resources, force recheck with fly -t T check-resource -r pipeline/resource. See references/resources-guide.md.registry-image expects an object (host: mirror), docker-image expects a URL string. Provide separate formats in CONCOURSE_BASE_RESOURCE_TYPE_DEFAULTS. See references/resources-guide.md.Www-Authenticate header. See references/resources-guide.md.references/pipeline-syntax.md -- Complete YAML schema for pipelines, jobs, resourcesreferences/core-concepts.md -- Step types, lifecycle hooks, fly CLI essentialsreferences/resources-guide.md -- Git-resource, registry-image, docker-image migration, gotcha detailsreferences/best-practices.md -- Optimization, troubleshooting, notifications, deployment patternsreferences/resource-types-catalog.md -- Available resource types (Ansible, Terraform, etc.)Working examples in examples/:
basic-pipeline.yml -- Build-test-deploy with versioningmodern-ci-cd.yml -- oci-build-task, across, build_log_retentionmulti-branch.yml -- Dynamic branch pipelines with set_pipelinedocker-build.yml -- Container image build and pushvars-template.yml -- Variable file organizationUse scripts/validate-pipeline.sh to check pipeline syntax before deployment.