{ "version": 1, "instructions": "这是公开索引，只有名字和一句说明。Skill 正文不在这个 URL。", "count": 80, "skills": [ { "name": "api-design", "title": "API Design Patterns", "description": "This skill should be used when the user asks about \"REST API设计\", \"接口命名\", \"HTTP状态码\", \"分页设计\", \"API版本控制\", \"限流设计\", or needs REST API design patterns for production APIs." }, { "name": "backend-patterns", "title": "Backend Development Patterns", "description": "This skill should be used when the user asks about \"后端架构\", \"API设计\", \"数据库优化\", \"Node.js patterns\", \"Express\", \"Next.js API routes\", or needs backend architecture patterns." }, { "name": "cf-domain-management", "title": "Cloudflare 域名管理", "description": "This skill should be used when the user asks to \"Cloudflare域名管理\", \"CF域名\", \"Cloudflare DNS\", \"Cloudflare Tunnel\", \"CF账号管理\", \"DNS管理\", \"防止域名被举报\", \"域名治理\", \"Cloudflare WAF\", or needs KT-specific domain governance, DNS operations, Tunnel routing, Cloudflare account management, and outward-facing domain planning." }, { "name": "cli-product-engineering", "title": "CLI Product Engineering", "description": "This skill should be used when the user asks to \"设计 CLI\", \"开发 CLI\", \"企业级 CLI 规范\", \"CLI 升级功能\", \"self update\", \"check-update\", \"命令行 help\", \"远程登录轮询\", \"device code\", \"release manifest\", or needs a reusable engineering standard for command-line products." }, { "name": "clickhouse-io", "title": "ClickHouse Analytics Patterns", "description": "This skill should be used when the user asks about \"ClickHouse查询\", \"分析型数据库\", \"OLAP\", \"ClickHouse优化\", or needs ClickHouse database patterns and analytics best practices." }, { "name": "coding-standards", "title": "KT 团队编码规范与语言选择", "description": "This skill should be used when the user asks about \"代码规范\", \"语言选择\", \"用什么语言写\", \"选Go还是Python\", \"新服务用什么写\", \"TypeScript规范\", \"JavaScript最佳实践\", \"React规范\", \"coding standards\", or needs universal coding standards, language selection guidance, and best practices for KT team development." }, { "name": "continuous-learning", "title": "Continuous Learning Skill", "description": "This skill should be used when the user asks to review learned patterns, curate extracted skills, tune session-end learning behavior, or manage reusable insights captured from Claude Code sessions." }, { "name": "cpp-testing", "title": "C++ Testing (Agent Skill)", "description": "This skill should be used when the user asks to \"写C++测试\", \"配置GoogleTest\", \"CTest\", \"C++覆盖率\", \"sanitizer\", or needs guidance on writing or fixing C++ tests." }, { "name": "database-migrations", "title": "Database Migration Patterns", "description": "This skill should be used when the user asks to \"数据库迁移\", \"schema变更\", \"migration回滚\", \"zero-downtime migration\", \"Prisma迁移\", \"Django migrations\", or needs database migration best practices." }, { "name": "deployment-patterns", "title": "Deployment Patterns", "description": "This skill should be used when the user asks to \"CI/CD流程\", \"Docker部署\", \"健康检查\", \"回滚策略\", \"发布流程\", or needs deployment workflow patterns and production readiness checklists." }, { "name": "django-patterns", "title": "Django Development Patterns", "description": "This skill should be used when the user asks about \"Django架构\", \"DRF设计\", \"Django ORM\", \"Django缓存\", \"Django信号\", or needs Django architecture patterns and REST API design." }, { "name": "django-security", "title": "Django Security Best Practices", "description": "This skill should be used when the user asks about \"Django安全\", \"CSRF防护\", \"SQL注入防护\", \"Django认证\", \"Django权限\", or needs Django security best practices." }, { "name": "django-tdd", "title": "Django Testing with TDD", "description": "This skill should be used when the user asks to \"Django测试\", \"pytest-django\", \"factory_boy\", \"DRF测试\", \"Django覆盖率\", or needs Django testing strategies and TDD methodology." }, { "name": "django-verification", "title": "Django Verification Loop", "description": "This skill should be used when the user asks to \"验证Django项目\", \"Django发布前检查\", \"Django lint\", \"Django安全扫描\", or needs a verification loop for Django projects before release or PR." }, { "name": "docker-patterns", "title": "Docker Patterns", "description": "This skill should be used when the user asks about \"Docker开发环境\", \"Docker安全\", \"Docker网络\", \"Docker Compose\", \"容器编排\", or needs Docker and Docker Compose patterns." }, { "name": "e2e-testing", "title": "E2E Testing Patterns", "description": "This skill should be used when the user asks to \"Playwright测试\", \"E2E测试\", \"Page Object Model\", \"端到端测试\", \"CI集成测试\", or needs Playwright E2E testing patterns." }, { "name": "existing-service-reuse", "title": "既有服务优先复用", "description": "This skill should be used when the user asks to \"复用已有服务\", \"不要重复造轮子\", \"利用已有服务\", \"接到现有系统\", \"看看能不能复用\", \"先用现有服务\", or needs architecture/design guidance that prefers existing KT services, gateways, buses, and control planes over building parallel implementations." }, { "name": "git-governance", "title": "Git Governance", "description": "This skill should be used when the user asks to \"Git 管理规范\", \"分支保护\", \"branch protection\", \"main 分支保护\", \"禁止直接提交 main\", \"PR/MR workflow\", \"merge policy\", \"release branch policy\", \"hotfix 流程\", or needs guidance on safe repository, branch, commit, merge, and release governance." }, { "name": "golang-patterns", "title": "Go Development Patterns", "description": "This skill should be used when the user asks about \"Go语言规范\", \"Go最佳实践\", \"idiomatic Go\", \"Go并发\", \"Go错误处理\", or needs idiomatic Go patterns and conventions." }, { "name": "golang-testing", "title": "Go Testing Patterns", "description": "This skill should be used when the user asks to \"Go测试\", \"table-driven test\", \"Go基准测试\", \"Go fuzz测试\", \"Go覆盖率\", or needs Go testing patterns and TDD methodology." }, { "name": "infisical-credential-access", "title": "Infisical Credential Access", "description": "This skill should be used when the user asks to access private GitHub resources, GitHub issues/PRs, API keys, service tokens, Cloudflare credentials, Kubernetes credentials, Infisical, secrets, or any operation that needs non-public credentials. It standardizes KT credential retrieval through Infisical, safe secret handling, and what to do when a user pastes secrets in chat." }, { "name": "iterative-retrieval", "title": "Iterative Retrieval Pattern", "description": "This skill should be used when the user asks to improve subagent context, debug missing context in agent tasks, or progressively retrieve codebase information for multi-agent workflows." }, { "name": "java-coding-standards", "title": "Java Coding Standards", "description": "This skill should be used when the user asks about \"Java代码规范\", \"Spring Boot命名规范\", \"Java不可变对象\", \"Optional用法\", \"Java异常处理\", or needs Java coding standards for Spring Boot services." }, { "name": "jpa-patterns", "title": "JPA/Hibernate Patterns", "description": "This skill should be used when the user asks about \"JPA实体设计\", \"Hibernate关系\", \"JPA查询优化\", \"JPA事务\", \"JPA分页\", or needs JPA/Hibernate patterns for Spring Boot." }, { "name": "k8s-resource-check", "title": "K8S 部署前后资源检查", "description": "Use this skill BEFORE deploying any new workload to K3S cluster. Checks node CPU/memory headroom, disk space, and whether the new workload can be safely scheduled without risking OOM or eviction. Also used AFTER deployment to confirm resource consumption is normal. Trigger phrases: \"部署前检查\", \"资源够吗\", \"会不会把系统搞挂\", check resources before deploy\", \"resource check\", \"节点资源\"." }, { "name": "kafka-event-driven-architecture", "title": "Kafka 事件驱动架构", "description": "This skill should be used when the user asks about Kafka, \"事件驱动架构\", \"消息队列\", \"event driven\", \"kafka producer consumer\", kt-agent Kafka message bus, topic design, consumer group isolation, troubleshooting, or deploying Kafka services." }, { "name": "kt-ack-acr-image-pull-management", "title": "KT ACK ACR Image Pull Management（Legacy）", "description": "Legacy-only skill for explicit Alibaba Cloud ACR incidents in KT ACK, such as \"ACR 401\", \"阿里云镜像仓库\", \"ACR token 过期\", \"managed-aliyun-acr-credential-helper\", or known legacy ACR imagePullSecrets. For new KT ACK image delivery or generic ImagePullBackOff, use kt-ack-ghcr-image-pull-management." }, { "name": "kt-ack-argocd-gitops-deploy", "title": "KTAI ACK Argo CD / GitOps Deployments", "description": "Use when working with KTAI ACK/Argo CD/GitOps deployments, kt-platform/kt-cluster-apps, Argo CD Application/ApplicationSet registration, or migrating GitHub Actions kubectl deployments to Argo CD." }, { "name": "kt-ack-ghcr-image-pull-management", "title": "KT ACK GHCR Image Pull Management", "description": "用于 KT ACK 集群里的 GHCR / GitHub Container Registry 镜像交付、ImagePullBackOff、ErrImagePull、401 Unauthorized、ghcr-pull-secret、GitHub Actions packages 权限、以及从 ACR 迁移到 GHCR 的企业级治理。" }, { "name": "kt-ack-ops", "title": "KT ACK Ops (kt-ack-ops)", "description": "This skill should be used when the user asks to manage Aliyun ACK operations for kt-k8s-aliyun, including kubeconfig generation, kubectl access, deployment troubleshooting, logs, scaling, permissions, or ACK cluster debugging." }, { "name": "kt-admin-api", "title": "KT Admin API", "description": "用于 KT Admin API、kt-admin-api-go、旧 Python 管理后台 API 迁移、Bus 兼容层、安全治理、RDS PostgreSQL、GHCR 镜像与 ACK/GitOps 部署相关工作。用户提到 admin api、管理后台 API、Bus 兼容、Python 管理后台迁移到 Go、kt-admin-api-go 时使用。" }, { "name": "kt-ai-transalte", "title": "kt-ai-translate 生产部署手册", "description": "This skill should be used when the user asks to \"deploy kt-ai-translate\", update kt-ai-translate\", \"redeploy ai translate\", \"roll out kt-ai-translate\", rollback kt-ai-translate\", \"replace kt-ai-translate binary\", \"check kt-ai-translate logs\", 部署 kt-ai-translate\", \"更新翻译服务\", \"重新部署 AI 翻译\", \"回滚翻译服务\", or needs to manage the kt-ai-translate production service on the KT infrastructure." }, { "name": "kt-api", "title": "KT API 核心后端服务", "description": "This skill should be used when the user asks about \"kt-api\", \"KTwww\", \"KTapi\", \"kt用户注册\", \"kt后端\", \"kt业务服务\", \"用户注册接口\", \"Bus.py\", \"消息总线\", \"busclient\", or needs to understand the KT core backend service architecture, user registration flow, or Bus event system." }, { "name": "kt-audio-api", "title": "kt-audio-api Groq Key 管理", "description": "This skill should be used when the user asks to \"添加 Groq key\", \"新增语音识别密钥\", \"groq 限流了加 key\", \"groq key 不够用\", \"音频识别配额不足\", \"扩充 groq 免费额度\", or needs to add/rotate Groq API keys for the kt-audio-api-v1 service." }, { "name": "kt-bug-report", "title": "kt-bug-report 服务部署", "description": "This skill should be used when the user asks to \"deploy kt-bug-report\", \"update bug report service\", \"redeploy bug report\", \"rollback bug report\", or needs to manage the kt-bug-report production service on the KT infrastructure." }, { "name": "kt-cli-infisical-bootstrap", "title": "KT CLI Infisical Bootstrap", "description": "用于用户要求“用 KT 命令配置 Infisical”、“kt infisical setup”、“KT CLI 登录后下发 Infisical”、“在 Codex/Agent 环境里配置 Infisical”、“远程登录后配置凭据环境”或需要先通过 KT 账号体系完成 Infisical 本地 bootstrap 时使用。该 skill 只负责登录、下发、写入和验证 Infisical 本地配置；具体读取业务 secret 时再联动 infisical-credential-access。" }, { "name": "kt-cli-runtime-delivery", "title": "KT CLI Runtime Delivery", "description": "用于用户要求交付 KT CLI 子命令 runtime、把子命令接到 ACK 服务、配置 Cloudflare Tunnel 入口、接入 KT Authentication、联动发布产物/manifest、验证 CLI 默认 endpoint，或排查 ktcli.com runtime 域名/Tunnel/GitOps/KT bearer token 链路时使用。" }, { "name": "kt-cloud-database-management", "title": "KT Cloud Database Management", "description": "Use when planning, deploying, migrating, or troubleshooting KT production/staging databases on Alibaba Cloud. Enforces the KT rule that production databases use managed SaaS databases such as Alibaba Cloud RDS/PolarDB for MySQL or PostgreSQL, not in-cluster MySQL/PostgreSQL Pods, PVC-backed demo databases, or ad-hoc self-hosted databases." }, { "name": "kt-desktop-client-testing", "title": "KT Desktop Client Testing Workflow", "description": "This skill should be used when the user asks to \"test kt-desktop client\", \"KT客户端测试\", \"kt-desktop自动化测试\", \"客户端冒烟测试\", \"validate kt-desktop login\", \"test desktop AI translation\", \"CDP 9223 desktop testing\", or needs to validate the KT Electron desktop client login, WebView IPC, translation UI, or AI workflow translation path." }, { "name": "kt-fans-api", "title": "KT Fans API", "description": "用于 KT Fans API、接粉服务、重粉检测、工单粉丝数核查、粉丝导入/回调、kt-fans-api 迁移、日志排查和生产数据核对。用户提到接粉、重粉、fans_count、kt_fans_task、WhatsApp/TG 好友统计或 kt-fans-api 时使用。" }, { "name": "kt-feishu-todos", "title": "KT Feishu Todos", "description": "This skill should be used when the user asks to 查询飞书待办事项, 查看飞书 Base 待办, 查看待办事项, 查询任务列表, 查询KT任务, or mentions the KT Feishu Base URL rcn3g1g7x9et.feishu.cn/base/A0E8b63Raa9X5bsxbebcIYaNnpb. It standardizes how to use the preconfigured lark-cli app credentials and known Base/table/view IDs to read the KT todo list safely." }, { "name": "kt-growth-fission", "title": "KT Growth Fission", "description": "This skill should be used when the user asks about \"裂变\", \"返佣\", \"邀请机制\", \"邀请码\", \"多级返佣\", \"转介绍\", \"团队裂变\", \"线上裂变\", \"线下裂变\", \"增长飞轮中的裂变环节\", or wants to find or use the `kt/growth/fission-design` repository." }, { "name": "kt-infra-memory", "title": "KT 基础设施记忆系统", "description": "This skill should be used when the user asks about \"服务器关系\", \"域名和服务关系\", 生产拓扑\", \"Zep 记忆\", \"infra memory\", \"图谱记忆\", \"域名走向\", \"端口对应服务\", 仓库和服务关系\", \"查一下服务器\", \"服务器IP\", or needs an agentic workflow for querying and updating KT infrastructure facts in Zep Cloud." }, { "name": "kt-infra-overview", "title": "KT 基础设施仓库全景", "description": "Use this skill when working on KT infrastructure operations, routing config, nginx/Istio, cluster management, observability, database ops, or any infra-level change. Provides the map of KT's infrastructure repository ecosystem so AI knows exactly which repo to read/write for any infra task. Trigger phrases: \"基础设施\", \"infra\", \"运维仓库\", \"路由配置\", \"nginx\", \"istio\", 集群管理\", \"kt-platform\", \"可观测性\", \"监控\", \"告警\", \"数据库运维\", \"服务器台账\", 边缘接入\", \"dns\", \"tunnel\", \"改路由\", \"加域名\", \"新增服务接入\", runner配置\", \"sidekiq\", \"helm values\", \"运维留痕\"." }, { "name": "kt-legacy-admin-ktpay-integration", "title": "KT 老后台 KTPay 集成手册", "description": "This skill should be used when the user asks about \"kt8899 后台支付\", \"老后台 KTPay\", ktpay 集成到 kt8899\", \"老后台微信支付在哪改\", \"老后台支付宝支付在哪改\", bc-pay-callback-service 是干嘛的\", \"kt-admin-web 的 ktpay\", or needs to understand the legacy KT admin KTPay integration on `kt8899.org` instead of the standalone kt-pay or new-api flow." }, { "name": "kt-mail", "title": "KT 自建邮箱服务器管理", "description": "This skill should be used when the user asks to \"添加新域名到邮箱服务器\", \"为邮箱添加域\", \"新增邮箱域名\", \"邮箱域名配置\", \"添加域到Mailcow\", \"配置邮箱DNS\", \"创建域管理员\", \"重置邮箱密码\", \"批量清理邮箱\", or needs to manage the KT self-hosted Mailcow email server." }, { "name": "kt-mysql-check", "title": "KT MySQL 状态检查", "description": "检查 KT 旧 MySQL 主从/备份状态。用于迁移前盘点或旧系统运维；生产新部署仍应优先迁移到阿里云托管 RDS/PolarDB，不把 MySQL 长期跑在 ACK Pod/PVC 中。" }, { "name": "kt-pay-service", "title": "bc-pay-callback-v1 (kt-pay-service) 部署与回滚", "description": "This skill should be used when the user asks to \"deploy kt-pay-service\", \"update bc-pay-callback\", \"roll out bc-pay-callback-v1\", \"rebuild bc-pay-callback container\", \"fix bc-pay-callback fiat routes\", or needs to update the bc-pay-callback-v1 Docker service on production." }, { "name": "kt-platform-plugin-development", "title": "KT Platform Plugin Development", "description": "This skill should be used when the user asks to \"add a new platform plugin\", \"support X\", \"support Twitter\", \"integrate a new social platform\", \"add DM support for a platform\", \"add feed/comment support for a platform\", or \"extend kt-plugin to a new site\". It standardizes how to analyze `_pluginUtils` host expectations, compare existing platform plugins, and implement a new platform in phased DM-first then feed/comment support." }, { "name": "kt-prod-access", "title": "KT 生产环境访问手册", "description": "This skill should be used when the user asks about \"KT生产环境\", \"生产跳板机\", 生产服务器\", \"翻译服务器\", \"生产mysql数据库\", \"连接生产\", 生产环境SSH\", \"跳板机\", \"production bastion\", \"production server\", or needs to connect to KT production infrastructure." }, { "name": "kt-prod-entrypoints", "title": "KT 生产入口排查手册", "description": "This skill should be used when the user asks about \"生产入口\", \"域名走向\", Nginx 配置\", \"Cloudflare Tunnel\", \"这个域名指向哪里\", \"生产路由\", domain routing\", \"nginx config\", \"tunnel config\", or needs to trace production domain routing and entrypoints." }, { "name": "kt-prod-live-entrypoint-trace", "title": "KT 生产 live 入口追踪手册", "description": "This skill should be used when the user asks about \"生产 Nginx 日志\", \"线上 404/502\", live nginx 配置\", \"这个域名到底打到哪台机器\", \"这个网址为什么报错\", upstream 在哪\", \"看生产访问日志\", \"trace production domain\", or needs to trace a KT production domain from live entrypoint to upstream service and logs." }, { "name": "kt-rds-migrate", "title": "阿里云 RDS / PolarDB 数据迁移", "description": "将外部数据库（PVE/K3s/Pod DB/自建 MySQL 或 PostgreSQL）迁移到阿里云托管 RDS/PolarDB。当用户说\"迁移数据库到 RDS\"、\"数据迁移到阿里云\"、\"数据库迁移\"、\"RDS迁移\"时使用此 skill。生产/预发必须遵循 SaaS-first，不在 ACK 中长期运行数据库 Pod/PVC。" }, { "name": "kt-service-map", "title": "KT 生产服务全景地图", "description": "This skill should be used when the user asks about \"KT服务全景\", \"服务在哪台服务器\", \"哪个仓库对应哪个服务\", 生产服务清单\", \"服务地图\", \"service map\", \"kt系统架构\", \"哪台机器跑了什么\", 代码仓库在哪\", \"kt-api在哪\", \"翻译服务在哪\", or needs to know which production server hosts which service and which current code repository corresponds to each service." }, { "name": "kt-strategy", "title": "KT Strategy", "description": "This skill should be used when the user asks about \"战略\", \"我的战略\", \"战略仓库\", \"kt-strategy\", \"北极星\", \"愿景\", \"路线图\", \"项目组合\", \"决策原则\", \"定价原则\", \"战略决策\", \"复盘\", \"长期方向\", \"高价值验证\", \"低利润渗透\", \"KT 支付\", \"翻译准快自动化\", \"KT-ClawX桥接\", or wants recommendations aligned with the canonical strategy repository." }, { "name": "ktpay", "title": "kt-pay Skill 总入口", "description": "This skill should be used when the user asks to \"deploy kt-pay to test\", \"deploy kt-pay to production\", \"roll out kt-pay\", \"rollback kt-pay\", \"check kt-pay logs\", \"troubleshoot kt-pay\", \"debug kt-pay webhook\", or \"query kt-pay database\"." }, { "name": "ktpay-bridge-troubleshooting", "title": "KT 老后台 KTPay 桥接排查手册", "description": "This skill should be used when the user asks about \"kt8899 的 ktpay 为什么不通\", 老后台支付 404\", \"KTPay capabilities 失败\", \"KTPay 下单失败\", \"支付成功没到账\", ktpay callback 失败\", \"bc-pay-callback-service 排查\", or needs to diagnose the bridge between legacy KT admin, `bc-pay-callback-service`, and upstream `kt-pay`." }, { "name": "newapi", "title": "New API Multi-Environment CI/CD on Aliyun", "description": "This skill should be used when the user asks to \"deploy New API\", \"set up New API CI/CD\", \"promote New API to test\", \"promote New API to production\", \"connect Argo CD for New API\", \"use Infisical with Argo\", \"switch New API to GHCR\", or needs to manage the reusable GitHub Actions + GHCR + ACK + Argo CD workflow for KTAIorg/new-api on Alibaba Cloud." }, { "name": "newapi-log-cleanup", "title": "NewAPI Historical Log Cleanup", "description": "This skill should be used when the user asks to \"清理 NewAPI 历史日志\", \"NewAPI 日志保留策略\", \"自动清理 ktapi.cc 使用日志\", \"调用 NewAPI 清理历史日志接口\", \"delete /api/log target_timestamp\", or needs agents to safely automate NewAPI `logs` table retention through the admin API." }, { "name": "notification-architecture-reuse", "title": "通知与触达架构复用", "description": "This skill should be used when the user asks to \"通知设计\", \"复用telegram service\", \"消息推送设计\", \"telegram通知\", \"触达链路\", \"告警通知\", \"升级通知\", \"复用现有通知服务\", or needs architecture guidance for notifications, Telegram/IM delivery, escalation, and message routing that should reuse existing KT services instead of creating parallel paths." }, { "name": "nutrient-document-processing", "title": "Nutrient Document Processing", "description": "This skill should be used when the user asks to convert documents, OCR scanned files, extract text or tables, redact sensitive content, sign PDFs, or fill forms using the Nutrient DWS API." }, { "name": "oh-my-opencode-config", "title": "Oh My OpenCode Agent 配置指南", "description": "This skill should be used when the user asks to \"配置oh my opencode\", \"修改agent模型\", \"配置opencode agent\", \"oh my opencode agent\", \"agent模型配置\", \"修改agent model\", \"配置sisyphus模型\", or needs guidance on Oh My OpenCode agent configuration, model overrides, or plugin setup." }, { "name": "opencode-development", "title": "OpenCode Developer Guide", "description": "This skill should be used when the user asks about \"OpenCode\", \"oh-my-opencode\", \"how to develop with OpenCode\", \"plugin development\", \"tool registration\", \"agent system\", \"MCP integration\", \"hook system\", \"background task\", or any question about OpenCode's architecture, API capabilities, or how to extend it." }, { "name": "postgres-patterns", "title": "PostgreSQL Patterns", "description": "This skill should be used when the user asks about \"PostgreSQL优化\", \"数据库索引\", \"PostgreSQL安全\", \"Supabase实践\", \"SQL查询优化\", or needs PostgreSQL database patterns." }, { "name": "python-patterns", "title": "Python Development Patterns", "description": "This skill should be used when the user asks about \"Python规范\", \"PEP 8\", \"Python类型注解\", \"Pythonic写法\", \"Python最佳实践\", or needs Pythonic idioms and best practices." }, { "name": "python-testing", "title": "Python Testing Patterns", "description": "This skill should be used when the user asks to \"Python测试\", \"pytest\", \"fixture\", \"mock\", \"参数化测试\", \"覆盖率\", or needs Python testing strategies using pytest." }, { "name": "security-review", "title": "Security Review Skill", "description": "This skill should be used when the user asks to \"安全审查\", \"认证实现\", \"输入验证\", \"密钥处理\", \"API安全\", \"支付安全\", or needs a security checklist and patterns for sensitive features." }, { "name": "security-scan", "title": "Security Scan Skill", "description": "This skill should be used when the user asks to \"安全扫描\", \"扫描OpenCode配置\", \"检查CLAUDE.md安全\", \"MCP安全检查\", or needs to scan Claude Code or OpenCode configuration for security vulnerabilities." }, { "name": "skill-installation-workflow", "title": "Skill Installation Workflow", "description": "用于用户要求“安装 skill”、“同步 skill”、“安装到 Codex”、“部署 skill 到 OpenCode”、“把 skill 落库”、“把 skill 提交到 skill 仓库”、“更新 skill 并同步本地”、“发布 skill”、“把这个能力做成 skill”或“管理 skill 仓库”时，按源仓库维护、安装到本地 Codex skills 目录并验证触发质量的完整流程执行。" }, { "name": "springboot-patterns", "title": "Spring Boot Development Patterns", "description": "This skill should be used when the user asks about \"Spring Boot架构\", \"REST API设计\", \"Spring分层架构\", \"Spring异步\", \"Spring缓存\", or needs Spring Boot architecture patterns." }, { "name": "springboot-security", "title": "Spring Boot Security Review", "description": "This skill should be used when the user asks about \"Spring Security\", \"Spring认证授权\", \"CSRF配置\", \"Spring Rate Limiting\", \"依赖安全扫描\", or needs Spring Security best practices." }, { "name": "springboot-tdd", "title": "Spring Boot TDD Workflow", "description": "This skill should be used when the user asks to \"Spring Boot测试\", \"JUnit 5\", \"Mockito\", \"MockMvc\", \"Testcontainers\", \"JaCoCo覆盖率\", or needs TDD for Spring Boot." }, { "name": "springboot-verification", "title": "Spring Boot Verification Loop", "description": "This skill should be used when the user asks to \"验证Spring Boot项目\", \"Spring Boot发布前检查\", \"Spring安全扫描\", \"构建验证\", or needs a verification loop for Spring Boot projects." }, { "name": "static-frontend-release", "title": "静态前端发布与回滚", "description": "This skill should be used when the user asks to \"上线管理后台前端\", \"发布 kt-admin-web\", \"部署 www.kt8899.org 后台页面\", \"把前端发到生产\", \"回滚后台前端\", or needs a safe static frontend release workflow with backup, verification, and fast rollback." }, { "name": "strategic-compact", "title": "Strategic Compact Skill", "description": "This skill should be used when the user is in a long session, approaching context limits, switching task phases, or needs manual context compaction at logical checkpoints instead of arbitrary auto-compaction." }, { "name": "tdd-workflow", "title": "Test-Driven Development Workflow", "description": "This skill should be used when the user asks to \"TDD\", \"测试驱动开发\", \"写测试\", \"先写测试\", \"80%覆盖率\", or needs a test-driven development workflow with unit, integration, and E2E tests." }, { "name": "telegram-ai-task-runtime", "title": "Telegram AI Task Runtime", "description": "用于开发、排查或交接 Telegram AI Task Runtime、kt-telegram、kt telegram 账号登录、API ID/API Hash 凭据导入、KT Auth bearer、Cloudflare Tunnel 入口、旧 Telegram Matrix/Managed System 迁移参考时使用。用户提到 Telegram runtime、Telegram 账号登录、API credential、kt telegram、telegram-ai-task-runtime、kt-telegram、旧 Matrix/Managed System 弃置或迁移时触发。" }, { "name": "telegram-escalation", "title": "Telegram 求助通知", "description": "This skill should be used when the user asks to \"telegram求助\", \"telegram通知别人\", \"给别人发telegram消息\", \"卡住了帮我通知\", \"用bot求助\", \"telegram escalation\", or needs the agent to notify a specific person via Telegram Bot when work is blocked, risky, or requires human assistance." }, { "name": "verification-loop", "title": "Verification Loop Skill", "description": "This skill should be used when the user asks to \"验证工作成果\", \"发布前检查\", \"质量验证\", \"代码验收\", or needs a comprehensive verification loop for completed work before shipping." }, { "name": "writing-hookify-rules", "title": "Writing Hookify Rules", "description": "This skill should be used when the user asks to \"create a hookify rule\", \"write a hook rule\", \"configure hookify\", \"add a hookify rule\", or needs guidance on hookify rule syntax and patterns." } ] }