By indykite
IndyKite skills for coding agents — Agent Gateway deployment, MCP server calls, KBAC authorization policy authoring and lifecycle, AuthZEN decisions and search (single evaluation, batch evaluations, action / resource / subject search), and ContX IQ policies / Knowledge Queries / executes (read, create node, create relationship, combined create-with-link, add property, add relationship property, delete).
Deploy and configure IndyKite Agent Gateway (IAG) in front of agent-to-agent (A2A) workflows. Use when wiring up A2A policy enforcement, modeling workflows in the IKG, or debugging IAG 401/403 responses.
Call the IndyKite MCP server to make AuthZEN authorization decisions and execute ContX IQ Knowledge Queries. Use when initializing an MCP session, calling its tools, configuring an MCP server, or debugging its two-layer auth.
Author and manage an IndyKite KBAC (Knowledge-Based Access Control) authorization policy - a single subject type, an actions list, a single resource type, and a Cypher condition over the IKG - through the Config API (`/configs/v1/authorization-policies` - create / read / list `?type=kbac` / update / delete, ETag-guarded). Use when the user wants to write, publish, inspect, change the status of, update, or delete a `2.0-kbac` policy - e.g. "write a policy letting a Person PROVISION a Server within budget and publish it", "list the active KBAC policies", "deactivate this policy". This authors the rule; it does NOT make decisions - for "can X do Y on Z?" use indykite-authzen-evaluation (single) or indykite-authzen-evaluations (batch), and to enumerate allowed actions/resources/subjects use indykite-authzen-search-action / -search-resource / -search-subject. This is KBAC, not ContX IQ - for CIQ read/write data policies use the indykite-ciq-* skills.
Make a single KBAC authorization decision via the IndyKite AuthZEN REST API (`POST /access/v1/evaluation`) - returns a boolean `decision` for one (subject, action, resource) triple, optionally with per-request `context.input_params`. Use for a single yes/no question - "can ada PROVISION gpu-node-7?", "is this user allowed to delete this document?", "gate this operation on a live check", or debugging why one decision is false. Not for many checks at once (use indykite-authzen-evaluations), not for enumerating which actions/resources/subjects are allowed (use indykite-authzen-search-action / -search-resource / -search-subject), and not for authoring the policy behind the decision (use indykite-authzen-kbac). For the same decision over MCP/JSON-RPC see indykite-mcp-server (`authzen_evaluate`).
Run many KBAC authorization decisions in one call via the IndyKite AuthZEN REST API (`POST /access/v1/evaluations`), with top-level subject/action/resource/context as defaults overridden per entry; returns one `decision` per entry, in order. Use when checking a known, fixed set of checks at once - one subject against many resources, one action across many subjects, or any mix of triples - e.g. "of these servers, which can grace provision?", "for each of these users, can they deploy gpu-node-7?". For a single check use indykite-authzen-evaluation; to enumerate ALL allowed actions/resources/subjects (open-ended, not a fixed list) use indykite-authzen-search-action / -search-resource / -search-subject; to author the policy use indykite-authzen-kbac.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This plugin requires configuration values that are prompted when the plugin is enabled. Sensitive values are stored in your system keychain.
API_KEYAppAgent credentials token. Goes into the X-IK-ClientKey header on every CIQ / MCP call. Mint via POST /configs/v1/application-agent-credentials.
${user_config.API_KEY}API_URLIndyKite REST API base URL for the project's region (e.g. https://us.api.indykite.com or https://eu.api.indykite.com).
${user_config.API_URL}MCP_URLIndyKite MCP server base URL for the project's region (e.g. https://us.mcp.indykite.com or https://eu.mcp.indykite.com). Required only when using the indykite-mcp-server skill.
${user_config.MCP_URL}PROJECT_GIDIndyKite project identifier. Visible in the Hub UI on the project settings page; required by indykite-mcp-server for the URL path.
${user_config.PROJECT_GID}BEARER_TOKENUser OAuth access token. Required for Person-subject CIQ flows and for MCP session initialisation; omit for _Application-subject flows.
${user_config.BEARER_TOKEN}SERVICE_ACCOUNT_TOKENToken with Config API write access. Used to create CIQ policies and Knowledge Queries (POST /configs/v1/authorization-policies and POST /configs/v1/knowledge-queries). Not required to execute existing Knowledge Queries.
${user_config.SERVICE_ACCOUNT_TOKEN}A collection of skills for coding agents that work with IndyKite — graph-based identity, authorization, and AI-agent integration.
A skill is a self-contained bundle of instructions (and optionally scripts, references, or assets) that an agent loads on demand to perform a specialized task.
Acronyms used throughout the skills, defined once here.
openapi.indykite.com; docs at developer.indykite.com.POST /contx-iq/v1/execute.authzen_evaluate).Each row is one skill — what it does and a representative prompt it's designed to handle. Activation isn't guaranteed: which skill actually fires depends on the agent's matching algorithm, the model, and what else is installed. Verify routing in your own setup before relying on it.
| Skill | What it does | Example prompt |
|---|---|---|
indykite-agent-gateway | Deploy and configure IAG in front of A2A agents to enforce caller, workflow, and delegation-chain checks. | "Deploy IAG in front of my three A2A agents and wire up the workflow in the IKG." |
indykite-mcp-server | Call the IndyKite MCP server (initialize session, list tools, call AuthZEN and CIQ tools) and configure the MCP endpoint for a project. | "How do I initialise an MCP session against eu.mcp.indykite.com and call authzen_evaluate?" |
indykite-authzen-kbac | Author and manage a KBAC authorization policy (subject, actions, resource, Cypher condition) through the Config API — create, read, list ?type=kbac, update, delete. The home of KBAC policy authoring. | "Write a policy letting a Person PROVISION a Server when its cost is within a budget, and publish it." |
indykite-authzen-evaluation | Make a single KBAC decision via the AuthZEN REST API (POST /access/v1/evaluation) — one yes/no answer for a (subject, action, resource) triple. | "Can ada PROVISION the server gpu-node-7 with a budget of 120000?" |
indykite-authzen-evaluations | Run many KBAC decisions in one call (POST /access/v1/evaluations) with top-level defaults overridden per entry. | "Of these servers, which can grace provision with a budget of 80000?" |
indykite-authzen-search-action | List the actions a subject may perform on a resource (POST /access/v1/search/action). | "What can linus do with the server gpu-node-7?" |
indykite-authzen-search-resource | List the resources a subject may act on, given an action (POST /access/v1/search/resource). | "Which servers can linus provision with a budget of 4000?" |
indykite-authzen-search-subject | List the subjects allowed an action on a resource (POST /access/v1/search/subject). | "Who can provision the server gpu-node-7 with a budget of 80000?" |
indykite-ciq-read | Author a read-only CIQ policy and Knowledge Query, then run it via POST /contx-iq/v1/execute. | "Expose Person-OWNS-Car as a parameterised read query through ContX IQ." |
indykite-ciq-create-node | Author a CIQ policy + Knowledge Query that creates a brand-new node in the IKG. | "Create a new Track node in the IKG with title and loudness, via CIQ." |
npx claudepluginhub indykite/skills --plugin indykite-skillsComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
UI/UX design intelligence. 67 styles, 161 palettes, 57 font pairings, 25 charts, 15 stacks (React, Next.js, Vue, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Nuxt, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.