2,450 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Capture durable project or workflow knowledge discovered during work. Use when a mistake, hidden constraint, repeated question, or changed behavior reveals a documentation gap. To root-cause one specific mistake the agent just made and let the user pick fixes, use `learn` (`/learn`) instead.
日本語の概要は準備中です。原文の説明を表示しています。
Review every Beads issue waiting on a person, one at a time, using the interactive questionnaire UI rather than plain-text prompts. Use when asked to go through blockers, clear the human queue, answer beads waiting on the user, triage `bd human list`, or unblock agent work that needs a decision.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Generate contextual briefings for legal work. Supports three modes — daily brief (morning summary of legal-relevant items), topic brief (research synthesis on a specific legal question), and incident brief (rapid briefing for developing situations like data breaches or regulatory inquiries).
日本語の概要は準備中です。原文の説明を表示しています。
Drafts the "Interest of Amicus Curiae" section of an amicus brief. Establishes institutional credibility, tethers the amicus's interest to the specific legal question, articulates non-party impacts, and embeds disclosure guardrails under FRAP 29 and Supreme Court Rule 37. Trigger when drafting amicus briefs, friend-of-the-court filings, interest statements, amicus disclosures, or when the user asks why an organization belongs in a case.
日本語の概要は準備中です。原文の説明を表示しています。
China legal triage assistant. Input a contract, labor dispute facts, lawsuit-cost question, or draft legal document need; output risk checklist, cost estimate, evidence outline, or editable document skeleton. Boundary: preliminary legal information only, not a lawyer and not formal legal advice.
日本語の概要は準備中です。原文の説明を表示しています。
在采购或开工之前，对拟议 AI 应用做一次结构化初始问询，产出「可继续 / 需补齐 / 不可按此形态部署」三种结论与带责任人和期限的行动清单。 方法论移植自波兰个人数据保护局（UODO）2026-08-05《初始问题清单》。覆盖 GDPR 与 AI Act 信号提示，适用于出海与境外 AI 项目； 中国大陆境内 AI 用例的红线与备案判断请走 ai-governance-use-case-triage。
日本語の概要は準備中です。原文の説明を表示しています。
Relentlessly interview the user about THEIR plan, one question at a time, until shared understanding. Checkpoints answers so progress survives a reset. Do NOT use to propose solutions.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a raw idea into ONE honest recommendation: interview one question at a time until confirmed, then give a verdict with trade-offs and a checklist. Not for options or debate.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. Use AFTER a plan exists. For validating the idea itself before planning, use /mk:office-hours first.
日本語の概要は準備中です。原文の説明を表示しています。
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)
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use when stuck on a hard problem, decomposition is unclear, a related problem is needed, or explicit looking-back review will improve transfer. NOT for routine execution with a known procedure, rote checklist work, or domain questions that need specialized subject matter expertise instead of heuristic search.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure HIPAA compliance when handling PHI (Protected Health Information). Use when writing code that accesses user health data, check-ins, journal entries, or any sensitive information. Activates for audit logging, data access, security events, and compliance questions.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-skill that orchestrates the discourse skill suite: routes between steel-man-argument, socratic-questioning, toulmin-argument-analysis, logical-fallacy-detector, bad-faith-rhetoric-detector, discourse-elision-analyzer, forensic-speech-structure, and productive-discourse-facilitator. Use when analyzing conversations, facilitating discourse, or operating as a dialogue copilot. Maintains mode (silent analysis, coaching overlay, active facilitator) and decides which skills to invoke based on conversation dynamics.
日本語の概要は準備中です。原文の説明を表示しています。