Agent Skills

---

name: koog-assistant

description: Concise general-purpose assistant powered by JetBrains Koog. Use when a brief, focused answer is preferable to long-form output.

---

name: llm-judge

description: AI quality judge that scores agent responses 0-10 across helpfulness, accuracy, completeness, and clarity. Use when evaluating multi-agent output or implementing LLM-as-judge quality gates.

---

name: mcp-analyze-topic

description: Expert analyst persona used by the MCP analyze-topic tool to produce structured topic analyses. Use when invoked through the Atmosphere MCP server's analyze-topic tool.

---

name: mcp-chat-summary

description: Chat moderator that summarizes ongoing conversations. Use when invoked through the Atmosphere MCP server's chat-summary tool.

---

name: omnichannel-chat

description: General-purpose AI assistant that answers naturally over web chat and external messaging platforms (Telegram, Slack, Discord, WhatsApp, Messenger). One agent, every channel.

---

name: rag-assistant

description: Knowledge base assistant that retrieves and cites documents from a curated index. Use when answering questions that must be grounded in specific source material with citations.

---

name: research-agent

description: Market research specialist that searches the web for market data, competitor intelligence, and industry reports, with curated fallback data when offline. Use when gathering external evidence for strategic decisions.

---

name: startup-ceo

description: CEO coordinator that dispatches research, strategy, finance, and writer specialists via A2A and synthesizes their findings into a GO/NO-GO investment briefing. Use for multi-agent advisory workflows.

---

name: strategy-agent

description: Market strategy analyst performing SWOT, competitive positioning, market-timing assessment, and go-to-market recommendations from research findings. Use after the research-agent has produced market data.

---

name: support-agent

description: Front-line support desk for account questions, technical troubleshooting, and general inquiries. Use as the default customer entry point; routes billing questions to the billing-agent via handoff.

---

name: support-agent

---

name: tool-assistant

description: Tool-calling assistant with backend functions for time, city time, weather, and temperature conversion, plus cost metering and approval workflows. Use when a question needs real-time data via tool calls.

---

name: writer-agent

description: Business writer that synthesizes research, strategy, and financial findings into executive briefings and reports. Use after upstream specialist agents have produced their data.

---

name: arming-thought

description: 求是方法论的入口与总原则。在每次新的顶层会话开始时加载一次，用「实事求是」约束全部判断，并只在明确适用时把任务路由到对应的方法论 skill；被派遣执行单一具体任务的子 agent 直接跳过。 English: Entry point and governing principle of the Qiushi methodology. Load once at the start of a top-level session to enforce "seek truth from facts" and route to a downstream skill only when it clearly helps. Delegated sub-agents on narrow tasks should skip it.

---

name: concentrate-forces

description: 集中兵力：多件事同时争抢时间、注意力或预算时，列出全部待办，选定唯一主攻目标并公开锁定，彻底解决、验证后再转向下一个。当待办过多、推进分散、"每件都做了一点但都没做完"、需要决定先做什么时触发；只有一个任务、任务彼此独立可并行、用户明确要求同时推进时不触发。 English: Concentrate forces. When several tasks compete for time, attention, or budget, enumerate them, lock onto a single main target, finish and verify it completely, then move on. Trigger when priorities sprawl, effort is scattered, or you must decide what to do first; skip when there is one task, tasks are independent and parallel, or the user explicitly wants them advanced together.

---

name: contradiction-analysis

description: 矛盾分析法：把复杂问题拆成若干对立面，找出规定其他矛盾的主要矛盾及其主要方面，判定对抗性 / 非对抗性，并据此选择处理方式。当问题头绪多、多个因素互相牵制、优先级不清、根因不明、反复修不好、trade-off 说不清时触发；直接执行类任务或用户已定方案时不触发。 English: Contradiction analysis. Decompose a tangled problem into opposing forces, isolate the principal contradiction and its dominant side, classify it as antagonistic or non-antagonistic, and choose the response accordingly. Trigger on unclear priorities, unknown root causes, recurring failures, or trade-offs that resist explanation; skip for direct execution or when the user has already chosen the solution.

---

name: criticism-self-criticism

description: 批评与自我批评：在工作完成、阶段验收、收到批评或同类错误反复出现时，对成果和过程做诚实、具体、基于事实的审视，输出可执行的改进项，并处理外来批评而不辩解。触发信号包括 review、复盘、审查、"帮我看看有没有问题"、"你确定吗"；任务刚开始或只是单步查询时不触发。 English: Criticism and self-criticism. After delivery, at a review checkpoint, on receiving criticism, or when the same mistake recurs, examine the result and the process honestly and concretely, produce actionable fixes, and accept valid criticism without defensiveness. Triggers include review, retrospective, audit, "check this for problems", "are you sure"; skip at the start of a task or for one-step lookups.

---

name: investigation-first

description: 调查研究：在下判断、做决策、给建议之前，先用第一手材料弄清现状，产出「事实 / 推断 / 未知」三栏调查结论。当上下文不完整、证据薄弱、领域陌生、用户说"先别动手"、或你发现自己在凭印象作答时触发；已充分调查后的执行阶段不要重复触发。 English: Investigate before judging. Gather firsthand facts and produce a fact / inference / unknown ledger before any recommendation. Trigger when context is incomplete, evidence is thin, the domain is unfamiliar, the user says "look first", or you notice yourself answering from impression; skip when investigation is already done and the task is pure execution.

---

name: mass-line

description: 群众路线：从持有真实情况的多方（用户、使用者、代码库、日志、运行结果）收集分散意见，系统化为方案，再带回去对齐与检验，循环改进。当多方意见分歧、需要汇总零散反馈、方案要拿回给真实使用者确认、或你发觉自己在闭门造车时触发；信息源单一且完整、处于执行阶段时不触发。 English: Mass line. Collect scattered input from everyone who holds ground truth (users, operators, codebase, logs, runtime results), synthesize it into a coherent plan, take it back for alignment and validation, and iterate. Trigger when inputs conflict, feedback must be consolidated, a plan needs sign-off from real users, or you sense you are designing in isolation; skip when there is a single complete source and the work is pure execution.

---

name: openspec-apply-change

description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

---

name: openspec-archive-change

description: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

---

name: openspec-explore

description: Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

---

name: openspec-propose

description: Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

---

name: openspec-sync-specs

description: Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.