This repository is the central library for all AI prompts and agent configurations used across the organization. Its purpose is to foster collaboration, maintain high standards, and accelerate our work by sharing effective and well-tested prompts and specialized agents.
Install skills using skills tool: npx skills add keboola/ai-kit
Alternatively, install via the Claude Code plugin marketplace:
/plugin marketplace add keboola/claude-kitAfter installation, enable the plugins you need:
/plugin install developerThe repository is organized into a plugin-based architecture to make prompts and agents easy to discover and use:
claude-kit/
├── .claude-plugin/
│ └── marketplace.json # Marketplace configuration
├── plugins/
│ ├── developer/ # Developer toolkit plugin
│ ├── component-developer/ # Keboola Python component development
│ ├── dataapp-developer/ # Streamlit data apps for Keboola
│ ├── incident-commander/ # Post-mortem creation from Slack
│ └── keboola-cli/ # Keboola project management and review
├── README.md # This file
└── LICENSE # MIT license
Location: ./plugins/developer
A comprehensive toolkit for developers including specialized agents for code review, security analysis, code quality management, and workflow automation.
Features:
- 🤖 Agents: Code review, security analysis, code mess detection & fixing
- ⚡ Commands: Task management, PR creation, merge conflict resolution, GitHub PR review processing
- 📊 Scripts: Context window progress bar for statusline
- 🔌 MCP Server: Linear integration
→ View Developer Plugin Documentation
Location: ./plugins/component-developer
A specialized toolkit for building production-ready Keboola Python components following best practices and architectural patterns.
Features:
- 🎯 Skills: Build component, build UI, debug, test, review, migrate to UV, getting started
- ⚡ Commands: Init, run, fix, review, migrate-repo, schema-test
- 🔌 MCP Server: Keboola integration
- 📋 Configuration Schemas: JSON Schema with UI elements
- 🚀 CI/CD Integration: Developer Portal and deployment workflows
→ View Component Developer Plugin Documentation
Location: ./plugins/dataapp-developer
A specialized toolkit for building production-ready Streamlit data apps for Keboola deployment with a systematic validate → build → verify workflow.
Features:
- 🎯 Skills: Data app development with validate → build → verify workflow
- 🔍 Data Validation: Automatic schema checking using Keboola MCP
- 🎨 Visual Verification: Browser testing with Playwright MCP
- 🏗️ SQL-First Architecture: Best practices for scalable data apps
- 📚 Comprehensive Docs: Quickstart, workflows, templates, and checklists
- 🛡️ Bug Prevention: Catches common issues before they become problems
- 🔌 MCP Servers: Keboola (remote HTTP) and Playwright (browser automation)
→ View Data App Developer Plugin Documentation
Location: ./plugins/incident-commander
A specialized toolkit for incident response, helping incident commanders create comprehensive post-mortem documents from Slack incident channels.
Features:
- Commands: Post-mortem creation from Slack incident channels
- Confluence Integration: Reads templates and creates structured documents
- Slack Integration: Gathers incident information from channels and threads
- Structured Output: Overview, Impact, Timeline, Action Items, and more
- Blameless Format: Focuses on systems and processes, not individuals
→ View Incident Commander Plugin Documentation
Location: ./plugins/keboola-cli
A project management and review toolkit for Keboola projects. Includes CLI sync commands and a 10-agent review team that audits SQL quality, security, performance, financial logic, data quality, and template readiness.
Features:
- 🤖 Agents: 10 specialized review agents (SQL, Config, DWH Architecture, Data Quality, Financial Logic, Semantic Layer, Security, Performance, Template Readiness, Consolidator) + config analyzer
- ⚡ Commands:
/kbc-init,/kbc-pull,/kbc-push,/kbc-diff,/kbc-review - 🔌 MCP Server: Keboola integration for live project analysis
- 📊 Financial Intelligence: Multi-ERP awareness (NetSuite, SAP, Oracle, D365, QuickBooks, Xero), SaaS metrics, budget variance
- 🔒 Security Audit: Credential scanning, PII detection, GDPR/CCPA compliance checks
→ View Keboola CLI Plugin Documentation
Some commands and plugins require MCP (Model Context Protocol) servers to be configured. If MCP tools are not available when running a command, use the /mcp command to authenticate and configure them.
Required for commands like /create-postmortem that interact with Confluence.
claude mcp add --transport sse atlassian https://mcp.atlassian.com/v1/sseAfter adding the MCP server, run /mcp to authenticate with your Atlassian account.
Required for commands like /create-postmortem that read incident information from Slack channels.
Step 1: Get Slack Tokens from Browser
You need two tokens from your Slack workspace:
- XOXC token: User token for API access
- XOXD token: Cookie token for authentication
To extract these tokens:
- Open your Slack workspace in a web browser (not the desktop app)
- Open Developer Tools (F12 or Right-click → Inspect)
- Go to the Application tab (Chrome) or Storage tab (Firefox)
- In the left sidebar, expand Cookies and select your Slack workspace URL
- Find the cookie named
d- its value is your XOXD token (starts withxoxd-) - Go to the Console tab and run:
localStorage.getItem('localConfig_v2') - In the output, find the
teamsobject and look fortoken- this is your XOXC token (starts withxoxc-)
Step 2: Add Slack MCP Server
claude mcp add --transport stdio slack-mcp-server \
--env SLACK_MCP_XOXC_TOKEN=<SLACK_MCP_XOXC_TOKEN> \
--env SLACK_MCP_XOXD_TOKEN=<SLACK_MCP_XOXD_TOKEN> \
-- npx -y slack-mcp-serverReplace <SLACK_MCP_XOXC_TOKEN> and <SLACK_MCP_XOXD_TOKEN> with your actual tokens from Step 1.
Step 3: Verify Setup
Run /mcp to verify the Slack MCP server is working and you can access your workspace channels.
If you encounter "MCP tools not available" errors:
- Run
/mcpto see available MCP servers and their status - Authenticate with the required MCP server
- Re-run your command
Always validate your changes before committing:
claude plugin validate .Test agents and commands locally:
# Test an agent
@agent-name
# Test a command
/command-nameWe follow semantic versioning. Update version numbers in:
.claude-plugin/marketplace.jsonplugins/<name>/.claude-plugin/plugin.jsonplugins/<name>/README.md
MIT licensed, see LICENSE file.