research-brief
>
slack-channel-monitor
>
slack-standup-digest
>
spark-version-upgrade
Upgrade Apache Spark applications between major versions (2.x→3.x, 3.x→4.x). Covers build files, deprecated APIs, configuration changes, SQL/DataFrame updates, and test validation.
technical-writing
Guides technical explanations toward flowing, direct, conversational prose. This skill should be used for engineering chat, design discussion, architecture analysis, code-review explanations, and technical recommendations that should be concise without becoming fragmented or vague.
ticket-to-code-change
>
upstream-fork-sync
>
maven-troubleshoot
Maven 构建故障排查专家，擅长解决依赖冲突、编译错误、插件配置问题
hello-skill
示例技能，用于 PluginRegistry 测试
api-design
RESTful API design best practices and conventions guide
code-quality-suite
代码质量综合技能包（代码审查 + 单元测试）
code-review
代码审查最佳实践指南
database-design
数据库设计规范与优化指南
git-commit-guide
Git 提交规范（Conventional Commits）
java-best-practices
Java 编码最佳实践与设计模式
unit-testing
Java单元测试编写指南（基于JUnit和Mockito）
weather
Get current weather and forecasts (no API key required).
bookkeeper
Specialized in maintaining project documentation, ensuring it reflects the current state of the codebase and operational procedures.
database-analyzer
Specialized in syncing the production database and performing analysis on trades, balances, and market history.
database-sqlite
SQLite best practices, connection management, and migration system for PolyFlup.
log-analyzer
Specialized in syncing logs from production and analyzing them to find trade history, errors, or performance metrics.
polyflup-history
Chronological log of system improvements and session summaries for PolyFlup.
polyflup-ops
Operational commands, environment configuration, and deployment for PolyFlup.
polymarket-trading
Polymarket-specific terminology, trading strategies, and API reference.
python-bot-standards
Coding standards, modular architecture, and common execution patterns for the PolyFlup Python backend.
svelte-ui-standards
Coding standards and UI guidelines for the PolyFlup Svelte dashboard.
trainer
Responsible for keeping the system's "Skills" and internal knowledge base up to date with the latest project developments.
commit-message
>
error-handling
>
excalidraw-ai
>
python-backend
>
logfire
>
pydantic
>
linting
>
ty-skills
>
candid-chrome-qa-fix
Take a candid-chrome-qa findings JSON, let the user pick which findings to fix, and dispatch fixes — single batched PR, one PR per finding via Conductor deep links, local-only, or issues-only. Optionally files Linear (or other tracker) issues per finding before shipping.
candid-chrome-qa
Drive a real Chrome session against a running web app to find bugs and write structured findings JSON. Use when the user asks for a QA pass, smoke test, UX audit, accessibility check, or "find bugs / polish / a11y / perf / copy issues" on a route.
candid-fast-ship
Fast ship for low-risk changes — runs only the steps you explicitly enable in fastShip config
candid-improve-implementation
Use when the code works and you want a focused pass on improving approach, clarity, and quality — distinct from candid-review's defect hunt. Each suggestion includes a concrete before/after, tradeoffs, and confidence level.
candid-improve
Use when you have an output — copy, a doc, an answer, a plan, a prompt, any text artifact — and want it made better against your goal. Runs a critique→refine loop with configurable stop conditions and auto/review-each/interactive modes. Default is a single pass using the current session context to decide what "better" means.
candid-loop
Run candid-review in a loop until all issues are resolved, with configurable auto, review-each, or interactive modes and support for ignored issues
candid-review
Use when reviewing code changes before commit or PR — configurable harsh or constructive review against Technical.md standards, with categorized issues, actionable fixes, todo tracking, and optional auto-commit.
candid-ship
Ship your changes - review, build, test, create PR, and optionally auto-merge
candid-validate-standards
Validate Technical.md for vague rules, linter overlaps, and effectiveness issues
candid-init
Generate Technical.md and config.json by deeply analyzing your codebase structure, architecture, and patterns
candid-optimize
Audit and optimize the context candid loads during reviews — Technical.md efficiency, exclude patterns, decision register, and config tuning
claudish-usage
CRITICAL - Guide for using Claudish CLI ONLY through sub-agents to run Claude Code with OpenRouter models (Grok, GPT-5, Gemini, MiniMax). NEVER run Claudish directly in main context unless user explicitly requests it. Use when user mentions external AI models, Claudish, OpenRouter, or alternative models. Includes mandatory sub-agent delegation patterns, agent selection guide, file-based instructions, and strict rules to prevent context window pollution.
architect-detective
Use when analyzing architecture and system design. Find design patterns, map layers, identify core abstractions via PageRank. Uses claudemem AST structural analysis for efficient architecture investigation.
claudemem-orchestration
Use when orchestrating multi-agent code analysis with claudemem. Run claudemem once, share output across parallel agents. Enables parallel investigation, consensus analysis, and role-based command mapping.
claudemem-search
⚡ PRIMARY TOOL for semantic code search AND structural analysis. NEW: AST tree navigation with map, symbol, callers, callees, context commands. PageRank ranking. Recommended workflow: Map structure first, then search semantically, analyze callers before modifying.
Page 795 of 1652 · 82593 results