Agent skill

Using Agent Skills

by kdlbs in kdlbs/kandev

Discover and choose the right Kandev agent skill for a task.

AGPL-3.0Auto-check passedTesting & QA

Install Using Agent Skills

skills CLI
$ npx skills add kdlbs/kandev --skill using-agent-skills -a claude-code

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

GitHub CLI
$ gh skill install kdlbs/kandev using-agent-skills --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/kdlbs/kandev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/using-agent-skills .claude/skills/using-agent-skills && 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
using-agent-skills
GitHub stars
909
Token cost
~1.5k tokens
SKILL.md length
397 words
Files
1
Skills in repo
45
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Discover and choose the right Kandev agent skill for a task.

  • Works in 10 steps: Work in the user-started primary… → Check for an applicable local skill… → If multiple skills apply, use the… → …
  • Starting a session
  • SKILL.md covers Skill Map, Operating Rules and Upstream Name Mapping
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Using Agent Skills is an agent skill from kdlbs/kandev. Discover and choose the right Kandev agent skill for a task. Use when starting a session, when the user asks which skill applies, when work spans multiple phases, or when existing skill references need to be mapped to this repo's actual skills.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA. The repository describes itself as: AI Kanban & Development Environment. Orchestrate multiple agents, review changes, open PRs. Multi-provider, self-hostable, no telemetry. The licence is AGPL-3.0.

When your agent uses it

  • Starting a session
  • The user asks which skill applies
  • Work spans multiple phases
  • Existing skill references need to be mapped to this repos actual skills

Example prompts

  • “/using-agent-skills”

Workflow steps

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

  1. Work in the user-started primary conversation; do not create a worker session.
  2. Check for an applicable local skill before starting non-trivial work.
  3. If multiple skills apply, use the smallest set that covers the task and state the order.
  4. Skills are workflows, not suggestions. Follow required verification and stop conditions.
  5. Surface assumptions before building on them. If requirements, specs, and code disagree, stop and name the conflict.
  6. Keep scope tight. Do not refactor adjacent systems or add "useful" features that are not in the request/spec.
  7. Verify with evidence: targeted task-defined tests and browser/E2E proof for
  8. Keep all repository work in the primary conversation. Use durable
  9. Product media always invokes /product-demo-seeding before /product-video-capture, even when a prior seed or capture exists. Re-prove…
  10. In Kandev repos, local /commit, /push, and /pr workflows, the repository

What it can do on your machine

Read from SKILL.md and the folder at commit bd63da3. 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

    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

Using Agent Skills loads about 1.5k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 397 words of instructions outside code blocks.

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

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 kdlbs/kandev at commit bd63da3, republished under its AGPL-3.0 licence (© kdlbs). 397 words, ~1,464 tokens.

Download SKILL.mdSave it as .claude/skills/using-agent-skills/SKILL.md (or your agent's skills folder).
name
using-agent-skills
description
Discover and choose the right Kandev agent skill for a task. Use when starting a session, when the user asks which skill applies, when work spans multiple phases, or when existing skill references need to be mapped to this repo's actual skills.

Using Agent Skills

Use this as the routing map for Kandev's local skills. Prefer the repo's existing skills over importing adjacent upstream names.

Skill Map

text
Task arrives
|
|-- Standalone interview or stress test? --> /interview-me
|-- Feature/fix planning assumptions? -----> /interview-me (question only material unknowns)
|-- Large initiative with dependent unknowns? -> /interview-me decision-mapping reference
|-- Create/change/fix/publish Kandev plugin? -> /create-kandev-plugin plus /fix or /tdd as needed
|-- New feature or behavior-changing fix? --> /spec-driven-development
|-- Bug regression? ------------------------> /fix -> requirement/design check -> fix plan/work orders -> /tdd
|-- Running/debugging Kandev locally? ------> /debug
|-- Inspecting native Codex app-server protocol? -> /codex-app-server-debug
|-- Need focused context setup? ------------> /context-engineering
|-- Code change with test coverage? --------> /tdd
|-- Browser/E2E coverage? ------------------> /e2e
|-- Seed isolated product demo data? -------> /product-demo-seeding
|-- Record landing/product media? ----------> /product-demo-seeding -> /product-video-capture (always in that order)
|-- Frontend/UI change? --------------------> /mobile-parity plus /e2e as needed
|-- High-impact security boundary/concern? -> pause for a strong-model review per /planner-orchestration
|-- Test strategy or coverage gaps? --------> /tdd or /e2e in the current conversation
|-- Add debug logs? ------------------------> /debug
|-- Add Jira/Linear-style integration? -----> /add-integration
|-- Add/roll out/promote/graduate/remove a runtime feature flag or release toggle? -> /runtime-feature-flags
|-- Validate implementation? ----------------> /tdd plus exact task-defined tests/E2E
|-- Need local QA/review/simplification? ----> only on explicit user request or PR finding
|-- End-of-session retrospective? ---------> /retro (explicit request only)
|-- Improve skills/agents/commands? --------> /harness-improvement
|-- Record decisions/specification changes? -> /record
|-- Public docs impact? --------------------> /docs-maintainer -> /diagram-design when a visual helps
|-- Commit/push/PR? ------------------------> /commit -> /push or /pr
`-- Release/versioning? --------------------> /release

When runtime-flag work also matches new behavior or validation, compose /runtime-feature-flags with /spec-driven-development and /tdd as needed. Use the smallest covering set and state the order.

Operating Rules

  1. Work in the user-started primary conversation; do not create a worker session.
  2. Check for an applicable local skill before starting non-trivial work.
  3. If multiple skills apply, use the smallest set that covers the task and state the order.
  4. Skills are workflows, not suggestions. Follow required verification and stop conditions.
  5. Surface assumptions before building on them. If requirements, specs, and code disagree, stop and name the conflict.
  6. Keep scope tight. Do not refactor adjacent systems or add "useful" features that are not in the request/spec.
  7. Verify with evidence: targeted task-defined tests and browser/E2E proof for user-facing flows. The two PR AI reviewers provide semantic review after PR creation; do not add broad local gates by default.
  8. Keep all repository work in the primary conversation. Use durable requirements, system designs, plans, and work orders as the user-controlled handoff when switching models.
  9. Product media always invokes /product-demo-seeding before /product-video-capture, even when a prior seed or capture exists. Re-prove current origin/main, disposable runtime/data, and teardown; never capture a developer instance or database.
  10. In Kandev repos, local /commit, /push, and /pr workflows, the repository PR template, and .github/AGENTS.md are authoritative for publication. External github:yeet is transport fallback only and must still use the local template and checklist; never replace them with a hand-composed body.
Show full SKILL.md (125 more words)Show less

Upstream Name Mapping

When adapting external skill references, map them to Kandev skills:

  • test-driven-development -> /tdd
  • spec-driven-development -> /spec-driven-development
  • planning-and-task-breakdown -> /plan
  • incremental-implementation -> /spec-driven-development or /tdd
  • debugging-and-error-recovery -> /debug or /fix
  • browser-testing-with-devtools -> /playwright-cli and /e2e
  • code-review-and-quality -> /code-review
  • security-auditor -> user-requested strong-model design review under /planner-orchestration
  • test-engineer -> /tdd or /e2e
  • code-simplification -> /simplify
  • git-workflow-and-versioning -> /commit, /push, /pr
  • documentation-and-adrs -> /record
  • harness-improvement -> /harness-improvement
  • observability-and-instrumentation -> /debug
  • shipping-and-launch -> /pr, /push, /release
  • frontend-ui-engineering -> /mobile-parity, /e2e, and frontend guidance in apps/web/AGENTS.md
  • api-and-interface-design -> scoped backend/frontend AGENTS.md plus /spec for public contracts
  • source-driven-development -> use official docs or primary sources, then follow the relevant implementation skill
  • doubt-driven-development -> direct design challenge inside /spec-driven-development; use /code-review or /qa only on explicit user request or PR/CI remediation

Do not reference upstream skills that are not installed unless you are explicitly importing or adapting them.

© kdlbs, AGPL-3.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 .agents/skills/using-agent-skills of kdlbs/kandev.

Open the folder on GitHubat commit bd63da3

Compare with similar skills

Using Agent Skills 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.

Using Agent Skills compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Using Agent Skills this skillkdlbs/kandev909—~1.5kAutomated safety check: PassAGPL-3.0
Chrome Devtoolsaeroxy/chrome-devtools-cli253—~9kAutomated safety check: WarnNone
Chrome Devtoolsgithub/awesome-copilot40k2 repos~1kAutomated safety check: PassMIT
Maggyalinaqi/maggy707—~1.5kAutomated safety check: PassMIT
Codex CLI TaskLeoYeAI/openclaw-master-skills2.2k—~7.1kAutomated safety check: PassMIT
Dogfood Exploratory QAvercel-labs/agent-browser44k8 repos~2.7kAutomated safety check: PassApache-2.0

Similar skills

  • Chrome Devtools

    aeroxy/chrome-devtools-cli

    A skill your agent uses when the user asks to "take a screenshot of a website", "navigate to a URL", "fill a form in the browser", "interact with Chrome", or when a chrome automation task is needed.

    253 GitHub stars~9k tokensUpdated 2 days ago
    Testing & QAAuto-check: warnings
  • Chrome Devtools

    github/awesome-copilot

    Official

    Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP.

    40k GitHub starsUsed in 2 repos~1k tokens
    Testing & QAAuto-check passed
  • Maggy

    alinaqi/maggy

    Maggy is a local AI engineering command center. An agent skill from alinaqi/maggy.

    707 GitHub stars~1.5k tokensUpdated 14 days ago
    Testing & QAAuto-check passed
  • Codex CLI Task

    LeoYeAI/openclaw-master-skills

    Launch OpenAI Codex CLI async in background with automatic delivery to Telegram/WhatsApp.

    2.2k GitHub stars~7.1k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Dogfood Exploratory QA

    vercel-labs/agent-browser

    Official

    Explores a web app with the agent-browser CLI to find bugs and UX problems, then writes a report with screenshots, repro videos and step-by-step reproduction for each issue.

    44k GitHub starsUsed in 8 repos~2.7k tokens
    Testing & QAAuto-check passed
  • Pester Failure Analysis

    PowerShell/PowerShell

    Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.

    56k GitHub stars~5.1k tokensUpdated today
    Testing & QAAuto-check passed

More from kdlbs/kandev

All 45 skills in this repo
  • PR Walkthrough

    kdlbs/kandev

    Generate a single-file HTML walkthrough that explains a PR's purpose, user impact, interface changes, compatibility risks, and implementation.

    909 GitHub stars~6.3k tokensUpdated today
    Auto-check passed
  • Debug

    kdlbs/kandev

    Diagnose Kandev bugs, running-instance issues, UI/browser failures, and runtime behavior.

    909 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Improve Kandev's AI harness from session learnings or explicit requests.

    909 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Diagram Design

    kdlbs/kandev

    Create branded architecture, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel…

    909 GitHub starsUsed in 1 repo~8k tokens
    Auto-check passed
  • TDD

    kdlbs/kandev

    Implement changes using Test-Driven Development (Red-Green-Refactor).

    909 GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • Verify

    kdlbs/kandev

    Run a broad local verification audit only when the user explicitly requests it or PR/CI remediation requires it.

    909 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Questions about Using Agent Skills

What does Using Agent Skills do?

Discover and choose the right Kandev agent skill for a task. Using Agent Skills is an agent skill from kdlbs/kandev. Discover and choose the right Kandev agent skill for a task.

When should I use Using Agent Skills?

Using Agent Skills fits situations like: starting a session; the user asks which skill applies; work spans multiple phases; existing skill references need to be mapped to this repos actual skills.

How do I install Using Agent Skills in Claude Code?

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

How do I install Using Agent Skills in Codex?

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

Can I use Using Agent Skills 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 kdlbs/kandev --skill using-agent-skills -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/using-agent-skills, .gemini/skills/using-agent-skills, .github/skills/using-agent-skills and .opencode/skills/using-agent-skills in your project.

What does Using Agent Skills need to run?

SKILL.md names no scripts, command-line tools or credentials: Using Agent Skills is instructions for the agent only.

Does Using Agent Skills 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 Using Agent Skills 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 Using Agent Skills use?

Using Agent Skills is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Using Agent Skills use?

About 1.5k tokens (SKILL.md is roughly 5.9k 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 Using Agent Skills?

Skills that share tags, products or a category with Using Agent Skills: Chrome Devtools (aeroxy/chrome-devtools-cli, 253 stars), Chrome Devtools (github/awesome-copilot, 40k stars), Maggy (alinaqi/maggy, 707 stars) and Codex CLI Task (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Using Agent Skills?

kdlbs (a GitHub organization) maintains it in kdlbs/kandev, which has 909 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on October 9, 2026.

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