New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Kode Capabilities Manager

by shareAI-lab in shareAI-lab/Kode-CLI

Lets the Kode agent manage its own features, such as LSP, statusline, output styles and plugins, by running its slash commands for you instead of listing install steps.

Apache-2.0Auto-check passedAgent Workflows

Install Kode Capabilities Manager

skills CLI
$ npx skills add shareAI-lab/Kode-CLI --skill capabilities-manage -a claude-code

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

GitHub CLI
$ gh skill install shareAI-lab/Kode-CLI capabilities-manage --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/shareAI-lab/Kode-CLI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/builtin-skills/skills/capabilities-manage .claude/skills/capabilities-manage && 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
capabilities-manage
GitHub stars
5.2k
Token cost
~760 tokens
SKILL.md length
330 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

Lets the Kode agent manage its own features, such as LSP, statusline, output styles and plugins, by running its slash commands for you instead of listing install steps.

  • Works in 4 steps: Clarify which capability: statusline /… → Inspect current state with minimal… → Apply changes → …
  • Enabling or disabling a Kode feature such as LSP, statusline or an output style
  • SKILL.md covers Goal, Rules (do not violate), Workflow and Capabilities audit…
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Users state an intent, for example enable LSP for TypeScript or fix my statusline, and the agent makes the change through the Kode CLI. The rules forbid installation-menu scripts and long lists of install commands, prefer SlashCommand to run /statusline, /lsp and /plugin, and require changes to be minimal, reversible and verified afterward.

The workflow is to clarify which capability is meant, inspect its state by reading settings files such as ~/.kode/settings.json and .kode/settings.local.json, apply the change and verify it. A statusline is set up by creating a Task with the statusline-setup subagent, LSP depends on a plugin that provides .lsp.json mappings and is checked on the /lsp screen, and output styles are set with the outputStyle setting. A capabilities audit returns a short OK or needs-attention checklist, passes permission problems to a permissions-debug skill and fixes what is safe to fix.

When your agent uses it

  • Enabling or disabling a Kode feature such as LSP, statusline or an output style
  • Finding out why a capability is switched off
  • Running a quick audit of which Kode capabilities are set up
  • Letting the agent configure Kode plugins on your behalf

Example prompts

  • “Enable LSP for TypeScript in this project.”
  • “Fix my statusline, it stopped showing.”
  • “Audit my Kode capabilities and tell me what needs attention.”

Requirements

  • The Kode CLI
  • Pre-approved tools (allowed-tools): SlashCommand, Read, Edit, Task, Skill

Workflow steps

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

  1. Clarify which capability: statusline / lsp / output-style / plugins (or multiple).
  2. Inspect current state with minimal friction
  3. Apply changes
  4. Verify: re-check status screens and run a minimal real operation.

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • SlashCommand
    • Read
    • Edit
    • Task
    • Skill

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Kode Capabilities Manager loads about 760 tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 330 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~760

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 shareAI-lab/Kode-CLI at commit c7f6fcc, republished under its Apache-2.0 licence (© shareAI-lab). 330 words, ~760 tokens.

Download SKILL.mdSave it as .claude/skills/capabilities-manage/SKILL.md (or your agent's skills folder).
name
capabilities-manage
description
Kode capability-management playbook: treat features (LSP, statusline, output styles, plugins, notifications) as configurable capabilities and drive changes through the agent CLI (SlashCommand/Task) instead of pushing users into menu-like flows. Use when the user asks to enable/disable/configure a capability, diagnose why it’s off, or wants the agent to self-manage Kode’s own features (meta capability management).
allowed-tools
SlashCommand, Read, Edit, Task, Skill

Capabilities Manage

Goal

Make users manage Kode features by expressing intent (“enable LSP for TS”, “fix my statusline”) while the agent performs the necessary actions via the agent CLI.

Rules (do not violate)

  • Do not output “installation menu” scripts or long lists of install commands.
  • Prefer SlashCommand to run Kode commands (/statusline, /lsp, /plugin ...) instead of asking the user to do it manually.
  • Keep changes minimal and reversible; verify after each change.

Workflow

  1. Clarify which capability: statusline / lsp / output-style / plugins (or multiple).
  2. Inspect current state with minimal friction:
    • Read settings files (~/.kode/settings.json, .kode/settings.local.json).
    • For interactive status screens, ask the user to open them (single step): /lsp, /output-style.
  3. Apply changes:
    • statusline: create a Task with subagent_type statusline-setup (do not ask the user to memorize the command).
    • lsp: ensure a plugin provides .lsp.json mappings; manage via /plugin, then re-check via /lsp screen.
    • output styles: set outputStyle in settings (or ask the user to choose via /output-style); for edits, edit the output style markdown file and then re-check /output-style.
  4. Verify: re-check status screens and run a minimal real operation.

Keep this fast and low-friction: default output should be a short checklist and only one question when a choice is required.

  1. Read current settings (best effort):
    • ~/.kode/settings.json (global)
    • .kode/settings.local.json (project, if present)
  2. Produce a compact checklist (OK / Needs attention) for:
    • Statusline: global settings.json contains statusLine.
    • Output style: either settings file contains a non-empty outputStyle string.
    • Plugins & LSP readiness: mention that LSP is plugin-driven; if the user cares, ask them to open /lsp (single step) to confirm resolved servers.
    • Permission friction: if the user reports unexpected denials/repeated prompts, invoke the permissions-debug skill.
  3. Auto-fix what you can safely:
    • Statusline: if requested, create a Task with subagent_type statusline-setup (do not ask the user to memorize the command).
    • Output style: set outputStyle in .kode/settings.local.json (project) or ~/.kode/settings.json (global) and re-read to verify.
  4. Verify each fix immediately by re-reading the changed file(s) and summarizing what changed.

© shareAI-lab, 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

Just SKILL.md in packages/builtin-skills/skills/capabilities-manage of shareAI-lab/Kode-CLI.

Open the folder on GitHubat commit c7f6fcc

Compare with similar skills

Kode Capabilities Manager 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.

Kode Capabilities Manager compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Kode Capabilities Manager this skillshareAI-lab/Kode-CLI5.2k—~760Automated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Claude Code Agent Developmentanthropics/claude-plugins-official38k7 repos~2.8kAutomated safety check: PassApache-2.0
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase10k11 repos~3.5kAutomated safety check: PassMIT
Plugin Settings Patternanthropics/claude-plugins-official38k7 repos~3kAutomated safety check: PassApache-2.0
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 11 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

  • Plugin Settings Pattern

    anthropics/claude-plugins-official

    Official

    Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.

    38k GitHub starsUsed in 7 repos~3k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Command Development

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.

    38k GitHub starsUsed in 10 repos~4.8k tokens
    Agent WorkflowsAuto-check passed

More from shareAI-lab/Kode-CLI

All 8 skills in this repo

  • Skill Creator

    shareAI-lab/Kode-CLI

    Guides writing a new agent skill or improving an existing one, covering how to keep it concise, how much freedom to give the agent and how to lay out bundled resources.

    5.2k GitHub starsUsed in 1 repo~4.4k tokens
    Auto-check passed

  • Skill Judge

    shareAI-lab/Kode-CLI

    Evaluates the design quality of an agent skill against official specifications and patterns from existing examples, scoring it and suggesting improvements.

    5.2k GitHub starsUsed in 4 repos~7.5k tokens
    Auto-check passed

  • Vibe Coding Partner

    shareAI-lab/Kode-CLI

    Gives an agent a set of working rules for any development task: understand first, surface decisions, verify results, and load deeper reference files per scenario.

    5.2k GitHub stars~5.6k tokensUpdated yesterday
    Auto-check passed

  • Doc Co-Authoring Workflow

    shareAI-lab/Kode-CLI

    Guides a three-stage workflow for turning partial context into a clear PRD, RFC or design doc: capture context, draft section by section, then test with a fresh reader.

    5.2k GitHub stars~977 tokensUpdated yesterday
    Auto-check passed

  • Kode LSP Maintenance

    shareAI-lab/Kode-CLI

    Diagnoses why Kode's LSP tool returns nothing and fixes it through plugin .lsp.json files and slash commands, then verifies with a real LSP call.

    5.2k GitHub stars~573 tokensUpdated yesterday
    Auto-check passed

  • MCP Server Builder

    shareAI-lab/Kode-CLI

    Guide to designing and building MCP servers: tool, resource and prompt design for agent usability, with TypeScript or Python implementation workflows.

    5.2k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Kode Capabilities Manager

What does Kode Capabilities Manager do?

Lets the Kode agent manage its own features, such as LSP, statusline, output styles and plugins, by running its slash commands for you instead of listing install steps. Users state an intent, for example enable LSP for TypeScript or fix my statusline, and the agent makes the change through the Kode CLI. The rules forbid installation-menu scripts and long lists of install commands, prefer SlashCommand to run /statusline, /lsp and /plugin, and require changes to be minimal, reversible and verified afterward.

When should I use Kode Capabilities Manager?

Kode Capabilities Manager fits situations like: enabling or disabling a Kode feature such as LSP, statusline or an output style; finding out why a capability is switched off; running a quick audit of which Kode capabilities are set up; letting the agent configure Kode plugins on your behalf.

How do I install Kode Capabilities Manager in Claude Code?

Run `npx skills add shareAI-lab/Kode-CLI --skill capabilities-manage -a claude-code`. Or copy the skill folder (packages/builtin-skills/skills/capabilities-manage in shareAI-lab/Kode-CLI) into .claude/skills/capabilities-manage in your project. Claude Code loads it when a task matches its description.

How do I install Kode Capabilities Manager in Codex?

Run `npx skills add shareAI-lab/Kode-CLI --skill capabilities-manage -a codex`. Or copy the skill folder (packages/builtin-skills/skills/capabilities-manage in shareAI-lab/Kode-CLI) into .agents/skills/capabilities-manage in your project. Codex loads it when a task matches its description.

Can I use Kode Capabilities Manager 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 shareAI-lab/Kode-CLI --skill capabilities-manage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/capabilities-manage, .gemini/skills/capabilities-manage, .github/skills/capabilities-manage and .opencode/skills/capabilities-manage in your project.

What does Kode Capabilities Manager need to run?

SKILL.md names no scripts, command-line tools or credentials: Kode Capabilities Manager is instructions for the agent only. Our summary lists: The Kode CLI. Its frontmatter pre-approves these tools: SlashCommand, Read, Edit, Task, Skill.

Does Kode Capabilities Manager access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Kode Capabilities Manager 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 Kode Capabilities Manager use?

Kode Capabilities Manager 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 Kode Capabilities Manager use?

About 760 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Kode Capabilities Manager?

Skills that share tags, products or a category with Kode Capabilities Manager: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars) and Plugin Settings Pattern (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kode Capabilities Manager?

shareAI-lab (a GitHub organization) maintains it in shareAI-lab/Kode-CLI, which has 5,234 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.

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