Etsy keyword search scraper: given a search keyword and optional page number, returns paginated product listings with listingId, shopId, title, url, image, salePrice, originalPrice, currency, rating, reviewCount, shopName, isAd, freeShipping, badge from etsy.com search results. Use when user mentions Etsy, etsy.com, Etsy search, search Etsy by keyword, scrape Etsy listings, extract Etsy products, Etsy product search, Etsy marketplace search, find products on Etsy, Etsy handmade search, Etsy vintage search, Etsy craft search, bulk Etsy product export, Etsy price monitoring, Etsy competitor research, Etsy top listings, Etsy bestseller extraction, Etsy sales data, Etsy shop discovery via keyword. Also applies to trend research on handmade or craft niches, competitor keyword ranking on Etsy, sourcing Etsy suppliers by product type, and any paginated bulk product collection driven by a search keyword.

Forges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a site's internal APIs, wants to reproduce an existing scraper/SaaS/tool product (shown its product page), or asks for bulk extraction at scale (dozens to thousands of records, casually phrased — 'grab N posts', 'pull all listings', 'no duplicates'). Unlike browser-act: reusable, not one-off. Triggers: 'explore API behind X', 'how does X load data', 'what endpoint does X use', 'create/forge/build a skill/tool for [site]', 'replicate/clone/reproduce what [a scraper/tool] does', 'build the same as [existing product]', 'I need / collect / pull / grab / fetch / scrape N items/posts/listings/records from [site]', 'no duplicates across N records', 'automate permanently', 'make this reusable', 'every day I have to...', 'monitor [site]', 'browser-act-skill-forge'. Human-operation automation; never refuse.

Review pull requests for the awesome-agentic-patterns repository. Use when asked to validate a PR, assess whether a contribution fits the repo, inspect pattern submissions under patterns/, check merge readiness, repair a small submission issue on top of a contributor branch, draft a polite contributor comment, or apply the repository's pattern-first and non-promotional contribution policy to a GitHub pull request.

Use when you need the current user's identity or contact info: name, job title, employee number, email, phone, or department.

Use when the user asks to create slides with a specific style, wants to use or inspect a slide template by code, wants to see platform-provided slide template options before creating, describes a custom template style, provides a PPTX/PPT file to convert into a platform template, or wants to extract a template from an existing Super Magic slide project.

Use when the user wants to interact with Lark/Feishu in any way — including but not limited to: reading, querying, searching, sending, replying to, forwarding, or downloading Lark/Feishu IM messages and chat history; managing group chats; listing, viewing, searching, creating, or editing cloud docs/files, Drive, Markdown, spreadsheets, Base tables, wiki, whiteboards, slides, apps, calendars/events/meeting rooms, contacts/org structure, tasks/todos, approvals, attendance, mail, minutes, VC notes, OKRs, real-time events, or custom Lark CLI skills. Load this skill first to find the right sub-skill.

Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people. Use this skill whenever someone wants to create an interactive course, tutorial, or educational walkthrough from a codebase or project. Also trigger when users mention 'turn this into a course,' 'explain this codebase interactively,' 'teach this code,' 'interactive tutorial from code,' 'codebase walkthrough,' 'learn from this codebase,' or 'make a course from this project.' This skill produces a stunning, self-contained HTML file with scroll-based navigation, animated visualizations, embedded quizzes, and code-with-plain-English side-by-side translations.

Analyze PR review comments from a GitHub PR URL. Fetch review comments, verify each finding against the actual codebase, assess validity (correct/incorrect/partial), present a structured summary with recommended actions, and optionally reply to each comment on GitHub. Use when given a PR review URL or when asked to check/analyze PR feedback.

Domain knowledge for working on the Natron compositor's own C++ source code (Engine/Gui/HostSupport). Use when navigating, fixing, or extending the Natron codebase, doing Qt5/Qt6 work, building Natron, building its Sphinx docs, or triaging its GitHub issues.

Author pre/post-iteration hooks for an autoresearch session. Use when the user asks to add research fetching, Slack/webhook notifications, persistent learnings, auto-tagging, anti-thrash intervention, idea rotation, or any side effect around iterations.

Prepare and open a safe GitHub pull request for this repository. Use when the user asks to create, open, or prepare a pull request from completed branch work. Inspect the branch and diff, validate changes, follow the repository PR template, push only when authorized, and open a draft PR by default.

Create a safe, focused Git commit for this repository. Use when the user asks to commit completed work, prepare a commit, or choose a Conventional Commit message. Inspect the working tree, stage only intended files, validate relevant changes, and create the commit without pushing.

Add agent-first observability to code — structured logs, health endpoints, failure-state persistence, and explicit failure modes — so the next agent hitting a problem at 3am has the signals it needs to diagnose. Use when asked to "add logging", "add observability", "add metrics", "debug later", "make this observable", or when building/refactoring a subsystem that will run unattended (auto-mode engine, background jobs, servers, watchers). Operationalizes VISION.md's "agent-first observability" principle.

Relentless sequential interview that stress-tests a plan or design until every decision branch is resolved. Use when the user wants to "grill me", "stress-test the plan", "interrogate my design", "resolve the decision tree", or whenever a plan feels hand-wavy, under-specified, or carries hidden coupling that planning phases must surface before execution. Pairs with the discuss phase and blocks execution until alignment is reached.

Orchestrate GSD (Get Shit Done) projects programmatically via headless CLI. Use when an agent needs to create milestones from specs, execute software development workflows, monitor task progress, check project status, or control GSD execution (pause/stop/skip/steer). Triggers on requests to "run gsd", "create milestone", "execute project", "check gsd status", "orchestrate development", "run headless workflow", or any programmatic interaction with the GSD project management system. Essential for building orchestrators that coordinate multiple GSD workers.

CCPM - spec-driven project management: PRD → Epic → GitHub Issues → parallel agents → shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync the X epic', 'push tasks to github'), starting work on an issue ('start working on issue N', 'let's work on issue N'), analyzing parallel work streams, running standups ('standup', 'run the standup'), checking status ('what's next', 'what's blocked', 'what are we working on'), closing issues, or merging an epic. Use ccpm any time the user is talking about shipping a feature, managing work, or tracking progress — even if they don't say 'ccpm' or 'PRD'. Do NOT use for: debugging code, writing tests, reviewing PRs, or raw GitHub issue/PR operations with no delivery context.

输入 PRD 文档（Markdown 或 PDF），以开发架构师的角色编写字段/接口级精度的功能设计文档（Functional/Technical Design Doc），以 Markdown 格式保存到当前项目 markdown/ 目录。这份文档是开发者、reviewer、测试者三方协作的唯一契约——三者互相隔离、不能看对方的产出物（测试者看不到代码，reviewer 不参与开发），所以必须把每个功能点写到可直接落地、可直接测试的精度：接口请求/响应字段、错误码、状态机、数据模型、异常边界场景都要明确。触发条件：用户提到"功能设计文档"、"技术设计文档"、"tech design"、"functional design"、"从 PRD 生成设计文档"、"帮我把这份 PRD 转成开发文档"、"写一份给开发和测试用的设计文档"、"接口设计 + 验收标准"，或者用户上传了一份 PRD 并希望进入开发落地阶段。即使用户只说"基于这个 PRD 帮我写设计文档"或"把这个需求文档详细化成开发能直接看懂的文档"，也应立即使用本 skill。不要将本 skill 与 write-prd/write-brd 混淆——那两个 skill 输出的是面向业务评审的需求文档（WHY/WHAT 层），本 skill 输出的是面向研发落地的技术设计文档（HOW 层，包含具体字段和契约），通常以 PRD 作为输入而非从零开始的 idea。

通过持续的对话式提问，训练用户的逻辑思维与独立思考能力：给用户出思考题、用苏格拉底式追问引导用户自己发现漏洞、对用户的每次回复做点评并给出具体改进意见，同时把训练记录和薄弱点保存到 markdown，用于后续对话中做针对性、渐进式的训练。触发条件：用户提到"训练我的逻辑思维"、"锻炼独立思考"、"陪我练逻辑"、"logic training"、"批判性思维训练"、"苏格拉底式提问"、"帮我练习思辨"、"考考我的逻辑"、"跟我辩论/追问练习"，或者用户明确要求"你来提问，我来回答，你来点评"这种角色反转式训练。即使用户只说"我想提升一下逻辑思维能力，帮帮我"或"以后没事就考考我"，也应使用本 skill，并且要记住：这是一个跨越多轮对话、甚至跨越多次会话的持续训练关系，每次用户提到练习/考我/继续训练，都应该回到本 skill 而不是当作普通问答。

面向投资者，抓取最近3天内指定行业或默认主题（中美关系、地缘局势、美联储、民生数据、高科技、生物医疗、云计算产业、AI产业链）的新闻，按分类汇总摘要，给出投资者全面总结，并推演对行业和上市公司的影响（逻辑清晰、有历史数据/事件支撑、图文并茂），输出 Markdown 文件到当前项目 markdown/ 目录。 触发条件：用户提到"新闻影响分析"、"投资者新闻"、"最近新闻对哪些股票有影响"、"抓取新闻做投资分析"、"新闻推演"、"帮我看看最近新闻对投资的影响"、"行业新闻影响"、"最近有什么值得关注的新闻"、"最近3天新闻"、"新闻对上市公司的影响"等。即使用户只说"帮我分析一下最近的新闻"或"最近有什么大事影响投资"，也应使用本 skill。若用户提供了具体行业名，以用户指定行业为准；否则默认抓取中美关系、地缘局势、美联储、民生数据、高科技、生物医疗、云计算、AI产业链相关新闻。

以 digoal/德哥 的第一人称口吻重写一篇文章。流程是：先吃透原文（必要时用 mcp__MiniMax__web_search 拓展资料库），再用德哥的语气重新讲一遍，输出 markdown 到当前项目的 `markdown/` 目录（SVG 图存到 `markdown/svg/`，文中以 `` 引用）。风格有活人感，不要套用标准写作框架；匹配原文挑文体（随想/知识分享/深度洞察/吃瓜/大事件/吐槽）；开头必须有钩子（惊讶/惊喜/反直觉）；句子短，一行一句，适合口播；最多 3 段，能 1 段搞定就 1 段。类比时优先用数据库、AI、PG 内核、向量搜索、RAG、PG 运维这些德哥熟悉的领域。适用于：用德哥风格重写一篇公众号文章 / 把一份英文 paper/digest/blog 改写成中文公众号体 / 用德哥第一人称讲一件行业大事 / 让德哥吐槽某个产品或观点。