agentleFS
Aidas-devAidas-dev/k8s-agent-skills/skills/tekton/SKILL.md

tekton

Skill4 starsChanged 5 months agoMITView on GitHub

Use when working with Tekton — route to the correct sub-skill based on what you need: PipelineRun/TaskRun authoring, the Tekton operator (install/config), or Pipelines-as-Code (Git-native CI).

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If routing is ambiguous:

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Tekton — Skill Router

Operator: tektoncd/operator — latest v0.80.0 (2026-06-09); LTS v0.78.x (pipeline v1.6.x, EOL 2026-12-08), v0.77.x (EOL 2026-08-21). Min K8s 1.28. Pipelines-as-Code: tektoncd/pipelines-as-code — latest v0.49.0 (2026-07-06). API version: tekton.dev/v1 (authoring), operator.tekton.dev/v1alpha1 (operator CRs), pipelinesascode.tekton.dev/v1alpha1 (PaC Repository CR).

Overview

Tekton is Kubernetes-native CI/CD. Three surfaces:

  • Authoring — writing PipelineRun/TaskRun YAML (resolvers, when/CEL, matrix, podTemplate, timeouts) in tekton.dev/v1
  • Operator — installs/manages Tekton components (Pipelines, Triggers, Dashboard, Chains, Results, PaC) via TektonConfig + component CRs
  • Pipelines-as-Code (PaC) — Git-native CI: PipelineRuns live in .tekton/ in the repo, triggered by Git events (push/PR/comment), results reported back as PR checks

Which Sub-Skill?

Match the user's request against the trigger keywords below, then call skill(name="<matched-skill>") to load the sub-skill's full content.

Routing Table

Trigger keywordsUser wants to...Skill to load
pipelinerun, taskrun, resolver, git-resolver, taskRef, when, CEL, matrix, podTemplate, nodeSelector, tolerations, timeout, finally, workspaces, tekton.dev/v1Author/write Tekton pipeline YAMLtekton-pipelines
operator, TektonConfig, TektonPipeline, TektonTrigger, TektonDashboard, TektonChain, TektonResult, TektonPruner, profile, install tekton, upgrade tekton, component CRInstall/configure/manage Tekton components on a clustertekton-operator
pipelines-as-code, pipelinesascode, PaC, .tekton/, Repository CR, on-event, on-target-branch, on-path-change, on-comment, on-cel-expression, ChatOps, /retest, /test, tkn pac, git_auth_secret, trigger_commentGit-native CI: pipelines in repo, triggered by Git eventstekton-pac

Decision Tree

If routing is ambiguous:

  1. User is writing YAML for a pipeline (taskRef, when, matrix, podTemplate) → tekton-pipelines
  2. User is installing/configuring Tekton itself (TektonConfig CR, profiles, components) → tekton-operator
  3. User is setting up Git-triggered CI (Repository CR, .tekton annotations, webhooks, ChatOps) → tekton-pac
  4. Combination? → Load the one matching the primary action. Common pairs: operator installs Pipelines → PaC connects repos → pipelines authoring writes the runs. Authoring (.tekton/ files) + PaC (annotations on those files) are especially tight — load both for PaC work.

When NOT to load this router

  • User is working on a different CI system (GitHub Actions, Gitea Actions, GitLab CI) → those are their own skills/tools
  • User needs Kubernetes cluster automation (Flux, ArgoCD) → Tekton runs workloads; GitOps is a separate concern (flux skill)
  • User asks about generic GitOps pipelines without Tekton → check if they mean Flux/ArgoCD first
  • User just needs a quick version/overview → the Overview above is sufficient

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.