Email, calendars, task management, and automation (7.8K skills)
风险诊断师（方有安）。擅长持仓风险体检、泡沫识别、拥挤度排雷、仓位决策建议。 在 A 股研究团队中由主理人调度，参与 Workflow 1 / Workflow 4。 擅长：持仓集中度风险、基本面风险信号（业绩变脸/商誉/质押）、泡沫反身性分析（基本面驱动 vs 预期透支）、拥挤度评估（基金重仓程度、踩踏风险）、仓位决策（总仓位区间 + 加仓/减仓条件 + 结构建议）、逐只持仓健康度评级（🟢🟡🔴）。
The English summary is being prepared. Showing the original description.
A股研究团队主理人（古见远 · 研究总监）。调度 7 位专业成员（宏观策略师、市场解读师、个股研究员、估值定价师、产业链分析师、资金行为分析师、风险诊断师）按 6 种预设 Workflow 完成 A 股研究工作，输出结构化研究报告。 触发词：A股、股票分析、市场分析、板块分析、持仓诊断、个股研究、 宏观分析、产业链、资金流向、估值分析、风险诊断、 股票推荐、板块推荐、投资建议、该不该买、能不能买、 今天怎么走、开盘前分析、市场情绪、主线、板块、ETF。
The English summary is being prepared. Showing the original description.
估值定价师（贾不贵）。擅长估值判断——PE/PB/PS 历史分位、PE Bands、PEG、同行对比、分红与股东回报分析。 在 A 股研究团队中由主理人调度，参与 Workflow 1 / Workflow 3 / Workflow 4 / Workflow 5 / Workflow 6。 擅长：PE/PB/PS 当前值与历史分位数、同行业可比公司估值横向对比、合理估值区间判断、分红质量评估（持续性、现金流支撑、回购协同）、红利资产属性判断。
The English summary is being prepared. Showing the original description.
Agent-agnostic long-term project memory through `.memory-bank/` + RULES (TDD/SOLID/Clean Architecture/FSD/Mobile) + dev-toolkit commands. Use when working in a project with a `.memory-bank/` directory or when the user explicitly asks for memory-bank workflow, code rules, or dev-toolkit commands (`/mb`, plan, spec, verify, done; «память проекта», «контекст проекта», «план», «продолжай по плану»).
The English summary is being prepared. Showing the original description.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
The English summary is being prepared. Showing the original description.
Decomposition playbook and anti-temptation rules for an orchestrator agent that routes work through the Surogates subagent task layer. Pair this skill with an AgentDef whose tool filter strips the implementation tools (terminal, file, web, code) — that's how 'don't do the work yourself' is enforced structurally, not just behaviorally.
The English summary is being prepared. Showing the original description.
Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.
The English summary is being prepared. Showing the original description.
Use when facing 2+ independent tasks or investigations that can be worked on without shared state or sequential dependencies — fan out to specialized sub-agents with isolated context, then synthesize the results.
The English summary is being prepared. Showing the original description.
Pitfalls, examples, and edge cases for workers executing a Surogates subagent task. Loaded automatically when the dispatcher spawns a session bound to a Task (Session.task_id is set).
The English summary is being prepared. Showing the original description.
AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.
The English summary is being prepared. Showing the original description.
Compact the current conversation into a handoff document for another agent to pick up.
The English summary is being prepared. Showing the original description.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
The English summary is being prepared. Showing the original description.
Use when starting a new feature, product, or system design. Eliminates the spec-implementation gap by making specifications the primary artifact that drives code generation. Keywords: SDD, spec-driven, PRD, feature spec, user stories, implementation plan, specification, acceptance criteria, Given-When-Then.
The English summary is being prepared. Showing the original description.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
The English summary is being prepared. Showing the original description.
Use when designing human approval gates for high-stakes agent actions. Keywords: human-in-the-loop, HITL, approval gate, checkpoint, confirmation, risk-tiered, action review.
The English summary is being prepared. Showing the original description.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
The English summary is being prepared. Showing the original description.
Use when you have a spec or requirements for a multi-step task, before touching code
The English summary is being prepared. Showing the original description.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
The English summary is being prepared. Showing the original description.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
The English summary is being prepared. Showing the original description.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
The English summary is being prepared. Showing the original description.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
The English summary is being prepared. Showing the original description.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
The English summary is being prepared. Showing the original description.
Stop. That last message did not land: re-pitch it.
The English summary is being prepared. Showing the original description.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
The English summary is being prepared. Showing the original description.