Kilo-Kit
by VoDaiLocz
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kilo_orchestrate_taskA | MANDATORY: Call this tool FIRST before diagnosing, debugging, analyzing, creating, or modifying any code, UI, backend, or project files. Determines task mode, selects required workflow skills, enforces brainstorming gating, and orchestrates the execution flow. |
| kilo_memory_reportB | Read global C4 memory facts, decisions, and recent suggestions. |
| kilo_record_reflectionB | Record correct approaches, wrong paths/pitfalls encountered, skill ratings, and lessons learned into SQLite to drive Kilo-Kit's continuous self-improvement across sessions. |
| kilo_remember_factA | Explicitly persist a project operating rule, workflow default, or verification standard into SQLite memory_facts for cross-session enforcement. |
| kilo_search_skillsA | Search the Kilo-Kit skill library by natural-language query. Use this for broad discovery before loading a specific skill. |
| kilo_get_skillB | Load a Kilo-Kit skill by name or category/skill. Supports fuzzy aliases (e.g. 'brainstorming', 'diagnose', 'playwright', 'tdd', 'productivity/brainstorming'). |
| kilo_route_intentB | Recommend the best Kilo-Kit skills for any user request, bug fix, feature, UI task, or coding issue. Call before selecting or executing a workflow skill. |
| kilo_route_reportB | Summarize route telemetry: top skills, task modes, workflow chains, score averages, and conflict penalties. |
| kilo_validate_skillsC | Run the Kilo-Kit skill validator and return a concise quality-gate summary. This is read-only and does not modify files. |
| kilo_read_fileB | Read file content safely across workspace boundaries (supports line ranges and byte capping up to 512KB). |
| kilo_search_filesB | Search for files matching a pattern, substring, or glob across the workspace. |
| kilo_grep_codeB | Search code snippets and matching lines across workspace files. |
| kilo_write_fileA | Create a new file or overwrite an existing file. PROTOCOL HARD-GATE: Requires valid sessionId in 'ready' state. |
| kilo_edit_fileA | Perform exact targeted search-and-replace edit on an existing file with AST check. PROTOCOL HARD-GATE: Requires valid sessionId in 'ready' state. |
| kilo_run_commandA | MANDATORY: Execute a terminal command with security guardrails and timeout. Use this INSTEAD OF native Bash/terminal tools. PROTOCOL HARD-GATE: Requires valid sessionId in 'ready' state. |
| kilo_think_stepB | Iterative step-by-step reasoning engine with hypothesis tracking, revision, and solution branching. |
| kilo_grill_planC | Automated adversarial stress-testing against Inversion, Simplification Cascades, Blast Radius, and Edge-cases. |
| kilo_trace_root_causeB | Recursive causal backward-propagation analysis from crash log to the underlying systemic root cause. |
| kilo_compact_contextA | Compacts verbose logs, test dumps, and noisy output by 40-70% while preserving architectural invariants. |
| kilo_synthesize_skillA | Distill a newly solved architectural pattern or bugfix methodology into a reusable, validated SKILL.md. |
| kilo_sentinel_statusB | Inspect real-time Sentinel supervisor telemetry: Circuit breaker state, step budget, failure streaks, and grounded files list. |
| kilo_reset_circuit_breakerA | Reset an open Circuit Breaker with justification and root-cause evidence. Transitions breaker to HALF_OPEN. |
| kilo_benchmark_solutionB | Audit the current session trajectory against open-source GitHub standards and industry best practices. Returns alignment score or triggers re-planning. |
| kilo_triangulate_researchB | Execute Triangulated Cognitive Synthesis: Combines Internal SQLite Memory, External GitHub Grounding, 3-Option ToT DAG Trade-Offs, and Low-Confidence Research Escalation. Persists reasoning atomically into SQLite before code modification. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| kilo-c4-workflow | Prompt the agent to use the C4 gate before substantive implementation work. |
| kilo-select-skill | Prompt the agent to route the current request through Kilo-Kit before implementation. |
| kilo-validate-library | Prompt the agent to run the Kilo-Kit validation quality gate. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| kilo-skills-index | Lightweight index for skill discovery. |
| kilo-core-master | Core Cognitive Flow Architecture and routing protocol. |
| kilo-c4-operating-rules | Minimal rules a host agent should follow after installing the Kilo-Kit MCP server. |
| agent-frameworks/agent-memory | Use when implementing or managing persistent, hierarchical memory systems for AI agents. Covers cross-session state, fact supersession, and self-managed memory tools to enable long-term recall and adaptive agent behavior. |
| agent-frameworks/claukit | Advanced Agentic Coding framework providing mission briefs, guardrails, and integration hints for complex tasks. This skill ensures high-quality output through disciplined automation and systematic workflows. |
| agent-frameworks/mcp-agent-patterns | Use when integrating or optimizing Model Context Protocol (MCP) servers and clients. Keywords: MCP, Model Context Protocol, tool discovery, lazy loading, sampling, resource subscription, MCP server. |
| agent-frameworks/multi-agent-orchestration | Use when coordinating multiple specialized agents for complex distributed tasks. Keywords: multi-agent, orchestrator, subagent, handoff, swarm, supervisor, agent topology, coordination. |
| agent-frameworks/workflow-state-machines | Use when designing, implementing, or debugging complex agentic workflows using state machine patterns. Keywords: state machine, durable execution, agent orchestration, graph-based agents, workflow checkpoints, C4 protocol. |
| ai-media/ai-multimodal | Process and generate multimedia content using Google Gemini API. Capabilities include analyze audio files (transcription with timestamps, summarization, speech understanding, music/sound analysis up to 9.5 hours), understand images (captioning, object detection, OCR, visual Q&A, segmentation), process videos (scene detection, Q&A, temporal analysis, YouTube URLs, up to 6 hours), extract from documents (PDF tables, forms, charts, diagrams, multi-page), generate images (text-to-image, editing, composition, refinement). Use when working with audio/video files, analyzing images or screenshots, processing PDF documents, extracting structured data from media, creating images from text prompts, or implementing multimodal AI features. Supports multiple models (Gemini 2.5/2.0) with context windows up to 2M tokens. |
| ai-media/geo-fundamentals | Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity). |
| ai-media/media-processing | Process multimedia files with FFmpeg (video/audio encoding, conversion, streaming, filtering, hardware acceleration) and ImageMagick (image manipulation, format conversion, batch processing, effects, composition). Use when converting media formats, encoding videos with specific codecs (H.264, H.265, VP9), resizing/cropping images, extracting audio from video, applying filters and effects, optimizing file sizes, creating streaming manifests (HLS/DASH), generating thumbnails, batch processing images, creating composite images, or implementing media processing pipelines. Supports 100+ formats, hardware acceleration (NVENC, QSV), and complex filtergraphs. |
| ai-media/screenshot | Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed. |
| ai-media/seo-fundamentals | SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles. |
| ai-media/sora | Use when the user asks to generate, remix, poll, list, download, or delete Sora videos via OpenAI’s video API using the bundled CLI (`scripts/sora.py`), including requests like “generate AI video,” “Sora,” “video remix,” “download video/thumbnail/spritesheet,” and batch video generation; requires `OPENAI_API_KEY` and Sora API access. |
| design/aesthetic | Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills. |
| design/figma | Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting. |
| design/figma-implement-design | Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection. |
| design/frontend-design | Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. |
| design/mobile-design | Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps. |
| design/tailwind-patterns | Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture. |
| design/ui-styling | Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications. |
| engineering/agentic-rag | Use when building self-correcting retrieval systems for AI agents. Keywords: RAG, retrieval, Corrective RAG, Self-RAG, query decomposition, reranking, hallucination, grounding. |
| engineering/api-patterns | API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination. |
| engineering/app-builder | Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents. |
| engineering/app-builder/templates | Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks. |
| engineering/architecture | Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design. |
| engineering/ask-matt | Ask which skill or flow fits your situation. A router over the skills in this repo. |
| engineering/aspnet-core | Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades. |
| engineering/backend-development | Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems. |
| engineering/better-auth | Implement authentication and authorization with Better Auth - a framework-agnostic TypeScript authentication framework. Features include email/password authentication with verification, OAuth providers (Google, GitHub, Discord, etc.), two-factor authentication (TOTP, SMS), passkeys/WebAuthn support, session management, role-based access control (RBAC), rate limiting, and database adapters. Use when adding authentication to applications, implementing OAuth flows, setting up 2FA/MFA, managing user sessions, configuring authorization rules, or building secure authentication systems for web applications. |
| engineering/clean-code | Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments |
| engineering/code-agent-patterns | Use when building autonomous code editing, bug fixing, or software engineering agents. Keywords: SWE-agent, code agent, bug localization, patch generation, AST, diff, TDD loop, repository indexing. |
| engineering/code-review | Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims. |
| engineering/code-review-checklist | Code review guidelines covering code quality, security, and best practices. |
| engineering/codebase-design | Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary. |
| engineering/context-engineering | Master context engineering for AI agent systems. Use when designing agent architectures, debugging context failures, optimizing token usage, implementing memory systems, building multi-agent coordination, evaluating agent performance, or developing LLM-powered pipelines. Covers context fundamentals, degradation patterns, optimization techniques (compaction, masking, caching), compression strategies, memory architectures, multi-agent patterns, LLM-as-Judge evaluation, tool design, and project development. |
| engineering/context-optimization | Use when optimizing token usage, KV cache efficiency, or context window management for LLM agents. Keywords: context optimization, KV cache, prompt caching, token budget, semantic pruning, lost-in-the-middle. |
| engineering/database-design | Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases. |
| engineering/databases | Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases. |
| engineering/diagnose | Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression. |
| engineering/diagnosing-bugs | Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow. |
| engineering/docs-seeker | Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel |
| engineering/domain-modeling | Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR. |
| engineering/frontend-development | Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code. |
| engineering/graph-rag | Use when needing global or relational understanding of codebases or knowledge corpora. Keywords: GraphRAG, knowledge graph, entity extraction, community summarization, graph traversal, Microsoft GraphRAG. |
| engineering/i18n-localization | Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support. |
| engineering/implement | Implement a piece of work based on a spec or set of tickets. |
| engineering/improve-codebase-architecture | Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable. |
| engineering/lint-and-validate | Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis. |
| engineering/llm-evals | Use when validating, benchmarking, or monitoring LLM application performance. Keywords: RAG evaluation, LLM-as-a-judge, CI/CD gating, trajectory scoring, test suites, prompt quality. |
| engineering/nextjs-best-practices | Next.js App Router principles. Server Components, data fetching, routing patterns. |
| engineering/nodejs-best-practices | Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying. |
| engineering/openai-docs | Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations, help choosing the latest model for a use case, or explicit GPT-5.4 upgrade and prompt-upgrade guidance; prioritize OpenAI docs MCP tools, use bundled references only as helper context, and restrict any fallback browsing to official OpenAI domains. |
| engineering/performance-profiling | Performance profiling principles. Measurement, analysis, and optimization techniques. |
| engineering/playwright | Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script. |
| engineering/playwright-interactive | Persistent browser and Electron interaction through `js_repl` for fast iterative UI debugging. |
| engineering/prompt-engineering | Use when designing, optimizing, testing, or deploying robust prompt systems for AI agents. This skill provides frameworks for structured prompt engineering, meta-prompting, and automated optimization workflows. |
| engineering/prototype | Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like. |
| engineering/python-patterns | Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying. |
| engineering/react-patterns | Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices. |
| engineering/render-deploy | Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform. |
| engineering/repomix | Package entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases. |
| engineering/research | Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent. |
| engineering/resolving-merge-conflicts | Use when you need to resolve an in-progress git merge/rebase conflict. |
| engineering/setup-matt-pocock-skills | Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs. |
| engineering/shopify | Build Shopify applications, extensions, and themes using GraphQL/REST APIs, Shopify CLI, Polaris UI components, and Liquid templating. Capabilities include app development with OAuth authentication, checkout UI extensions for customizing checkout flow, admin UI extensions for dashboard integration, POS extensions for retail, theme development with Liquid, webhook management, billing API integration, product/order/customer management. Use when building Shopify apps, implementing checkout customizations, creating admin interfaces, developing themes, integrating payment processing, managing store data via APIs, or extending Shopify functionality. |
| engineering/structured-outputs | Use when needing 100% type-safe, schema-valid data extraction from LLMs. Keywords: structured output, JSON schema, Pydantic, Zod, type-safe, constrained decoding, validation, tool use. |
| engineering/tdd | Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development. |
| engineering/tdd-workflow | Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle. |
| engineering/testing-patterns | Testing patterns and principles. Unit, integration, mocking strategies. |
| engineering/to-issues | Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues. |
| engineering/to-prd | Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context. |
| engineering/to-spec | Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed. |
| engineering/to-tickets | Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker). |
| engineering/triage | Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs. |
| engineering/vulnerability-scanner | Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization. |
| engineering/wayfinder | Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear. |
| engineering/web-frameworks | Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons in outlined/filled styles). Use when creating React applications, implementing server-side rendering, setting up monorepos with multiple packages, optimizing build performance and caching strategies, adding icon libraries, managing shared dependencies, or working with TypeScript full-stack projects. |
| engineering/webapp-testing | Web application testing principles. E2E, Playwright, deep audit strategies. |
| engineering/wizard | Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself. |
| engineering/write-a-skill | Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill. |
| games/2d-games | 2D game development principles. Sprites, tilemaps, physics, camera. |
| games/3d-games | 3D game development principles. Rendering, shaders, physics, cameras. |
| games/game-art | Game art principles. Visual style selection, asset pipeline, animation workflow. |
| games/game-audio | Game audio principles. Sound design, music integration, adaptive audio systems. |
| games/game-design | Game design principles. GDD structure, balancing, player psychology, progression. |
| games/game-development | Game development orchestrator. Routes to platform-specific skills based on project needs. |
| games/game-development/2d-games | 2D game development principles. Sprites, tilemaps, physics, camera. |
| games/game-development/3d-games | 3D game development principles. Rendering, shaders, physics, cameras. |
| games/game-development/game-art | Game art principles. Visual style selection, asset pipeline, animation workflow. |
| games/game-development/game-audio | Game audio principles. Sound design, music integration, adaptive audio systems. |
| games/game-development/game-design | Game design principles. GDD structure, balancing, player psychology, progression. |
| games/game-development/mobile-games | Mobile game development principles. Touch input, battery, performance, app stores. |
| games/game-development/multiplayer | Multiplayer game development principles. Architecture, networking, synchronization. |
| games/game-development/pc-games | PC and console game development principles. Engine selection, platform features, optimization strategies. |
| games/game-development/vr-ar | VR/AR development principles. Comfort, interaction, performance requirements. |
| games/game-development/web-games | Web browser game development principles. Framework selection, WebGPU, optimization, PWA. |
| games/mobile-games | Mobile game development principles. Touch input, battery, performance, app stores. |
| games/multiplayer | Multiplayer game development principles. Architecture, networking, synchronization. |
| games/pc-games | PC and console game development principles. Engine selection, platform features, optimization strategies. |
| games/vr-ar | VR/AR development principles. Comfort, interaction, performance requirements. |
| games/web-games | Web browser game development principles. Framework selection, WebGPU, optimization, PWA. |
| grounded-research-benchmark | Perform triangulated cognitive research combining SQLite memory, GitHub 10k+ stars patterns, and ToT DAG benchmarking before critical architectural decisions. Automatically triggers subagent research escalation when confidence is low (<0.70). Keywords: research, benchmark, github, memory, triangulation, grounding, best-practices, escalation |
| kilo-kit | Core Kilo-Kit skill enforcing Hard-Gate and Iron Law principles. Ensures AI agents scan the system and codebase before proposing solutions. Keywords: hard-gate, iron-law, evidence, scan, verify, system-check, codebase |
| kilo-kit/_template | Template for creating new Kilo-Kit skills. Copy this folder and customize for your skill. Keywords: template, new, create, skill |
| kilo-kit/debugging/root-cause | Deep root cause analysis using the 5 Whys and Fishbone techniques. Use when systematic debugging hasn't found the cause, or for complex systemic issues. Keywords: root cause, why, underlying, fundamental, systemic, deep, origin |
| kilo-kit/debugging/systematic | Comprehensive 4-phase debugging methodology for complex bugs. Use for bugs that aren't immediately obvious or have resisted quick fixes. Keywords: bug, error, fix, debug, broken, crash, fail, exception |
| kilo-kit/debugging/verification | Comprehensive fix verification methodology to ensure bugs are truly fixed. Use after implementing any bug fix to verify it works and hasn't caused regressions. Keywords: verify, confirm, test, validate, check, ensure, regression, fixed |
| kilo-kit/development/backend | Comprehensive backend API development skill for building robust, scalable APIs. Use when creating new endpoints, services, or backend functionality. Keywords: API, backend, endpoint, service, REST, GraphQL, server, controller, route |
| kilo-kit/development/security | Security-focused development skill covering OWASP Top 10 and secure coding. Use when implementing authentication, handling user data, or security review. Keywords: security, auth, authentication, authorization, OWASP, XSS, SQL injection, CSRF, secure |
| kilo-kit/quality/code-review | Comprehensive code review checklist and methodology. Use when reviewing PRs, conducting code audits, or assessing code quality. Keywords: review, PR, code review, audit, assess, quality, check |
| kilo-kit/quality/testing | Comprehensive testing skill covering unit, integration, and e2e testing with TDD. Use when writing tests, improving coverage, or setting up testing infrastructure. Keywords: test, TDD, unit test, integration, e2e, coverage, mock, jest, vitest |
| learned/sqlite-triangulation-pattern | Reasoning data lost across agent steps and missing low-confidence fallback Keywords: sqlite, triangulation, escalation, confidence |
| learned/sqlite-wal-optimization | High concurrent SQLite access causing lock contention and missing indexes Keywords: sqlite, wal, indexes, performance |
| operations/agent-observability | Use when monitoring, tracing, or debugging agentic workflows in production. Keywords: observability, tracing, OpenTelemetry, Langfuse, latency, token cost, loop detection, telemetry. |
| operations/bash-linux | Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems. |
| operations/chrome-devtools | Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging. |
| operations/deployment-procedures | Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts. |
| operations/devops | Deploy and manage cloud infrastructure on Cloudflare (Workers, R2, D1, KV, Pages, Durable Objects, Browser Rendering), Docker containers, and Google Cloud Platform (Compute Engine, GKE, Cloud Run, App Engine, Cloud Storage). Use when deploying serverless functions to the edge, configuring edge computing solutions, managing Docker containers and images, setting up CI/CD pipelines, optimizing cloud infrastructure costs, implementing global caching strategies, working with cloud databases, or building cloud-native applications. |
| operations/mcp-builder | Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). |
| operations/mcp-management | Manage Model Context Protocol (MCP) servers - discover, analyze, and execute tools/prompts/resources from configured MCP servers. Use when working with MCP integrations, need to discover available MCP capabilities, filter MCP tools for specific tasks, execute MCP tools programmatically, access MCP prompts/resources, or implement MCP client functionality. Supports intelligent tool selection, multi-server management, and context-efficient capability discovery. |
| operations/powershell-windows | PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling. |
| operations/server-management | Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands. |
| problem-solving/collision-zone-thinking | Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?" |
| problem-solving/defense-in-depth | Validate at every layer data passes through to make bugs impossible |
| problem-solving/inversion-exercise | Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?" |
| problem-solving/meta-pattern-recognition | Spot patterns appearing in 3+ domains to find universal principles |
| problem-solving/root-cause-tracing | Systematically trace bugs backward through call stack to find original trigger |
| problem-solving/scale-game | Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales |
| problem-solving/sequential-thinking | Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope. |
| problem-solving/simplification-cascades | Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z" |
| problem-solving/systematic-debugging | Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes |
| problem-solving/when-stuck | Dispatch to the right problem-solving technique based on how you're stuck |
| productivity/brainstorming | You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. |
| productivity/caveman | Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. |
| productivity/claude-handoff | Hand the current conversation off to a fresh background agent that picks up the work immediately. |
| productivity/dispatching-parallel-agents | Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies |
| productivity/executing-plans | Use when you have a written implementation plan to execute in a separate session with review checkpoints |
| productivity/finishing-a-development-branch | Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup |
| productivity/git-guardrails-claude-code | Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code. |
| productivity/grill-me | Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me". |
| productivity/grill-with-docs | Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions. |
| productivity/grilling | Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases. |
| productivity/handoff | Compact the current conversation into a handoff document for another agent to pick up. |
| productivity/human-in-the-loop | Use when designing human approval gates for high-stakes agent actions. Keywords: human-in-the-loop, HITL, approval gate, checkpoint, confirmation, risk-tiered, action review. |
| productivity/loop-me | Grill me about specs for the workflows I want to build, within this workspace. |
| productivity/migrate-to-shoehorn | Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data. |
| productivity/parallel-agents | Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives. |
| productivity/plan-writing | Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work. |
| productivity/receiving-code-review | Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation |
| productivity/requesting-code-review | Use when completing tasks, implementing major features, or before merging to verify work meets requirements |
| productivity/scaffold-exercises | Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section. |
| productivity/setup-pre-commit | Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing. |
| productivity/setup-ts-deep-modules | Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked. |
| productivity/spec-driven-development | Use when starting a new feature, product, or system design. Eliminates the spec-implementation gap by making specifications the primary artifact that drives code generation. Keywords: SDD, spec-driven, PRD, feature spec, user stories, implementation plan, specification, acceptance criteria, Given-When-Then. |
| productivity/subagent-driven-development | Use when executing implementation plans with independent tasks in the current session |
| productivity/teach | Teach the user a new skill or concept, within this workspace. |
| productivity/test-driven-development | Use when implementing any feature or bugfix, before writing implementation code |
| productivity/to-questionnaire | Turn a decision you can't fully answer into a questionnaire for someone else to fill in. |
| productivity/using-git-worktrees | Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification |
| productivity/using-superpowers | Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions |
| productivity/verification-before-completion | Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always |
| productivity/wait-what | Stop. That last message did not land: re-pitch it. |
| productivity/writing-beats | Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it. |
| productivity/writing-for-agents | Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md. |
| productivity/writing-fragments | Writing, explore: mine raw fragments, no structure yet. |
| productivity/writing-plans | Use when you have a spec or requirements for a multi-step task, before touching code |
| productivity/writing-shape | Writing, exploit: shape raw material into an article, paragraph by paragraph. |
| productivity/writing-skills | Use when creating new skills, editing existing skills, or verifying skills work before deployment |
| productivity/zoom-out | Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture. |
| security/ai-guardrails | Use when building autonomous LLM agents operating in live environments. Protects against prompt injection, tool abuse, data exfiltration, and runaway loops. Keywords: guardrails, prompt injection, IPI, safety, sandboxing, NeMo, LLM Guard. |
| security/red-team-tactics | Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting. |
| writing-docs/behavioral-modes | AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type. |
| writing-docs/doc | Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks. |
| writing-docs/documentation-templates | Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation. |
| writing-docs/docx | Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks |
| writing-docs/mermaidjs-v11 | Create diagrams and visualizations using Mermaid.js v11 syntax. Use when generating flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, Gantt charts, user journeys, timelines, architecture diagrams, or any of 24+ diagram types. Supports JavaScript API integration, CLI rendering to SVG/PNG/PDF, theming, configuration, and accessibility features. Essential for documentation, technical diagrams, project planning, system architecture, and visual communication. |
| writing-docs/pdf | Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale. |
| writing-docs/pptx | Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks |
| writing-docs/slides | Create and edit presentation slide decks (`.pptx`) with PptxGenJS, bundled layout helpers, and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution. |
| writing-docs/template-skill | A template for creating new modular and scalable agent skills. |
| writing-docs/templates | Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks. |
| writing-docs/xlsx | Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas |
TDQS
B3.4/5.0
Scored across 24 tools
Disambiguation3/5
Several tools have overlapping meta-level purposes, especially kilo_orchestrate_task, kilo_route_intent, kilo_search_skills, and kilo_get_skill, which could cause misselection. The descriptions provide useful distinctions, but boundaries between workflow routing, skill discovery, and skill loading remain blurry.
Naming Consistency5/5
All tools follow a consistent snake_case pattern with the same kilo_ prefix. The naming convention is predictable and easy to scan.
Tool Count3/5
At 24 tools, the set is heavy for the server's apparent scope, sitting in the borderline range where each tool does not clearly earn its place. The domain is broad, but consolidation could reduce redundancy.
Completeness4/5
The surface covers skill discovery, loading, validation, synthesis, memory, routing, file operations, command execution, and several reasoning workflows. Minor gaps exist, such as no explicit skill deletion/update or memory fact deletion, but core workflows are well represented.
Maintenance
ActivityMaintained
ResponsivenessResponsive