Use this skill when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually works end-to-end. Use the repository bootstrap scripts to standardize the local `clawteam` command and to wire project-local `.agents` and `.claude` skills back to this repository. This skill is repository-development oriented, not a general end-user usage guide.

Build the visual layer of a holaOS dashboard app — TanStack Start + @holaboss/ui + workspace tokens. Use when an app has SDK primitives wired (via app-builder-sdk) AND needs a `src/client/` UI surface. NOT for marketing pages, NOT for snapshot HTML reports.

杀猪盘检测器。当用户提到"朋友推荐"、"群里说"、"老师带"、"内幕消息"、"小红书 / 抖音看到推荐"等关键词，或显式要求"看看是不是杀猪盘 / 检测一下风险 / 这只票安全吗"时使用。扫描 8 个信号给出风险评级 🟢🟡🟠🔴。

cheat-on-content 的状态看板。显示当前模式 / rubric 版本 / 校准进度 / 待复盘 / pool 状态 / 是否该升级 SQLite / 是否该 bump rubric。**任何时候都可调，无副作用**。触发词："状态"/"看板"/"status"/"我现在该做什么"/"进度怎么样"。

Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/. Classifies incoming tasks and routes to brainstorm, direct edit, or task workflow. Use when beginning a new coding session, resuming work, starting a new task, or re-establishing project context.

Set up and run an autonomous experiment loop for any optimization target. Gathers what to optimize, then starts the loop immediately. Use when asked to "run autoresearch", "optimize X in a loop", "set up autoresearch for X", or "start experiments".

When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies.

Workspace Git identity and credential management. ALWAYS invoke this skill when the user asks about configuring Git user info, adding HTTPS tokens, importing SSH keys, or managing workspace-level Git authentication.

Image expert. ALWAYS invoke this skill when you need to read, analyze, describe, or generate images. Use for screenshots, photos, charts, diagrams, AI-generated images, or any visual content.

Synthesize the current conversation into a milestone brief (PRD). Writes to `M###-CONTEXT.md` by default, or files a GitHub issue only with explicit user confirmation. Use when asked to "turn this into a PRD", "draft a milestone brief", "capture this context", "write it up", or when enough has been discussed to commit the plan to paper. Does not interview — it synthesizes what is already known.

Lint and format code. Auto-detects ESLint, Biome, Prettier, or language-native formatters and runs them with auto-fix. Reports remaining issues with actionable suggestions.

Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.

Regenerate Python + TypeScript gRPC stubs after editing proto files. Use when proto/*.proto changes, imports from bindu.grpc.generated fail, CI reports generated-code drift, or HandleMessages calls fail with proto mismatch.

Write a practical Product Requirements Document (PRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, create, generate, or save a PRD, product requirements document, product spec, feature requirements, 产品需求文档, 产品方案, 需求说明, or PRD from an idea. Output a diagram-rich Markdown PRD under the current project's markdown/ directory.

Write a practical Business Requirements Document (BRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, generate, refine, or save a BRD/business requirements document/product business case in Markdown, especially when the output should be saved under the current project's markdown directory and include diagrams using Mermaid, SVG, or ASCII.

Search current hot social or industry news, identify visible "world bugs" such as incentive failures, regulatory gaps, information asymmetry, safety risks, and unreasonable value-chain behavior, then propose root-cause fixes and business opportunities in a sourced, diagram-rich Chinese Markdown report saved under the current project's markdown directory. Use when the user gives an industry name and asks to find bugs/opportunities from industry news, or gives no industry and wants hot social-news bug analysis.

输入一个产品 idea（一句话或详细描述均可），自动生成图文并茂、结构完整的 MRD（市场需求文档），以 Markdown 格式保存到当前项目 markdown/ 目录，同时输出配套 SVG 图表文件。触发条件：用户提到"写 MRD"、"帮我写市场需求文档"、"生成 MRD"、"写产品市场需求"、"我有个产品想法"、"帮我把这个 idea 写成 MRD"、"市场需求文档模板"、"产品立项文档"、"帮我写需求文档"。即使用户只给出一句简短的产品描述如"我想做一个 XX 产品"，也应立即使用本 skill 生成 MRD。本 skill 面向产品经理、创业者、产品负责人，输出可直接用于团队评审和立项决策的专业文档。

预测美股个股次日走势，输出图文并茂的 Markdown 分析报告（含逻辑推导、中间结果、概率量化、操作建议）。触发条件：用户输入美股股票名称或代码，并希望获得次日走势预测；关键词包括"预测明天走势"、"明天能涨吗"、"帮我分析一下XX股票"、"明天该买吗"、"次日预测"、"做T建议"、"短线操作"、"明日行情"、"值得持有吗"等。即使用户只说"帮我看看NVDA明天怎么走"或"AAPL明天能不能买"，也应使用本 skill。输出 Markdown 文件保存到当前项目 markdown/ 目录，要求逻辑清晰、概率可量化、图文并茂，投资小白也能看懂。

深度解读学术论文，将论文 PDF（文件或 URL）转化为通俗易懂、图文并茂的 Markdown 解读文档，保存到项目的 markdown/ 目录。触发条件：用户上传或提供论文 PDF、提到"解读论文"/"读论文"/"分析这篇论文"/"帮我看这篇 paper"，或任何需要深入理解一篇学术论文的场景。即使用户只说"帮我看这个 PDF"但内容是论文，也应使用本 skill。输出文件包含：论文定位、知识地图、5W1H精读、术语词典、批判性评估五大板块，并在关键位置插入 mermaid/svg/text 图表辅助理解。

Read a provided URL, local file, or pasted article, digest its core claims and assumptions, rebuild the topic into a concise original source-backed Chinese Markdown article, and save it under the current project's markdown directory. Use when the user asks to upgrade, elevate, rewrite, extend, deconstruct, critique, refine, or produce a higher-order article from an existing article or URL, especially when the desired output should preserve the source insight but feel like a clean standalone article rather than an analysis of the source.