1,400 件 ・ 関連度順
概要と使いどころ
Automatically assess task complexity and adjust reasoning level. Triggers on every user message to evaluate whether extended thinking (reasoning mode) would improve response quality. Use this as a pre-processing step before answering complex questions.
日本語の概要は準備中です。原文の説明を表示しています。
Verify and write proofs using the Acorn theorem prover for mathematical and cryptographic formalization. Use when working with Acorn proof files (.ac), verifying theorems, formalizing mathematical or cryptographic protocols, or writing proofs in the Acorn language. Triggers on: (1) Creating or editing .ac files, (2) Running acorn verify commands, (3) Formalizing math or crypto proofs, (4) Questions about Acorn syntax or standard library.
日本語の概要は準備中です。原文の説明を表示しています。
Generate synthetic code context for LLM coding tasks. Automatically use this before making code changes, fixing bugs, refactoring, or answering questions about the codebase. Provides execution paths, relevant files, symbols, tests, and code snippets.
日本語の概要は準備中です。原文の説明を表示しています。
Uses the local pruner indexer to gather relevant code context before making changes, debugging, refactoring, or answering questions about this repository.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.
日本語の概要は準備中です。原文の説明を表示しています。
Web search and research using Perplexity AI. Use when user says "search", "find", "look up", "ask", "research", or "what's the latest" for generic queries. NOT for library/framework docs (use Context7) or workspace questions.
日本語の概要は準備中です。原文の説明を表示しています。
Implement signal-based reactive state management in Angular v20+. Use for creating reactive state with signal(), derived state with computed(), dependent state with linkedSignal(), and side effects with effect(). Triggers on state management questions, converting from BehaviorSubject/Observable patterns to signals, or implementing reactive data flows.
日本語の概要は準備中です。原文の説明を表示しています。
Reference guide for using Xpoz effectively. Load this skill whenever working with Xpoz MCP tools, SDKs, or CLI — it ensures correct query syntax, optimal field selection, proper pagination, and best practices for every Xpoz interaction. Covers authentication, query syntax (boolean operators, date filtering), response modes (fast/paging/CSV), field selection, tracking setup, and all platform tool references (Twitter, Instagram, Reddit, TikTok). Use for ANY Xpoz-related work, not just explicit best-practices questions.
日本語の概要は準備中です。原文の説明を表示しています。
One-shot GEO visibility check for a brand using Xpoz. Runs the buyer questions that matter through Claude, ChatGPT, and Gemini, and reports where the brand appears, who wins instead, and which surfaces the answers are assembled from. Use when asked to "check my AI visibility", "does ChatGPT recommend us", "GEO audit", "where do we show up in AI answers", or "who wins our category in AI answers".
日本語の概要は準備中です。原文の説明を表示しています。
方案拷问 / 压力测试：当用户有一个产品方案、架构设计、计划或决策，想被连续追问、反方挑战、 压测取舍和失败模式时使用。可用中文唤起：“拷问我的方案”“压力测试这个设计”“帮我问 hard questions” “这个方案哪里会翻车”“grill me”。目标是一问一答把决策树走清楚，不是直接替用户写最终方案。 跨 Skill 运行时只输出 Challenge/Critic Handoff，并把一个 gap 返回最小责任节点；不重写完整方案。 如果用户还不知道真正问题是什么，先用 ai-collaboration-calibration；如果用户要标准 PRD 交付准备度评审， 用 prd-review。
日本語の概要は準備中です。原文の説明を表示しています。
Use when facing SEO algorithm questions, content strategy decisions, Threads growth planning, GEO optimization, AI tool selection for SEO, or evaluating SEO vendors. Triggers on any algorithm or content marketing decision — even without mentioning darkseoking. Every insight is backed by patent numbers or tested data.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts a Petition for Writ of Certiorari to the U.S. Supreme Court under Rules 10, 13, 14, and 33. Enforces Rule 10 criteria (circuit splits, precedent conflicts, important federal questions), jurisdictional verification under 28 U.S.C. §§ 1254/1257, timeliness, document structure, and booklet formatting. Use when seeking discretionary Supreme Court review, filing a cert petition, or drafting a writ of certiorari.
日本語の概要は準備中です。原文の説明を表示しています。
Generate customer-facing answers for common legal services questions. Use when working on FAQ content for legal ops teams, attorneys, compliance teams.
日本語の概要は準備中です。原文の説明を表示しています。
在采购或开工之前，对拟议 AI 应用做一次结构化初始问询，产出「可继续 / 需补齐 / 不可按此形态部署」三种结论与带责任人和期限的行动清单。 方法论移植自波兰个人数据保护局（UODO）2026-08-05《初始问题清单》。覆盖 GDPR 与 AI Act 信号提示，适用于出海与境外 AI 项目； 中国大陆境内 AI 用例的红线与备案判断请走 ai-governance-use-case-triage。
日本語の概要は準備中です。原文の説明を表示しています。
Answer factual project questions (codebase, architecture) with cited evidence. NOT for brainstorming, trade-offs (mk:party), debugging (mk:investigate), review (mk:review), or plans (mk:plan-creator).
日本語の概要は準備中です。原文の説明を表示しています。
YC Office Hours — product validation for a new product, feature, or side-project concept. Startup mode tests demand; Builder mode develops an unvalidated product idea. Use when the user asks whether something is worth building or has an idea whose problem/value is not yet validated. Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use BEFORE a plan exists. For reviewing an existing plan, use /mk:plan-ceo-review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when answering factual or explanatory questions about the current project — codebase, architecture, conventions, workflows, constraints — with minimal cited evidence. Triggers on "how does X work here", "what does X mean", "why is X structured this way", "is this claim true in the repo", "explain X with sources". NOT for brainstorming or comparing approaches (mk:brainstorming), trade-off decisions (mk:party), debugging/root cause (mk:investigate), code review (mk:review), plans (mk:plan-creator), security audits (mk:cso), visual explanations/diagrams (mk:preview --explain), test-coverage gaps (mk:nyquist), library docs (mk:docs-finder), or workflow navigation (mk:help).
日本語の概要は準備中です。原文の説明を表示しています。
Relentlessly interview the user about THEIR plan or design — one question at a time — resolving each branch of a decision tree until shared understanding. Claude is the interviewer; the user is the interviewee. Triggers on "grill me", "stress-test this plan", "get grilled on my design", "interrogate my plan". Checkpoints every answer to docs/knowledge/<slug>.md so progress survives a context-window reset. Flags knowledge the user cannot answer as a gap to chase. Do NOT use to PROPOSE solutions or compare approaches (→ mk:brainstorming). Do NOT use to validate "is this worth building?" (→ mk:office-hours). Do NOT use when Claude should ANSWER questions about the repo (→ mk:ask-me). Do NOT use for a one-shot review of an existing plan (→ mk:plan-ceo-review). Do NOT use to apply named reasoning lenses to findings (→ mk:elicit).
日本語の概要は準備中です。原文の説明を表示しています。
Generate a grounded Human Design BodyGraph and whole-chart reading from exact birth data. Use for Human Design charts, BodyGraph, decisions, profile, channels, talents, work, wealth, relationships, mission, or chart-based follow-up questions. Supports Chinese and English.
日本語の概要は準備中です。原文の説明を表示しています。
Use the project wiki as RAG knowledge source — search wiki pages to answer codebase questions before exploring raw files
日本語の概要は準備中です。原文の説明を表示しています。
YC-style product strategy assessment with forced questions and CEO scope modes — adapted from gstack /office-hours pattern
日本語の概要は準備中です。原文の説明を表示しています。
Pre-routing ambiguity analysis — scores request clarity and asks clarifying questions when needed (inspired by ouroboros)
日本語の概要は準備中です。原文の説明を表示しています。
Assess the reliability of companies and individuals through Openapi Risk - credit scores, CRIF reports, patrimonial reports, negative events, heirs reports, worldwide KYC (PEP, sanction lists, adverse media). Use for due diligence, creditworthiness, AML/KYC questions.
日本語の概要は準備中です。原文の説明を表示しています。
Look up company/business data through Openapi - Italian companies by VAT/tax code or name, European and worldwide company search, shareholders, UBO, AML, PEC/SDI codes, company monitoring. Use for questions like "find data about company X", "who owns VAT number Y", "search companies in France/EU/worldwide".
日本語の概要は準備中です。原文の説明を表示しています。