Browse reusable Agent Skills, each with a clear purpose and practical guidance.
精确复现特定作者的中文写作风格。适用于：(1) 以该风格从零生成文章，(2) 将AI风格或其他风格的文章改写为该风格，(3) 在同一次任务里对草稿做终稿打磨/精修（保持作者笔力，不得改成中性说明书），(4) 审阅文章是否符合该风格，(5) 结构保真地将非简体中文翻译为简体中文（保留原始结构与不可改动片段，如人名/专名、代码、代码块、URL 等；不擅自增删）。核心特征：半文半白的用词、长短交替的句式节奏、类比先行的论证方式、冷面热心的情感表达、第一人称介入的立场标定；并在不破坏作者习惯的前提下，清除显眼的 AI 写作痕迹（24 项检测）。触发词：写作、改写、风格、润色、重写、精修、再优化、二稿、终稿、最终版、翻译、译、translate、翻成、译成、转为简体。
基于西柚洞察MCP的亚马逊竞品分析与广告策略工具。提供7大核心工作场景：实时监控广告投放效果、快速找到高性价比流量缺口、快速拆解对标竞对打法、提升新品推广效率、精准拆解竞品流量以及广告策略、透视竞品广告策略和预算、高效搭建关键词库。适用于亚马逊卖家进行竞品分析、广告优化和关键词研究。
Chinese AI/tech writing de-AI editor for posts, X/Twitter threads, technical essays, product notes, model reviews, and public-writing drafts. Use when the user asks to 去AI味, 改得像本人, 写推特post, 精修中文AI技术文章, or complains about AI-flavored shells such as 不是A而是B, 真正/其实/本质上, 更重要的是, 冒号讲义腔, 空泛总结, 顺滑但没作者判断的稿子.
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
Turn an approved PRD or implementation goal into SRS/FRS technical requirements (How), architecture, contracts, and verification decisions.
Proofread and lightly edit sorg Markdown content before publication. Use when the user passes a content file path such as content/nanoglyphs/052-adrift.md, content/articles/*.md, content/fragments/*.md, or another prose-heavy Markdown file and asks for a proofread, spelling/grammar check, minor editorial pass, repeated-word scan, or publication readiness review.
Screens all Hyperliquid perps and surfaces top trading setups
Analyze whether end users will discover clear value in product ideas. Use when: discussing product concepts, evaluating features, providing product improvement directions, planning marketing strategies, analyzing adoption or retention problems, assessing whether copy communicates value, mapping features to usage scenarios or use cases, or when the user is uncertain about product direction, positioning, or whether end-user demand exists (e.g., 'is this a good idea?', 'what do you think of this product?', 'will users want this?', 'what is this feature useful for?', 'how should I explain this feature's value?', 'what do you think of this copy?', 'help me write a few usage scenarios', 'why aren't users retaining?', 'how should we position this?').