2,361 件 ・ 関連度順
概要と使いどころ
Crypto market scanner and single-token analyst - movers scans top winners/losers/trending or on-chain runners with pump-risk flags; single-token produces a verdict-first deep report for one token.
日本語の概要は準備中です。原文の説明を表示しています。
Review open PRs two ways - default is a per-PR deep review with severity-tagged findings, inline comments, and a verdict; --survey runs a risk-tiered triage digest of what's safe to merge first
日本語の概要は準備中です。原文の説明を表示しています。
Deep security audit of a smart-contract repo OR a live on-chain contract by address - detect Solidity, model the protocol invariants and trust boundaries first, run Slither (best-effort) plus a bounded agentic pass that hunts for a path breaking each invariant, triage, adversarially verify, prove with a fuzzer, and drive each finding through the shared responsible-disclosure routing. The dedicated contract arm split out of vuln-scanner.
日本語の概要は準備中です。原文の説明を表示しています。
An SEO agent skill for quick, lightweight, default single-page SEO audits. Performs basic on-page and site-level checks and outputs a structured basic SEO audit report. Use when the user asks for "SEO audit", "SEO check", "check my page SEO", "page analysis", or wants a first-pass review of a URL. If the user requests "deep audit", "full report", "technical SEO audit", or "advanced SEO", use seo-audit-full instead.
日本語の概要は準備中です。原文の説明を表示しています。
Deep Amazon review analysis for competitive intelligence and product improvement. Extract sentiment patterns, recurring complaints, feature requests, and competitive insights from customer feedback. Turn reviews into actionable product development and marketing strategies. Use when the user asks about review analysis, customer feedback, product complaints, sentiment analysis, or what customers think about products.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute substantial multi-file builds, features, migrations, and refactors with Astra as orchestrator and DeepSeek V4.1 Flash as the native Codex implementation worker. Use for phased planning and delegated build execution, including existing Superpowers or GSD plans. Skip trivial edits and explicitly single-agent tasks. Worker children must not invoke this orchestration skill.
日本語の概要は準備中です。原文の説明を表示しています。
Flatten deeply nested conditionals into readable, early-return code. Use on any function with 3+ levels of indentation.
日本語の概要は準備中です。原文の説明を表示しています。
Deep need-clarification skill. Use only when the user explicitly invokes $task-clarifier. Once activated, keep asking until all three goals are met: the user fully understands their own needs, the AI fully understands the user's needs, and the user confirms the AI's understanding is correct. Do not intervene in task execution unless explicitly invoked.
日本語の概要は準備中です。原文の説明を表示しています。
Craft a brand's origin story, founder narrative, and "why we exist" statement. Use when the user says "brand story", "origin story", "founder story", "why we exist", "about us", "our story", "company narrative", "brand narrative", "write our about page", "tell our story", "founding story", "brand history", or wants to articulate the deeper purpose and human story behind the brand. Also use when the About Us page feels generic or corporate and needs a rewrite.
日本語の概要は準備中です。原文の説明を表示しています。
Clean Code principles (DRY, KISS, YAGNI), naming, function design and readability. Use when code is hard to read, with long methods, unclear names, duplication or deep nesting. For how responsibilities are split across classes and which way dependencies point, use solid-principles instead.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user wants an evidence-based research memo, literature review, market/policy/technical landscape, or a multi-source decision brief with citations, trade-offs, and a clear conclusion. Best for tasks that need synthesis across multiple external sources, iterative follow-up research, or a reusable written artifact. Do not use for quick factual lookups, single-source summaries, simple Q&A, summarizing one document the user already provided, plan-only requests where the user explicitly defers the actual research, or when the user wants a short answer with no need for cited evidence (a short but evidence-backed conclusion is still a brief memo, which this skill covers). Chinese trigger examples: "帮我调研", "深度研究", "综述报告", "技术选型分析", "竞品研究", "政策分析".
日本語の概要は準備中です。原文の説明を表示しています。
资深产品经理助手，提供 PRD/MRD/BRD 创作与评审、产品策略、留存增长、竞品分析、功能优先级，以及 grill-me-to-doc 逐轮访谈。用户要求“逐个问我”“先把需求问清楚”“grill me”“把想法变成产品文档”时进入 grill-me-to-doc：先读仓库证据，每轮只问一个决策，给推荐答案与理由，记录决策和未决项，支持 resume，产出结构化 PRODUCT-DOC；文档完成且用户批准前硬停止，任何时候都不写实现代码。即使未提“产品”，讨论 App 功能、增长或商业模式也应触发。不用于：单纯代码实现、系统架构深设（用 solution-architect）、需多源引用的市场调研（用 deep-research）、纯营销文案。
日本語の概要は準備中です。原文の説明を表示しています。
PPT 生产 Agent：理解场景 → 推荐风格 → 先出大纲 → 定义页面 → 双通路交付（PPT 内容稿 / 逐页视觉图 / 信息图组图）。当用户要做汇报、路演、培训课件、提案、咨询报告的演示文稿，或要把大纲/文章做成 slides、deck、PPT、信息图、小红书图文、可视化传播图时使用。支持指定风格或从风格库推荐，支持 image 模型逐页出视觉稿。前身为 notion-infographic（v2）并吸收 ppt-designer 的设计原则。不用于：pptx 文件的纯技术操作（拆分/合并/提取，用宿主 pptx skill）、演讲稿或文章本体的写作（用 wechat-article-writer）、需要先做研究的内容调研（先走 deep-research 再回来）、单张海报或 logo 设计。
日本語の概要は準備中です。原文の説明を表示しています。
专业微信公众号文章助手，支持四个独立且可组合模式：article 写正文；image-prompts 从文章生成版本化、provider-neutral 的图片提示词 manifest 与稳定占位符，但不调用生图；layout 把文章和 manifest 确定性转换为微信安全的内联 HTML；full-pipeline 串联正文、提示词/占位符和排版。用户提到公众号、微信文章、推文、配图提示词、图片 manifest、公众号排版、内联 HTML 或完整图文流水线时触发。支持企业官号、个人技术博客、活动回顾和产品评测。不用于：带引用的研究报告（用 deep-research）、PPT/组图（用 deck-studio）、英文文章、仅润色一小段。永不自动发布，永不把提示词或占位符声称为已生成图片。
日本語の概要は準備中です。原文の説明を表示しています。
公众号运营｜微信公众号｜公众号一条龙｜公众号全流程｜自媒体运营｜wechat automation｜content pipeline｜AIGC workflow — 公众号一条龙运营总控入口，选题→写稿→审稿→排版→配图→发布串联 8 个子 skill，单条指令完成整篇图文从 0 到上架。面向公众号小编、自媒体、品牌内容。触发词分层：**一条龙流程**「一条龙」「完整流程」「从头做」「从 0 到发布」；**新做新发**「帮我写篇公众号文章」「做一篇公众号文章」「我想发一篇」「帮我发一篇」「再来一篇」；**选题起点**「今天写什么好」「有什么好写的」「找个话题」「爆款选题」「热点选题」「起个爆款标题」；**策划起点**「内容日历」「系列策划」「专栏规划」「连载」；**流程恢复**「接着上次那篇」「继续昨天的」「继续上次的」「接着之前的进度」；**显式模型新写**「用 GPT 写一篇」「用 DeepSeek 写一篇」「把提纲写成文章」。子 skill（topics/writing/review/formatting/images/publish/sticker/assets）单独触发仅限对**已有产物**的修改场景（如"改标题""润色这段""排版""审稿""加封面""发布"）；新做/策划/多环节串联一律走本入口。
日本語の概要は準備中です。原文の説明を表示しています。
Use after a phase's code is written, or when the user asks to review changed files for bugs, security issues, or quality. Spawns the gsd-code-reviewer agent at quick, standard, or deep depth and writes the phase REVIEW.md.
日本語の概要は準備中です。原文の説明を表示しています。
Deep knowledge for Outside-In TDD - double-loop architecture, ATDD integration, port-to-port testing, walking skeletons, and test doubles policy
日本語の概要は準備中です。原文の説明を表示しています。
25 real-world system design case studies condensed from Alex Xu's System Design Interview Vol 1 and 2 - requirements, architecture, deep dive insights, key takeaways
日本語の概要は準備中です。原文の説明を表示しています。
Question-first approach to understanding user journeys. Load when starting a new journey design or when the discovery phase needs deepening.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting work on a new product, client, or market — this skill creates the file `.agents/product-marketing-context-global.md` that 60+ other global skills read before they write anything: product, ICP, positioning, proof, objections, brand voice, pricing, and KPIs, with a region variant for US, EU, SEA, or LATAM. Run once, reuse forever. Trigger on 'set up marketing context', 'new client setup', 'onboard a new product', 'the AI does not know my product', 'US marketing context', 'EU GDPR setup', 'SEA market context', 'LATAM setup'. Also use when the user complains every answer comes back generic because nothing about the business was ever provided. Not for — a personal brand belonging to a founder, coach, or creator, see `22-personal-brand-context-global`; deep persona and JTBD research, see `09-customer-insight-global`; the period plan itself, see `00-marketing-plan-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to understand customers deeply enough to write copy and pick targeting — consumer versus shopper, JTBD, layered persona, internal monologue, pain map, objection list, journey map, and a customer language bank pulled from real reviews and DMs. Trigger on 'customer insight', 'buyer persona', 'who is my customer', 'what do they actually want', 'jobs to be done', 'why do they hesitate before buying'. Also use when the user cannot explain who the product is for. Not for — intake questions when an agency signs a new client, see `20-client-intake-brief-global`; paid audience targeting setup, see `51-audience-research-global`; competitor study, see `08-competitor-research-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default provider, preferred execution mode, and template choice. For deeper tweaks beyond the curated questions, users can hand-edit files in .atlas-ai/customizations/. Use when the user says "customise workflow", "customize workflow", "adjust my PRD settings", "tune the skill", or wants to change how prd-taskmaster behaves.
日本語の概要は準備中です。原文の説明を表示しています。
Expand all TaskMaster tasks with deep research before coding begins. Reads tasks.json, launches parallel research agents per task in waves using the research-expander agent. Writes findings back to tasks.json. Part of the prd-taskmaster toolkit. Use after PRD is parsed and before implementation. Invoke with /expand-tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.
日本語の概要は準備中です。原文の説明を表示しています。