1,999 件 ・ 関連度順
概要と使いどころ
Report how many problems the two brains found: mutual review (the other model checks the work, from the peer-review records) and self-check (an agent finds its own error in its own conversation, judged by that agent's own model), side by side. Use when the owner asks whether the second agent or the reviews are worth it, or wants the week's review results.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial review and fix loop for code, specs, plans, and migration manifests.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate Agent Skill design quality with an opinionated, practice-derived rubric informed by public specifications and examples. Use when reviewing, auditing, comparing, or improving SKILL.md files and skill packages. Produces evidence-backed findings, optional multi-dimensional scoring, and prioritized changes; treat the result as diagnostic guidance, not official certification or a universal standard.
日本語の概要は準備中です。原文の説明を表示しています。
Integrating Global Privacy Control (GPC) signals with cookie consent platforms. Covers GPC signal detection in browsers, automatic opt-out triggering, mapping GPC to US state privacy laws, and CMP integration for CCPA, CPA, and CTDPA compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution.
日本語の概要は準備中です。原文の説明を表示しています。
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.
日本語の概要は準備中です。原文の説明を表示しています。
备考教练的一屏速查卡：工作流、3×4 学习选择、产物偏好、工作区文件、6 大题型、来源规则与子技能路由。 用户问怎么用、有哪些模式、文件用途或支持题型时使用。
日本語の概要は準備中です。原文の説明を表示しています。
考前复盘已记录错题与概念疑难：重做原题、复述疑难、更新已订正/已回顾/待回顾状态，并形成最后扫雷清单。 进入最终复习阶段或用户要求复盘、查漏补缺时使用。
日本語の概要は準備中です。原文の説明を表示しています。
全员通关后把 错题本+笔记本+知识点窗口+wiki 编译成考前速记小抄 cheatsheet.md（每条要点带可溯源 锚点），并在视觉产物模式或用户明确要求 PDF/打印版时按指定页数渲染成打印级 PDF：按「必背结论/公式 → 有难度例题（必要时含题面图）→ 例题解答（代入公式、保留基础过程）→ 要点解释（同类题怎么办）」 四段组织。当复习收尾、用户要「考前小抄/速记/总结/打印版」时使用。
日本語の概要は準備中です。原文の説明を表示しています。
只读检查一个已生成的备考工作区是否健康并报告问题，默认不做任何修改。核对 .ingest 原材料版本、 内容单元、接管队列与派生产物完整性，以及 wiki、题库、视觉证据、计划和进度的一致性。当用户怀疑 工作区有问题、建库 readiness 被阻断、或想在开始复习前体检时使用。
日本語の概要は準備中です。原文の説明を表示しています。
从 references/quiz_bank.json 抽取本章题目并按标准答案判分，支持选择、主观、画图、填空、判断、代码； 主观题按 keywords 要点覆盖判分，连续错两次提供提示/跳过/归档。禁止现场编题。用于阶段检查或模考。
日本語の概要は準備中です。原文の説明を表示しています。
教学过程中自动捕获和记录学习者的概念疑难点（"为什么/是什么/怎么推/什么意思"类型的问题），保存到进度文件的"概念疑难点记录"区，形成考前回顾清单。
日本語の概要は準備中です。原文の説明を表示しています。
按章节惰性加载授课：每次只读当前阶段的一个 wiki 章节，用生活隐喻讲概念、解剖公式；重点题固定走 题面图→问题→读图量→公式→演算→答案详解→溯源七步，画图题先运行算法。用于讲懂当前章或老师勾出的重点题。
日本語の概要は準備中です。原文の説明を表示しています。
从学生上传的课件/大纲/老师勾的重点/真题，一键初始化并验证备考工作区：解析 PDF、DOCX、PPTX、 XLSX、常见独立图片与 txt/md，建立分章节 LLM Wiki、标准题库、结构化接管队列与进度状态；仅在 Python 确实无法运行时 明确降级为手动写盘。当工作区尚未建立、资料发生变化、或建库 readiness 被阻断时使用。
日本語の概要は準備中です。原文の説明を表示しています。
将已经讲完但尚未完成阶段门禁的一个章节整理成强类型教材清单，并在视觉模式下编译为公式可读、图片可见、知识点与全部对应例题逐项精讲的自包含 HTML/PDF。结构化工作区准备阶段完成证据、用户说 Markdown 公式仍是 raw LaTeX、图片缺失、要含课件/作业/Quiz/模拟考试题及答案的零基础讲义，或要求打印版时使用。
日本語の概要は準備中です。原文の説明を表示しています。
临考前的极速备考总教练。把课件、大纲、重点与真题建成分章 wiki 和标准题库，再组织惰性授课、 题库判分、错题与疑难复盘及可选考前小抄，并持久化进度。用于期末、备考、突击、刷题、划重点、 错题与考前复习；不用于长期规划或与考试无关的写作/编程。
日本語の概要は準備中です。原文の説明を表示しています。
Art direction for open world and sandbox games in Blender with biome landmarks, traversable scale, and discovery props.
日本語の概要は準備中です。原文の説明を表示しています。
Interact with Slack — read channels, search messages, check unreads, send messages, manage reactions, and look up users. Use this skill whenever the user mentions Slack, wants to read Slack messages, check unread channels, search Slack conversations, send a Slack message, add reactions, or look up Slack users. Also trigger when the user pastes a Slack message URL, mentions a Slack channel (#channel), or asks about Slack notifications.
日本語の概要は準備中です。原文の説明を表示しています。
Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or goal it serves for the business or a user), and from there what it does, how it flows, and where to start — so you can get up to speed before working on or reviewing it. Use when you want to understand, get oriented in, make sense of, explain, or get up to speed on a chunk of code, a file, a directory, a symbol, or a PR's changes. Writes the overview to a scratch file and changes no code. Does not review code quality or raise findings — use code-review for auditing changes or post-code-review-to-pr for posting them. Does not produce durable feature or system documentation — use project-documentation. Does not assess architecture or structural risk — use architectural-analysis. Does not diagnose bugs or root-cause failures — use investigate. Does not pace a person through the code one step at a time in conversation — use code-walkthrough.
日本語の概要は準備中です。原文の説明を表示しています。
Surfaces Han's shared Human-Readable Output Standard — the readability rule and the writing-voice profile — into the calling skill's own context, so the caller drafts in voice and runs its self-check against the current standard sourced from one canonical copy. Use when a prose-producing skill needs the shared readability standard available in context before it drafts. Governs the shape of a written deliverable, where explanation-guidance governs what a run says to a person in a turn. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Does not run the adversarial rewrite pass — dispatch the readability-editor agent for that, or use edit-for-readability to rewrite an existing target. Does not cover explaining technical work to a reader who will not implement it — use explanation-guidance for that.
日本語の概要は準備中です。原文の説明を表示しています。
Designs the contract for an API change inside one codebase — a component's props, a function surface, URL or query parameters, an event payload, or a module boundary — through a discovery pass, an options document with one recommendation, a question round, and an adversarial validation round, with every element of the contract justified from one stated goal. Use when you want to design, shape, decide, or nail down an interface, contract, signature, or API change for a capability you can already describe, sized for roughly one pull request. Produces a design document and changes no code. Does not specify what a feature should do — use plan-a-feature. Does not plan delivery or sequencing — use plan-implementation. Does not assess the architecture of existing code — use architectural-analysis. Does not write the code — use tdd. Does not restructure existing code — use refactor. Runs its rounds without pausing for review; to review each round as it lands, use pairing.
日本語の概要は準備中です。原文の説明を表示しています。
Walks a person through code changes one step at a time in conversation, starting at the entry point and following the flow that changes, showing a small chunk per step and explaining it in plain language. Defaults to the current branch's changes, and walks the code from the perspective of any context provided instead — a file, directory, symbol, pull request, plan, or ticket. Use when someone wants to be walked through, taught, paced through, or shown around code or a branch step by step, or to learn how a change works before reviewing or extending it. Stops after every step and waits, so the learner sets the pace. Paces through code that already exists and builds nothing — to build new work while being paced through it, use pairing. Does not produce a written overview to read alone — use code-overview. Does not review code quality — use code-review. Does not diagnose bugs — use investigate.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a feature implementation plan from an existing feature specification (or equivalent context) through a facilitated team conversation. Use when the user wants to plan how to implement, build, deliver, or ship a feature that has already been specified. Does not specify what the feature should do — use plan-a-feature first. Does not design the contract for an interface — use design-an-api. Does not refine or stress-test an already-written plan — use iterative-plan-review. Runs its resolution rounds to completion and holds its questions until after they finish; to review each round as it lands, use pairing.
日本語の概要は準備中です。原文の説明を表示しています。