create-pipeline
Skill2 starsChanged 15 days agoMITView on GitHub
Create or update a CooperativeAICoding solution's CI/CD pipeline and missing infrastructure, driven by the infrastructure and scaffold blocks in its solution spec. Use when the user asks to set up a pipeline, deployment, CI, or infrastructure for a solution. Never writes secret values into code or committed config — secrets are referenced by name from their stores.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- harness/harness-skillstheir own version, first seen Nov 1, 2026
- glassflow/agent-skillstheir own version, first seen Oct 15, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- harness/harness-skills★ 127same name
- glassflow/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- buildSkill
- debtSkill
- draftSkill
- emit-guardrailsSkill
- new-itemSkill
- pipelineSkill
- productSkill
- qaSkill
- translateSkill
- verifySkill
- draft-briefSkill
- emit-guardrailsSkill
- translate-briefSkill
- buildSkill
- debtSkill
- draftSkill
- emit-guardrailsSkill
- new-itemSkill
- pipelineSkill
- productSkill
- qaSkill
- translateSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Read ai-only/procedures/pipeline.md under the project root you are working in, and follow it exactly.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Read ai-only/procedures/pipeline.md under the project root you are working in,
and follow it exactly. In this repository the canonical copy is
template/ai-only/procedures/pipeline.md; a project created with
coperativeai init has it at
ai-only/procedures/pipeline.md.
The procedure is the instruction, and it lives there rather than here so that
an agent which is not Claude Code reads the same text from AGENTS.md instead of
a copy that has drifted. Do not add behaviour to this file: a rule that exists in
.claude/ and nowhere else is a rule only one model follows.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.