Agent skill

Kelos

by kelos-dev in kelos-dev/kelos

Install and configure Kelos; author, document, inspect, troubleshoot, and operate its Kubernetes custom resources and CRD schemas in the kelos.dev API group using manifests, kubectl, or the kelos CLI.

Apache-2.0Auto-check passedDevOps & Cloud

Install Kelos

skills CLI
$ npx skills add kelos-dev/kelos --skill kelos -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kelos-dev/kelos kelos --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kelos-dev/kelos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/kelos .claude/skills/kelos && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
kelos
GitHub stars
336
Token cost
~1.3k tokens
SKILL.md length
446 words
Files
8 (incl. references)
Skills in repo
1
Repo updated
First seen
Licence
Apache-2.0

At a glance

Install and configure Kelos; author, document, inspect, troubleshoot, and operate its Kubernetes custom resources and CRD schemas in the kelos.dev API group using manifests, kubectl, or the kelos CLI.

  • Works in 5 steps: Identify the resource kind, name, and… → Prefer scoped reads such as kelos get… → Check whether referenced resources and… → …
  • A request names Kelos
  • SKILL.md covers When To Use, Loading Rule, Resource Summary and References, plus 2 more sections
  • Calls kubectl; reaches github.com

What it does

Kelos is an agent skill from kelos-dev/kelos. Install and configure Kelos; author, document, inspect, troubleshoot, and operate its Kubernetes custom resources and CRD schemas in the kelos.dev API group using manifests, kubectl, or the kelos CLI. Use when a request names Kelos or a distinctive Kelos kind such as AgentConfig or TaskSpawner and concerns an installation, CLI command, API or CRD schema, manifest or example, resource-field documentation, or live custom resource. Do not use for ordinary code, test, build, review, CI, or Git work, even in the Kelos…

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/agentconfig.yaml`, `references/cli.md` and `references/session.yaml`).

It sits in DevOps & Cloud, covering Container orchestration. It works with Kubernetes, Git and Google Gemini. The repository describes itself as: Kelos - The Kubernetes-native framework for orchestrating autonomous AI coding agents. The licence is Apache-2.0.

When your agent uses it

  • A request names Kelos
  • A distinctive Kelos kind such as AgentConfig
  • TaskSpawner and concerns an installation
  • Resource-field documentation

Example prompts

  • “/kelos”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Identify the resource kind, name, and namespace before running broad queries.
  2. Prefer scoped reads such as kelos get task NAME -d,
  3. Check whether referenced resources and Secrets exist before assuming a
  4. Use full YAML or JSON when comparing resource state. Avoid relying only on
  5. If editing manifests in the Kelos repository, keep changes narrow and run

What it can do on your machine

Read from SKILL.md and the folder at commit d64960f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • kubectl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Kelos loads about 1.3k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 144 tokens; SKILL.md has 446 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~144
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from kelos-dev/kelos at commit d64960f, republished under its Apache-2.0 licence (© kelos-dev). 446 words, ~1,346 tokens.

Download SKILL.mdSave it as .claude/skills/kelos/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
kelos
description
Install and configure Kelos; author, document, inspect, troubleshoot, and operate its Kubernetes custom resources and CRD schemas in the kelos.dev API group using manifests, kubectl, or the kelos CLI. Use when a request names Kelos or a distinctive Kelos kind such as AgentConfig or TaskSpawner and concerns an installation, CLI command, API or CRD schema, manifest or example, resource-field documentation, or live custom resource. Do not use for ordinary code, test, build, review, CI, or Git work, even in the Kelos repository or on a service hosted under kelos.dev.

Kelos Skill

Use this skill as a compact guide for Kelos resource work. Keep context small: use the quick summary first, and read only the reference file that matches the user's request.

When To Use

Use this skill for:

  • Authoring or editing Kelos manifests for Task, Session, Workspace, AgentConfig, or TaskSpawner.
  • Debugging live Kelos resources on Kubernetes with kelos or kubectl.
  • Operating Kelos installs, task runs, logs, suspension, deletion, or cluster resources.
  • Editing Kelos CRD/API examples, generated CRDs, self-development manifests, or docs that describe resource fields.

Do not use this skill for ordinary Kelos repository code edits, tests, reviews, CI fixes, or git work unless the request specifically involves Kelos resources, CRDs, resource YAML, examples, self-development manifests, or cluster operations.

Loading Rule

  • For a simple CLI operation, use the quick commands below and do not open references.
  • For one resource kind, open only that resource's reference file.
  • For multi-resource manifests, open only the involved resource references.
  • For live debugging, start with the operational workflow below, then open references/troubleshooting.md only if the symptom matches.
  • For API or CRD source changes, verify current Go types and generated CRDs in the repo before trusting examples. Examples are patterns, not the source of truth.

Resource Summary

Kelos resources use apiVersion: kelos.dev/v1alpha2.

ResourcePurposeKey fields
TaskSingle agent runspec.type, spec.prompt, spec.credentials, spec.workspaceRef, spec.agentConfigRefs[], spec.branch, spec.dependsOn, spec.model, spec.effort, spec.podOverrides, spec.ttlSecondsAfterFinished
SessionPersistent interactive agent conversationspec.worker, spec.volumeClaimTemplate
WorkspaceGit repository for the agentspec.repo, spec.ref, spec.secretRef, spec.remotes, spec.files
AgentConfigReusable instructions and toolsspec.agentsMD, spec.plugins, spec.skills, spec.mcpServers
TaskSpawnerCreates Tasks from external sourcesspec.when.githubIssues, spec.when.githubPullRequests, spec.when.cron, spec.when.jira, per-source pollInterval, spec.taskTemplate, spec.maxConcurrency, spec.maxTotalTasks, spec.suspend

Task phases are Pending, Waiting, Running, Succeeded, and Failed. Session phases are Pending, Ready, and Failed.

Show full SKILL.md (161 more words)Show less

References

NeedRead
Task examples, credentials, dependencies, branch locks, pod overrides, TTLreferences/task.yaml
Session examples, worker configuration, ephemeral or persistent storagereferences/session.yaml
Workspace examples, repository auth, remotes, injected filesreferences/workspace.yaml
AgentConfig examples, plugins, skills, agents, MCP serversreferences/agentconfig.yaml
TaskSpawner examples, GitHub/Jira/cron sources, comment policy, concurrencyreferences/taskspawner.yaml
CLI flags, config file, supported agent types, install/uninstallreferences/cli.md
Pending/Waiting/Failed tasks, spawner issues, AgentConfig issues, push failuresreferences/troubleshooting.md

CLI Quick Commands

bash
kelos install
kelos uninstall
kelos init

kelos run -p "Fix the login bug" --type claude-code
kelos run -p "Add tests" --workspace my-ws --agent-config my-ac
kelos run -p "Refactor auth" --model opus --effort high --branch feature/auth
kelos run -p "Fix bug" -w

kelos run --from taskspawner/daily-audit
kelos run --from taskspawner/issue-worker -f values.yaml

kelos create workspace my-ws --repo https://github.com/org/repo.git --ref main --secret github-token
kelos create agentconfig my-ac --skill review=@review.md --dry-run

kelos get tasks
kelos get sessions
kelos get task my-task -d
kelos get task my-task -o yaml
kelos get session my-session -d
kelos session connect my-session
kelos logs my-task -f

kelos suspend taskspawner my-spawner
kelos resume taskspawner my-spawner
kelos delete task my-task
kelos delete session my-session

Operational Workflow

  1. Identify the resource kind, name, and namespace before running broad queries.
  2. Prefer scoped reads such as kelos get task NAME -d, kelos logs NAME -f, or kubectl get task NAME -o yaml.
  3. Check whether referenced resources and Secrets exist before assuming a controller bug. Do not print Secret values.
  4. Use full YAML or JSON when comparing resource state. Avoid relying only on table output for debugging.
  5. If editing manifests in the Kelos repository, keep changes narrow and run the project's Makefile targets requested by the repo instructions.

© kelos-dev, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in skills/kelos of kelos-dev/kelos.

  • SKILL.md
  • references/agentconfig.yaml
  • references/cli.md
  • references/session.yaml
  • references/task.yaml
  • references/taskspawner.yaml
  • references/troubleshooting.md
  • references/workspace.yaml

Open the folder on GitHubat commit d64960f

Compare with similar skills

Kelos next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Kelos compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Kelos this skillkelos-dev/kelos336—~1.3kAutomated safety check: PassApache-2.0
GitOps with ArgoCD and Fluxwshobson/agents40k11 repos~1.5kAutomated safety check: PassMIT
HypaHypabolic/Hypa207—~2.6kAutomated safety check: PassCustom licence
Tokf Runmpecan/tokf199—~571Automated safety check: PassMIT
Argocd GitopsBagelHole/DevOps-Security-Agent-Skills1.1k—~2.4kAutomated safety check: PassMIT
Alloygrafana/skills278—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Sets up GitOps continuous delivery for Kubernetes with ArgoCD or Flux, covering installation, repository layout, sync policies, progressive delivery and secrets.

    40k GitHub starsUsed in 11 repos~1.5k tokens
    DevOps & CloudAuto-check passed
  • Hypa

    Hypabolic/Hypa

    Context-optimized command runtime. An agent skill from Hypabolic/Hypa.

    207 GitHub stars~2.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Tokf Run

    mpecan/tokf

    Compress verbose CLI output with tokf before returning results.

    199 GitHub stars~571 tokensUpdated 5 days ago
    DevOps & CloudAuto-check passed
  • Argocd Gitops

    BagelHole/DevOps-Security-Agent-Skills

    Implement GitOps with ArgoCD for declarative Kubernetes deployments.

    1.1k GitHub stars~2.4k tokensUpdated 4 mo ago
    DevOps & CloudAuto-check passed
  • Alloy

    grafana/skills

    Official

    Build a unified telemetry pipeline with Grafana Alloy — one OpenTelemetry-compatible binary that collects metrics, logs, traces, and profiles and ships to Grafana Cloud / Prometheus / Loki / Tempo /…

    278 GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Implementing Gitops

    ancoleman/ai-design-components

    Implement GitOps continuous delivery for Kubernetes using ArgoCD or Flux.

    526 GitHub stars~2.9k tokensUpdated 10 mo ago
    DevOps & CloudAuto-check passed

Categories

Questions about Kelos

What does Kelos do?

Install and configure Kelos; author, document, inspect, troubleshoot, and operate its Kubernetes custom resources and CRD schemas in the kelos.dev API group using manifests, kubectl, or the kelos CLI. Kelos is an agent skill from kelos-dev/kelos.dev API group using manifests, kubectl, or the kelos CLI.

When should I use Kelos?

Kelos fits situations like: A request names Kelos; A distinctive Kelos kind such as AgentConfig; taskSpawner and concerns an installation; resource-field documentation.

How do I install Kelos in Claude Code?

Run `npx skills add kelos-dev/kelos --skill kelos -a claude-code`. Or copy the skill folder (skills/kelos in kelos-dev/kelos) into .claude/skills/kelos in your project. Claude Code loads it when a task matches its description.

How do I install Kelos in Codex?

Run `npx skills add kelos-dev/kelos --skill kelos -a codex`. Or copy the skill folder (skills/kelos in kelos-dev/kelos) into .agents/skills/kelos in your project. Codex loads it when a task matches its description.

Can I use Kelos in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kelos-dev/kelos --skill kelos -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kelos, .gemini/skills/kelos, .github/skills/kelos and .opencode/skills/kelos in your project.

What does Kelos need to run?

Going by SKILL.md and its folder, Kelos needs the command-line tools its instructions call (kubectl).

Does Kelos access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Kelos safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Kelos use?

Kelos is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Kelos use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.5k tokens, read only when the agent opens those files.

What are the alternatives to Kelos?

Skills that share tags, products or a category with Kelos: GitOps with ArgoCD and Flux (wshobson/agents, 40k stars), Hypa (Hypabolic/Hypa, 207 stars), Tokf Run (mpecan/tokf, 199 stars) and Argocd Gitops (BagelHole/DevOps-Security-Agent-Skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kelos?

kelos-dev (a GitHub organization) maintains it in kelos-dev/kelos, which has 336 GitHub stars. The repository was last updated on October 7, 2026.

Source: kelos-dev/kelos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.