8,037 件 ・ 関連度順
概要と使いどころ
Generate Azure environment monthly report (Markdown + PowerPoint) from Azure Advisor and Cost Management API. Use when creating Advisor recommendations report, cost trend analysis, or security/reliability assessment for a customer subscription. Triggers on 'Advisor report', 'Azure monthly report', 'subscription report', 'Azure環境レポート', '簡易月次レポート'.
Run a Duck Critic producer-critic loop: you (main) keep producing the plan/code/tests and gate your own work at checkpoints with a different-model critic, revising until it passes. Use when asked for rubber duck, ラバーダック, 別モデルレビュー, second opinion, critic, or a different-model code review, design review, plan critique, or review by another model/agent harness. Not for readability refactoring or code cleanup alone.
Operate a reusable technical book manuscript workspace with writing structure, reader persona SSOT, review rules, and optional Markdown to Re:VIEW/PDF support. Use when organizing a book manuscript repo, defining or reviewing target readers, standardizing chapter/section files, setting writing/review agents, handling publisher proof comments, or assessing an existing writing workspace. Triggers on book writing workspace, reader persona, reader audience, 読者ペルソナ, persona SSOT, technical book project, 執筆ワークスペース, manuscript workflow, Re:VIEW workspace, proof PDF, annotated proof, publisher proof comments, 校正, 校正注釈, and 初校.
Prose quality checker for Quarto (.qmd) files, grounded in William Zinsser's *On Writing Well* (30th Anniversary Edition). Checks for clutter, weak verbs, hollow qualifiers, clichés, inflated academic voice, poor leads and endings, pronoun and tense inconsistency, and unclear explanation. Produces a structured markdown report organized by document section — never modifies the source file. Use when asked to improve prose quality, tighten writing, reduce clutter, or apply Zinsser's writing principles to a draft. For grammar and punctuation, use the proofread skill. For APSA style rules, use the apsa-style skill. Supports an optional output-file argument and an optional @sec-label argument to restrict checking to one section.
日本語の概要は準備中です。原文の説明を表示しています。
"Conduct a systematic literature review following the PRISMA framework with explicit search strategy, inclusion and exclusion criteria, quality assessment, and transparent synthesis. Use this skill when the user needs to design a reproducible literature search, apply PRISMA flow documentation, develop inclusion and exclusion criteria, assess study quality, or when they ask 'how do I do a systematic review', 'what is PRISMA', or 'how do I make my literature review reproducible'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply spiral of silence theory (Noelle-Neumann) to analyze how perceived opinion climate suppresses minority expression. Use this skill when the user needs to understand why certain viewpoints disappear from public discourse, evaluate the role of fear of isolation in opinion expression, or assess opinion climate dynamics — even if they say 'why are people afraid to speak up', 'silent majority', or 'social pressure on opinions'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Efficient Market Hypothesis (Fama, 1970) to evaluate information incorporation in asset prices across weak, semi-strong, and strong forms. Use this skill when the user needs to assess market efficiency, determine if a trading strategy can generate abnormal returns, evaluate event studies, or when they ask 'can technical analysis work', 'does the market already know this', or 'is this anomaly exploitable'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Fama-French three-factor model to decompose asset returns into market, size, and value factors. Use this skill when the user needs to explain cross-sectional return differences, evaluate fund performance beyond CAPM alpha, assess small-cap or value tilts in a portfolio, or when they ask 'why do small caps earn more', 'is value premium real', or 'what factors drive returns'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the three-level framework of digital transformation — Digitization, Digitalization, and Digital Transformation — to diagnose and plan organizational change enabled by digital technologies. Use this skill when the user needs to assess an organization's digital maturity, distinguish between automating processes versus transforming business models, plan a DX roadmap, or when they ask 'where are we on digital transformation', 'is this digitization or real transformation', or 'how do we build a DX strategy'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply phenomenological methods including bracketing (epoche), lived experience inquiry, and Interpretive Phenomenological Analysis (IPA) to uncover the essence of human experience. Use this skill when the user needs to study how people experience a phenomenon from the first-person perspective, apply Husserlian descriptive or Heideggerian interpretive phenomenology, conduct IPA with idiographic focus, or when they ask 'what is the lived experience of X', 'how do I bracket my assumptions', or 'how do I do IPA'.".
日本語の概要は準備中です。原文の説明を表示しています。
"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'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Conduct SWOT analysis with TOWS matrix for strategic planning. Use this skill when the user needs to evaluate a company, product, or project by identifying strengths, weaknesses, opportunities, and threats, or wants to generate strategic options from internal and external factors. Also use when the user mentions competitive positioning, strategic assessment, or asks 'what are our advantages and risks', even without naming SWOT explicitly.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Porter's Five Forces framework to assess industry competitive dynamics and attractiveness. Use this skill when the user needs to analyze an industry's profitability structure, evaluate market entry barriers, assess supplier or buyer bargaining power, or understand competitive intensity — even if they say 'industry analysis' or 'is this market worth entering' without naming Porter's explicitly.".
日本語の概要は準備中です。原文の説明を表示しています。
"Calculate Cpk process capability index to assess whether a process meets specification requirements. Use this skill when the user needs to evaluate process capability, compare processes, or determine if quality targets are achievable — even if they say 'can our process meet spec', 'process capability', or 'Cpk calculation'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Conduct FMEA to systematically identify, prioritize, and mitigate potential failure modes. Use this skill when the user needs to assess product or process risks, prioritize corrective actions, or build a risk register — even if they say 'failure mode analysis', 'risk assessment', 'what could go wrong', or 'RPN calculation'.".
日本語の概要は準備中です。原文の説明を表示しています。
Assess identified vulnerabilities for exploitability, impact, and risk. Provide CVSS scoring and remediation strategies. Use when analyzing security findings.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-activates during requirements analysis to assess security risks using OWASP Top 10 framework, identify security requirements, and recommend mitigation strategies.
日本語の概要は準備中です。原文の説明を表示しています。
Audits whether a machine-readable regelrecht law model is faithful to the LETTER of the wettekst — and strictly separates the wettekst (leading) from the toelichting (Nota/Memorie van Toelichting; explanatory, not a norm). Runs in critical passes per article/lid and detects four deviation classes: toelichting-bleed (a modeled criterion that the letter only states as an open norm, or not at all), missing verbatim elements (a word/condition such as a "tenzij" or a qualifier dropped from the model), wrong legal_basis anchoring (an endpoint hung on a "kapstok"-article while the operative norm lives elsewhere), and verbatim-drift in text: (an ingetrokken/older redaction). Also detects positief-lid vs uitsluitings-lid conflicts and checks the chapeau for an explicit derogation rule ("zo nodig in afwijking van het eerste lid") before judging precedence. Classifies every finding as modelfout (fix), wettekst-gevolg (report, do not fix), or letter-vs-toelichting-question (jurist decides what is leading + revision signal). Use when the user wants to know if a model is "dicht bij de letter", mentions letter vs toelichting/bedoeling, fidelity, "natuurgetrouw", or before trusting feature outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Open the warm channel for a role the pipeline already assessed. Finds who the user already knows at the company, researches named targets from public professional presence when they know nobody, grades each path honestly, drafts the ask through the voice agent, and writes the contacts into the Referrals table in job_search.md.
日本語の概要は準備中です。原文の説明を表示しています。
Map existing business processes using BPMN 2.0 notation or simplified swimlane diagrams. Identify waste, handoffs, decision points, and improvement opportunities using Lean principles (8 Wastes). Use when documenting workflows for SOP creation, automation assessment, or process improvement. Do not use for software architecture diagrams — use architecture tools instead.
日本語の概要は準備中です。原文の説明を表示しています。
Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Turn launch dates, campaign inputs, and asset requests into a structured content calendar and workback plan. Use when the work is recurring marketing coordination and schedule packaging. Do not use for brand strategy, positioning design, or deep performance interpretation.
日本語の概要は準備中です。原文の説明を表示しています。
Use this agent when you need to review UniProt annotation rules (ARBA, UniRule) for quality, biological accuracy, and GO annotation appropriateness. This agent performs comprehensive analysis of rule condition sets, evaluates literature support, assesses taxonomic scope, and recommends curation actions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when developing Thunderbird MailExtensions - Manifest V2/V3 configuration, messenger.* APIs for accounts, messages, folders and compose, UI actions, message display scripts, Experiment APIs, ATN submission, or migration from legacy extensions
日本語の概要は準備中です。原文の説明を表示しています。