「assessment」の検索結果

Move quality earlier in the development lifecycle. Covers dev/QA pairing patterns, Three Amigos sessions, TDD facilitation (Red-Green-Refactor), PR review checklists for testability, and Definition of Done with quality gates. Includes shift-left maturity model for team assessment. Use when: "shift left," "TDD," "dev-QA pairing," "definition of done," "testability," "quality culture," "QA in sprint planning." Not for: writing the unit tests themselves — use unit-testing; automated PR test-quality review at scale — use ai-qa-review; multi-quarter QA direction or roadmap — use test-strategy. Related: unit-testing, ai-qa-review, test-strategy.

日本語の概要は準備中です。原文の説明を表示しています。

Surface risks through guided questioning, helping users consider pivots, constraints, and prioritization during PRD v0.5 Red Team Review. Triggers on requests to identify risks, stress-test the idea, perform red team review, or when user asks "what could go wrong?", "identify risks", "red team", "risk assessment", "challenge assumptions", "stress test the idea". Consumes all prior IDs (CFD-, BR-, FEA-, PER-, UJ-, SCR-) as interview context. Outputs RISK- entries with owner decisions and mitigations. Feeds v0.5 Technical Stack Selection.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in designing and structuring online courses - curriculum architecture, learning outcomes, module design, and assessment strategies. Covers backward design methodology, scaffolding content, and creating courses that actually deliver transformation. Use when "create a course, course curriculum, course outline, learning outcomes, course structure, design a course, online course, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in decision-making frameworks - systematic approaches to making better decisions under uncertainty. Covers decision criteria, reversibility assessment, stakeholder alignment, and decision documentation. Knows when to decide fast and when to deliberate. Use when "decision framework, how to decide, making a choice, tradeoff, should we, pros and cons, decision matrix, weighing options, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Work with climate data, models, and projections for climate impact assessment, downscaling, and scenario analysis using CMIP6 and other climate datasets. Use when "climate model, climate projection, CMIP6, climate data, downscaling, climate scenario, RCP, SSP, global warming, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarksUse when "agent testing, agent evaluation, benchmark agents, agent reliability, test agent, testing, evaluation, benchmark, agents, reliability, quality" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Backlink profile audit via the DataForSEO Backlinks API. Returns total backlinks, referring domains, dofollow ratio, top anchors with over-optimization flags, top referring domains by authority, and a toxicity assessment with an Authority Score (0-100).

日本語の概要は準備中です。原文の説明を表示しています。

Unified multi-platform paid media audit with parallel execution. Spawns scored audits for Google Ads, Meta Ads, and Microsoft Ads simultaneously, merges results into a budget-weighted aggregate health score (A-F), adds cross-platform analysis (budget allocation, tracking consistency, creative alignment, attribution overlap), and produces a prioritized action plan. Optionally generates a client-ready deck via pro-deck-builder. Use when the user asks for a full paid media audit, cross-platform review, or multi-channel ad assessment.

日本語の概要は準備中です。原文の説明を表示しています。

Create polished HTML technical reports and multi-page documents for consulting deliverables. Includes a customizable design system with dark cover page, warm cream content pages (8.5x11 portrait), professional typography, and a curated component library (KPI cards, data tables with severity coloring, callout boxes, recommendation cards, priority banners). Trigger on report, audit report, technical document, written report, assessment, or multi-page document. Outputs standalone HTML files exported to PDF via Chrome headless.

日本語の概要は準備中です。原文の説明を表示しています。

Documents rollback procedures before making risky changes. Covers what's changing, verification steps, rollback procedures, and blast radius assessment. Use before database migrations, breaking API changes, infrastructure or DNS changes, large dependency upgrades, or any change where undo is not obvious.

日本語の概要は準備中です。原文の説明を表示しています。

Advanced Evaluation workflow skill. Use this skill when the user needs This skill should be used when the user asks to "implement LLM-as-judge", "compare model outputs", "create evaluation rubrics", "mitigate evaluation bias", or mentions direct scoring, pairwise comparison, position bias, evaluation pipelines, or automated quality assessment and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Advanced Evaluation workflow skill. Use this skill when the user needs This skill should be used when the user asks to "implement LLM-as-judge", "compare model outputs", "create evaluation rubrics", "mitigate evaluation bias", or mentions direct scoring, pairwise comparison, position bias, evaluation pipelines, or automated quality assessment and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluate third-party vendors for engineering fit. Use when a senior developer needs a structured vendor assessment.

日本語の概要は準備中です。原文の説明を表示しています。

Perform threat modeling for a system or feature. Use when a senior developer needs security risk assessment.

日本語の概要は準備中です。原文の説明を表示しています。

Audit dependencies for licensing, security, and maintenance risk. Use when a senior developer needs risk assessment.

日本語の概要は準備中です。原文の説明を表示しています。

Assess a system for growth bottlenecks. Use when a senior developer needs to evaluate scaling limits.

日本語の概要は準備中です。原文の説明を表示しています。

临床诊断思维 (临床诊断思维 / 临床推理 (Clinical Diagnostic Reasoning) — 医生『怎么想病』的元学科:从症状/体征/检查到诊断结论的认知操作系统,从业者(临床医生/住院医/规培生,尤其全科/急诊/大内科等以未分化主诉为生的科室)、医学生与医学教育者、诊断安全与质量改进研究者、以及做医疗 AI 辅助诊断产品的人的视角。覆盖: (a) 第一性张力 — **直觉模式识别 (System 1: illness scripts 疾病脚本 / pattern recognition / gestalt, 『资深人一眼认出 aunt Minnie』) ⇄ 分析性推理 (System 2: hypothetico-deductive 假设演绎 / Bayesian 概率更新)** 的 dual-process 双过程理论 (Kahneman→Croskerry/Norman 谱系), 资深≠更会分析而是『脚本库更大+校准更好』; 更深层论战 — **『认知去偏可教 (Croskerry: bias awareness / cognitive forcing strategies / diagnostic timeout) ⇄ 偏倚标签是马后炮、知识结构才是主因 (Norman/Sherbino/Monteiro: debiasing 干预 transfer 证据弱, bias 是 hindsight 标签)』** — 本行最核心学术对垒; 『概率思维 (验前概率 × 似然比 → 验后概率, Pauker-Kassirer test/treatment threshold 阈值模型) ⇄ 穷尽式排查 (rule-out everything / 防御性医疗 / VOMIT)』; 『临床 gestalt ⇄ 结构化临床决策规则 (Wells/PERC/HEART)』; 『诊断简约 Occam's razor ⇄ Hickam's dictum (病人可以同时得 N 个病)』; 『床旁体格检查复兴 (Verghese Stanford 25 / McGee 循证体检) ⇄ 影像检验替代床旁』; (b) 方法论正典 — illness script theory (Schmidt/Boshuizen: enabling conditions/fault/consequences 三段结构), problem representation + semantic qualifiers 问题表征与语义限定词 (Bowen NEJM 2006, 把病人翻成 one-liner), hypothetico-deductive model (Elstein 1978《Medical Problem Solving》: 早期假设生成+定向检验), Bayesian 工具箱 (sensitivity/specificity/LR/Fagan nomogram/SnNout-SpPin), threshold model (Pauker-Kassirer NEJM 1975/1980), 认知偏倚分类学 (anchoring/premature closure/availability/confirmation/base-rate neglect/search satisficing/diagnostic momentum — Croskerry 偏倚清单), 去偏与元认知策略 (diagnostic timeout/cognitive forcing/Ely checklist/calibration), schema-based reasoning (Clinical Problem Solvers schemas: 按 pivot 症状走分支), reflective practice 结构化反思 (Mamede/Schmidt), 诊断错误科学 (NAM 2015 报告定义 / Newman-Toker Big Three / Hardeep Singh e-triggers / SAFER Dx 框架); (c) 行业结构与角色 — 医学生→实习/住院医 (晨会 morning report/查房被 pimping/汇报训练)→主治 attending→master clinician (NEJM CPC discussant/晨会大师如 Dhaliwal); 配套生态: 医学教育者 (clinical reasoning curriculum + 评估: script concordance test/key features exam/OSCE), 诊断安全研究者 (SIDM/AHRQ), 诊断辅助与 CDS 工具开发者 (DDx generator/AI); (d) 核心工作流 — 数据采集 (病史为王 + 循证体检 + 针对性检验影像) → 问题表征 (one-liner + semantic qualifiers) → 鉴别诊断生成 (schema / 解剖定位法 / VINDICATE-M 病因筛, 按『常见可能 × 致命不能漏 can't-miss』双轴排序) → 假设定向检验 (按 LR 选检查 / 阈值决策) → working diagnosis + 安全网 (red flags 交代 / test of time / test of treatment) → 反馈校准 (follow-up / M&M / diagnostic timeout); 教学工作流: 晨会渐进披露汇报 / CPC / SNAPPS / one-minute preceptor / virtual morning report; AI 增强工作流 (2023-2026: LLM 鉴别诊断头脑风暴 / OpenEvidence 检索 / ambient scribe 释放认知带宽 + 自动化偏倚 guardrails); (e) 产出物 — one-liner, problem list, prioritized DDx, assessment & plan (按问题分层), 晨会/CPC 汇报, M&M 复盘, 诊断不确定性沟通 (『最可能是 X, 但出现 Y 红旗立刻回来』); (f) 教育与评估 — script concordance test / key feature exam / EPA / 里程碑; 中国语境: 人卫《诊断学》教材 / 执业医师考试 / 规培结业临床思维考核; (g) 争议/批判 — debiasing 之争 (Croskerry vs Norman-Sherbino『knowledge is the cure』, 去偏 RCT 效果弱 / bias 标签不可证伪), 诊断错误率数字之争 (『10-15%』经典估计 / Newman-Toker 79.5 万美国年严重伤害外推方法被质疑 / 尸检符合率), dual-process 二分被批过度简化 (连续谱 / 难以实证分离), 决策规则 vs gestalt (资深 gestalt 常不输 Wells 类规则 / 算法厌恶), vignette 研究外推性 + context/case specificity (推理高度内容绑定不可通用迁移 [Norman/Eva] — 对『教推理通用课』产业的根本批判), AI 辅助诊断 2023-2026 (GPT-4 在 NEJM CPC/vignette 追平或超医生 [Kanjee 2023 JAMA / Goh 2024 JAMA Netw Open『AI alone > physician+AI』悖论] / Google AMIE / OpenEvidence 爆发 vs 自动化偏倚 / 去技能化 / 真实环境验证缺失), 防御性医疗与过度检查 (incidentaloma 瀑布 / VOMIT), 体检衰亡之争, pimping 教学法争议; (h) 流派/思想谱系 — 决策科学/Bayesian 派 (Ledley-Lusted 1959 → Elstein/Kassirer/Sox/Pauker/Eddy → Brush) vs 认知心理/双过程派 (Kahneman-Tversky → Croskerry/Graber) vs 教育认知派 (Schmidt/Boshuizen illness scripts → Norman/Eva/Mamede/Durning 情境认知) vs 诊断安全/系统派 (NAM 2015 / Newman-Toker / Hardeep Singh / Graber-SIDM: 错误=系统×认知共因) vs 床旁临床派 (Osler 传统 → Tierney aphorisms / Verghese / McGee / Dhaliwal / Saint: 病史体检为王 + 刻意练习) vs AI/计算派 (INTERNIST-1/DXplain 专家系统 → Isabel → LLM 世代 Rodman/Topol)。不含: 具体专科治疗方案与手术决策深度 (足踝外科/种植牙等另有 skill), 中医辨证 (另有 skill), EBM 文献批判性评价方法学 (相关但本 skill 聚焦诊断推理本身), 护理诊断体系 (NANDA), 影像/病理知觉型读片训练 (相邻但独立), 精神科 DSM 结构化访谈细节, 医患沟通技巧全集 (只覆盖诊断不确定性沟通), 患者自查/自我诊断指

日本語の概要は準備中です。原文の説明を表示しています。

健身私教 — 为客户设计、指导和推进个性化训练方案的专业工艺, 有别于团课教练、物理治疗师或运动队教练: (a) 训练方案设计与周期化 (线性 / 波动 / 板块周期化 Bompa & Haff; NSCA《力量训练与体能训练精要》行业圣经; Schoenfeld 肌肥大机制; Helms/Valdez/Morgan 肌肉与力量金字塔; 共轭训练法 Simmons/Westside; Starting Strength 线性渐进 Rippetoe; Renaissance Periodization 训练量地标 Israetel); (b) 动作评估与筛查 (FMS 功能性动作筛查 Gray Cook; NASM CEx 纠正性训练连续体 抑制-拉伸-激活-整合; 关节逐级方法 Cook/Boyle; 姿势与代偿模式识别; PAR-Q+ 与 ACSM 运动前筛查指南); (c) 教学与指令 (外部 vs 内部注意焦点 Wulf; 差异化学习 Schöllhorn; 约束导向方法 Davids/Renshaw; RIR/RPE 自动调节 Zourdos/Helms; 动机访谈在健身中的应用 Rollnick/Miller); (d) 营养指导的执业边界 (宏量营养素周期化; Precision Nutrition / ISSN 立场声明的循证建议; 边界: 私教提供一般性指导, 医学营养治疗需 RD/RDN 资质; 能量可用性与 RED-S Mountjoy IOC 共识); (e) 商业与客户管理 (客户留存与方案依从; 咨询与销售伦理; 线上教练平台与规模化 Goodman PTDC; 方案交付工具 TrueCoach/Trainerize/TrainHeroic; 课时定价模型; 独立教练 vs 健身房雇员); (f) 专项方向 (运动表现 CSCS; 纠正性训练 CES; 老年健身 SFN; 产前产后; 青少年 YSCA; 适应性 / 无障碍健身; 健美 / 形体; 力量举; 耐力运动 S&C)。诚实处理: 兄弟科学 vs 循证之争, 补剂行业利益冲突, 合成代谢激素使用现状 (诚实但不推广: 匿名调查约 30% 有经验男性健身者使用过 — 业内估, Kanayama/Pope/Hudson 记录健康风险, WADA 禁用清单用于竞技语境), 体型焦虑与进食障碍风险 (男性私教肌肉变形症, 正食症倾向, NEDA 负责任语言指南), 健身房掠夺性销售 (高压推销、误导性对比照、长约锁定), 执业边界违规 (私教诊断伤病或超范围开饮食处方), 线上教练认证造假 (周末速成、未经认可的认证)。不含: 物理治疗 / 康复治疗 (持照医疗职业), 不含: 团课教练 (Les Mills/Zumba/CrossFit 分馆教练 — 相邻但不同), 不含: 精英竞技运动教练 (团队项目周期化, 不同职业路径), 不含: 营养作为主业 (临床营养学需单独资质)。 (Personal Trainer — the craft of designing, coaching, and progressing individualized exercise programs for clients, distinct from group fitness instruction, physiotherapy, or sports coaching: (a) exercise programming and periodization (linear / undulating / block periodization per Bompa & Haff; NSCA Essentials of Strength Training and Conditioning as industry bible; Schoenfeld on hypertrophy mechanisms; Helms/Valdez/Morgan Muscle & Strength Pyramids; conjugate method Simmons/Westside; Starting Strength linear progression Rippetoe; Renaissance Periodization volume landmarks Israetel); (b) movement assessment and screening (FMS Gray Cook; NASM CEx corrective exercise continuum inhibit-lengthen-activate-integrate; joint-by-joint approach Cook/Boyle; posture and compensation pattern identification; PAR-Q+ and pre-exercise screening ACSM guidelines); (c) coaching and cueing (external vs internal cueing Wulf attentional focus research; differential learning Schöllhorn; constraints-led approach Davids/Renshaw; RIR/RPE autoregulation Zourdos/Helms; motivational interviewing for adherence Rollnick/Miller adapted to fitness); (d) nutrition guidance within scope of practice (macronutrient periodization; evidence-based recommendations per Precision Nutrition / ISSN position stands; scope boundary: PT gives general guidance NOT medical nutrition therapy which requires RD/RDN credential; energy availability and RED-S awareness Mountjoy IOC consensus); (e) business and client management (client retention and programming adherence; consultation and sales ethics; online coaching platforms and scaling Goodman PTDC; programming delivery tools like TrueCoach/Trainerize/TrainHeroic; session pricing models; independent contractor vs gym employee dynamics); (f) specialization tracks (sports performance CSCS; corrective exercise CES; senior fitness SFN; pre/postnatal; youth YSCA; adaptive/inclusive fitness; bodybuilding/physique coaching; powerlifting/strength sports; endurance athlete S&C). Evidence-based practice as the core ethos: Schoenfeld/Krieger meta-analyses on volume-response, Helms systematic reviews on protein/resistance training, Brad Schoenfeld's MASS journal bridging research to practice, Menno Henselmans and Eric Helms as practitioner-researchers, Greg Nuckols Stronger By Science as translation layer. Chinese fitness industry context: rapid growth of personal training in commercial gyms (Keep/Lefit/Megafit chains), NSCA-CPT and ACE-CPT as dominant certifications alongside local CSFA (China Sport and Fitness Association) credential, '体适能' (physical fitness) as formal term, online coaching boom post-COVID, PT business models in tier 1-3 cities diverge sharply. Honest treatment of: bro science vs evidence-based d

日本語の概要は準備中です。原文の説明を表示しています。

60-Second Agency Snapshot — rapid 5-dimension assessment without subagents, outputs a compact scorecard

日本語の概要は準備中です。原文の説明を表示しています。

Run an authorized, local-first application security assessment on the current project using this agent's own reasoning. Use when the user invokes Myrqen, asks to security-test or pentest the app they are building, asks whether their app has real vulnerabilities before shipping, wants a Myrqen finding validated, or wants a Myrqen remediation applied and retested.

日本語の概要は準備中です。原文の説明を表示しています。

Content quality and E-E-A-T analysis with AI citation readiness assessment. Use when user says "content quality", "E-E-A-T", "content analysis", "readability check", "thin content", or "content audit".

日本語の概要は準備中です。原文の説明を表示しています。

Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Spawns parallel subagents for comprehensive analysis. Produces per-post scores and a prioritized action queue. Use when user says "audit blog", "blog audit", "site audit", "blog health", "audit all posts", "check all blogs".

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill to apply the rigorous epidemiological reasoning of Julie E. Buring (epidemiologist and women's health trialist) to study design, clinical trial critiques, cardiovascular risk assessment, and evidence-based integrative medicine. Trigger this skill whenever you are evaluating medical literature, designing cohort studies or RCTs, assessing conflicting research findings, or analyzing cardiovascular risk factors (especially in women). Reach for this when users ask about the validity of supplements, the discrepancy between observational and randomized data, or how to future-proof a clinical registry.

日本語の概要は準備中です。原文の説明を表示しています。

Structured planning mode for AI agents working on coding and development tasks. Produces a comprehensive plan BEFORE any code is written or changed, including task decomposition, architecture decisions, risk assessment, and approval gates. Use this skill whenever the user says "/plan", "plan mode", "plan first", "think before coding", "make a plan", or asks the agent to plan before executing. Also trigger when the user describes a complex multi-step development task and would clearly benefit from structured planning before implementation — especially for tasks involving new features, refactors, migrations, infrastructure changes, or multi-file edits. When in doubt, plan. A few minutes of planning prevents hours of rework.

日本語の概要は準備中です。原文の説明を表示しています。