1.7万 件 ・ 関連度順
概要と使いどころ
Choose responsibility for substantial work before deep execution: keep one responsibility's coupled parts in a single lane, and hand a bounded or independent lane to a worker when clean context, an unknown cause, independent review, or coordinator attention materially improves the outcome.
日本語の概要は準備中です。原文の説明を表示しています。
Use for hands-on repository work when a quiet, risk-scaled engineering method can improve design, execution strategy, implementation, material incorporation, debugging, review, delegation, workspace lifecycle, or verification. Keep clear local changes direct, preserve the complete requested outcome, and add method only where risk or uncertainty justifies it. Do not use for general technical explanations, simple file lookup, casual discussion, or non-engineering writing.
日本語の概要は準備中です。原文の説明を表示しています。
Implement a settled request or current execution strategy through connected slices, feed observations into the same task record, and revise affected work when evidence changes.
日本語の概要は準備中です。原文の説明を表示しています。
Preview a Remotion video
日本語の概要は準備中です。原文の説明を表示しています。
Generative Engine Optimization plus agent readiness. Use this skill whenever the user asks about GEO, AEO, LLMO, optimizing content for AI search engines (ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, Copilot), getting cited by LLMs, brand mentions in AI responses, llms.txt, robots.txt for AI crawlers, Schema.org JSON-LD, FAST framework, agent readiness, MCP server discovery, Web Bot Auth, OAuth for agents, API Catalog, agentic commerce (x402, ACP, UCP), Markdown content negotiation, or auditing a site or page for AI visibility. Also trigger when the user says "AI SEO", asks how to "rank in ChatGPT", "show up in Perplexity", "appear in AI Overviews", or wants a site to "speak to AI agents". Trigger even when the request is implicit, such as "review this article so AI search picks it up" or "make our docs agent-friendly".
日本語の概要は準備中です。原文の説明を表示しています。
Compose, revise, validate, compare, inspect, and export original multi-track music as Standard MIDI with BeatFlow's compact, style-neutral Python DSL. Use for turning a musical brief into a deterministic Composition, testing explicit phrase/counterpoint/theme contracts, or inspecting MIDI.
日本語の概要は準備中です。原文の説明を表示しています。
Run a reusable opportunity-to-artifact workflow: discover unmet needs, set up workspace factories, schedule recurring commander/worker/reporter prompts, batch-refine many items, optionally use SQLite state, build small artifacts, review quality, and track outcomes. Use when the user wants to repeatedly create apps, games, products, content, or experiments from market/user needs.
日本語の概要は準備中です。原文の説明を表示しています。
Design, run, and review fair performance, token, and cost comparisons across GitHub Copilot CLI, Codex CLI, and direct model APIs. Use for AI CLI benchmark, Copilot vs Codex, prompt-cache diagnosis, cache read/write analysis, fresh-process latency measurement, token-cost comparison, or when a benchmark must separate provider caching from local CLI caches.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses a research paper outline (.qmd file) against structured criteria from Kosuke Imai's empirical research guide. Evaluates the abstract and section outline for: research question clarity, stated contributions, hypotheses and testable implications, data description, planned results and inferential approach, and robustness checks. Detects causal papers from the abstract and conditionally assesses identification strategy only when causal framing is present. Produces a structured markdown report with PASS/PARTIAL/FAIL assessments and actionable suggestions. Use when asked to assess, evaluate, review, or check a paper outline, abstract-and-outline, or research plan in a .qmd file.
日本語の概要は準備中です。原文の説明を表示しています。
Writes expert academic paper summaries for social science research, particularly political science and applied statistics. Use when asked to summarize, review, or create a reading summary of an academic paper, PDF, or research article. Accepts a file (PDF or text format) or a directory of papers. Produces a structured markdown summary — approximately 400–600 words — covering primary contributions, major questions and answers with point estimates, methods and data, and limitations and robustness. Includes BibTeX citation retrieved from Google Scholar and keyword metadata.
日本語の概要は準備中です。原文の説明を表示しています。
Live developer experience audit. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
"Design consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview. (gstack)".
日本語の概要は準備中です。原文の説明を表示しています。
Visual design audit for iOS apps on real hardware. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Apply narrative research methods to understand human experience through stories, analyzing narrative structure, temporality, and meaning-making in life stories and oral histories. Use this skill when the user needs to analyze how people construct meaning through storytelling, examine narrative structure and plot, conduct life story or oral history research, or when they ask 'how do stories shape identity', 'how do I analyze a life narrative', or 'what does this story reveal about experience'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply mechanism design (reverse game theory) to engineer incentive-compatible rules for allocation problems. Use this skill when the user needs to design auctions, voting systems, or matching markets, or when evaluating whether a proposed mechanism satisfies incentive compatibility and individual rationality constraints.".
日本語の概要は準備中です。原文の説明を表示しています。
Build accessible UI—semantic HTML, keyboard support, ARIA when needed, WCAG-oriented checks. Use when implementing or reviewing web UI, forms, modals, and design systems.
日本語の概要は準備中です。原文の説明を表示しています。
"Analyze inventory health using turnover ratios, ABC classification, safety stock calculations, and stockout vs overstock diagnostics. Use this skill when the user needs to optimize inventory levels, reduce carrying costs, prevent stockouts, or classify products by inventory priority — even if they say 'we have too much stock', 'we keep running out of bestsellers', 'how much safety stock do we need', or 'which products should we focus on'.".
日本語の概要は準備中です。原文の説明を表示しています。
Generate financial statements (income statement, balance sheet, cash flow) with period-over-period comparison and variance analysis. Use when preparing a monthly or quarterly P&L, closing the books and need to flag material variances, comparing actuals to budget, building a financial summary for leadership review, or looking up GAAP presentation requirements and period-end adjustments.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Bloom's revised taxonomy to classify learning objectives and design assessments across six cognitive levels. Use this skill when the user needs to write learning objectives at specific cognitive levels, align assessment with instructional goals, or evaluate curriculum for cognitive complexity distribution — even if they say 'how to write learning objectives', 'what level of thinking does this require', or 'higher-order thinking skills'.".
日本語の概要は準備中です。原文の説明を表示しています。
Split independent work across parallel agents with explicit boundaries and a parent integration review. Use only when user allows subagents and tasks do not share mutable files.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-source research on a customer question or topic with source attribution. Use when a customer asks something you need to look up, investigating whether a bug has been reported before, checking what was previously told to a specific account, or gathering background before drafting a response.
日本語の概要は準備中です。原文の説明を表示しています。
Security testing checklist for HTTP APIs—authn/z, input validation, rate limits, sensitive data exposure, and common OWASP API issues. Use when reviewing or testing REST/GraphQL endpoints before release.
日本語の概要は準備中です。原文の説明を表示しています。
"Corporate innovation-governance toolkit integrating Stage-Gate process, 3 Horizons model, innovation portfolio management, open innovation, corporate venture capital (CVC), innovation KPIs, and intrapreneurship. Use for innovation-portfolio design, second-curve planning, innovation-project review gating, open-innovation evaluation, CVC setup, innovation-KPI design, or managing tension between core and new businesses. Triggers: 『第二曲線』『創新專案怎麼管』『新事業孵化』『收購投資新創』『Stage-Gate』『研發投資組合』『內部創業』『開放式創新』『CVC』『3 Horizons』『創新 KPI』. For Taiwan EMBA innovation-management/strategy/technology-management cases (台大／中山). Startup basics: use Asgard `ux-lean-startup`; innovation theory: use Asgard `grad-disruptive-innovation`, `grad-ambidexterity`; 家族二代接班治理: use `biz-corporate-governance` 或 `ops-talent-strategy`; ESG/淨零策略結合: use `biz-net-zero-transition`.".
日本語の概要は準備中です。原文の説明を表示しています。