「assess」の検索結果

Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating claims/evidence quality use scientific-critical-thinking; for quantitative scoring frameworks use scholar-evaluation.

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

Research an explicitly requested Marin question or coordinate a multi-session experiment; find prior work, assess evidence, and record results in the task's existing durable surface.

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

Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.

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

Assess a GitHub issue or PR for demonstrated need, supported alternatives, correctness, and maintainer action. Desk review only.

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

持久战略：面对长期、复杂、短期不可能速胜的任务，客观评估态势，划分战略防御 / 相持 / 反攻三阶段，判定当前所处阶段，设置阶段转换条件，并在困难阶段仍给出局部进攻点。当任务跨多个会话或多轮迭代、资源暂时不足、或出现"想放弃"与"一把梭"两种情绪时触发；任务能在当前会话完成时不触发。 English: Protracted strategy. For long-horizon work that cannot be won quickly, assess the situation objectively, divide the effort into defense / stalemate / counter-offensive stages, name the current stage and its exit condition, and always identify a local offensive even while accumulating. Trigger when work spans many sessions or iterations, resources are temporarily short, or you notice either defeatism or a rush to finish; skip when the task fits in the current session.

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

统筹兼顾：当多个目标、指标或利益方相互制约、优化一项会伤害另一项时，识别全部辩证关系对，检查片面性，为每对关系定出当前阶段的侧重与底线，评估系统性影响，并设失衡预警。触发信号包括 trade-off、目标冲突、速度 vs 质量、短期 vs 长期、"顾此失彼"；只有单一目标、用户已定取舍、或属硬性二选一时不触发。 English: Overall planning. When several goals, metrics, or stakeholders constrain each other and optimizing one harms another, map every dialectical pair, check for one-sidedness, set the current emphasis and floor for each pair, assess system-wide effects, and define imbalance alarms. Triggers include trade-offs, goal conflicts, speed vs quality, short vs long term; skip for single-goal work, decisions the user already made, or hard either/or constraints.

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

星火燎原：从零起步、资源极少时，先评估客观条件，选定一个能站稳、能复用、能扩展的"根据地"（最小切入点），扎根后再逐步扩张，拒绝四处出击的流寇主义。当启动新项目、做 MVP / pilot、面对宏大目标不知从何下手、或做了很多零散事却没有积累时触发；项目已有稳固基础、只是修改现有系统时不触发。 English: Spark a prairie fire. When starting from almost nothing, assess the conditions, choose one base area (a minimal foothold that can hold, be reused, and expand), dig in, then grow step by step instead of scattering effort. Trigger for new projects, MVPs, pilots, daunting goals with no obvious first step, or busy work that accumulates nothing; skip when a solid base already exists or the task modifies an existing system.

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

CVE lookup and applicability assessment domain card. Use after reconnaissance has identified products, versions, services, or fingerprints and red-team mode needs evidence-based CVE matching before deeper testing.

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

Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and writing with quantitative scoring and actionable feedback.

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

Evaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality, identifying flaws. For formal peer review writing use peer-review.

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

Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating claims/evidence quality use scientific-critical-thinking; for quantitative scoring frameworks use scholar-evaluation.

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

Comprehensive biosignal processing toolkit for analyzing physiological data including ECG, EEG, EDA, RSP, PPG, EMG, and EOG signals. Use this skill when processing cardiovascular signals, brain activity, electrodermal responses, respiratory patterns, muscle activity, or eye movements. Applicable for heart rate variability analysis, event-related potentials, complexity measures, autonomic nervous system assessment, psychophysiology research, and multi-modal physiological signal integration.

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

Architecture design skill with ADR records, system design checklists, scalability assessment, and architecture patterns

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

Build, migrate, review, and maintain third-party NVIDIA NeMo Fabric adapters against the public adapter contract. Use when creating adapter or target descriptors, mapping AgentConfig into an agent harness or custom-agent runtime, implementing start/invoke/stop, declaring schemas and capabilities, packaging discovery metadata, or assessing adapter conformance. Do not use for consumer applications that only call the NVIDIA NeMo Fabric SDK.

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

Guides Holoscan SDK installation: inspects the host, assesses platform compatibility, recommends an install method, and delegates to the matching install skill.

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

[omh] Which tools and credentials a workflow needs: inventory which MCP servers, CLIs, APIs, credentials, and connectors a workflow needs; use external-connector-readiness to assess one named integration and executor-runtime-readiness to choose the coding owner. Use when the user says: toolbelt-readiness, mcp readiness, tool readiness, plugin readiness, connector readiness, needed mcp, api credential, missing cli.

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

[omh] Evaluating a plugin, connector, or API for adoption: external connector readiness - assess whether a named plugin, connector, API, data provider, or multimodal route is safe, affordable, fresh, and observable; use executor-runtime-readiness for coding-owner choice and toolbelt-readiness for missing capability inventory. Use when the user says: external-connector-readiness, external connector readiness, connector readiness matrix, plugin readiness matrix, provider readiness, api readiness, connector adoption, external plugin adoption.

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

Retrieve and analyze AlphaFold predicted structures for a protein. Use when the user provides a specific UniProt Accession ID and wants structural confidence metrics (pLDDT), domain boundary analysis, or disorder assessment. Do not use if the user only has a protein name, gene name, or amino acid sequence — ask for a UniProt ID first.

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

Performs multiple sequence alignment of proteins with EBI Clustal Omega. Use when you need to align multiple sequences to assess similarity, domain conservation, or key residue conservation. Supports up to 4000 sequences and a maximum file size of 4 MB. Do not use to search for homologous proteins in a database (use MMseqs2, BLAST), align non-protein sequences (DNA, RNA), perform structural alignment (use Foldseek, PyMOL), or if you only have a single sequence.

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

Query the Genome Aggregation Database (gnomAD). Use when determining the rarity or allele frequency of specific genetic variants, retrieving gene constraint metrics (pLI, LOEUF) to assess loss-of-function intolerance, finding variants in a genomic region or gene, or querying structural variants. Don't use for analyzing individual patient genomes, tracking somatic mutations in cancer (use COSMIC), or requesting raw sequencing reads (use ENA).

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

Evaluate research rigor. Assess methodology, experimental design, statistical validity, biases, confounding, evidence quality (GRADE, Cochrane ROB), for critical analysis of scientific claims.

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

Use when reviewing code security, auditing dependencies for CVEs, checking configuration or secret security, assessing authentication and authorization patterns, identifying OWASP vulnerabilities (injection, XSS, CSRF), or addressing security concerns about implementations.

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

Use when evaluating business model viability, analyzing profitability per customer/product/transaction, validating startup metrics (CAC, LTV, payback period), making pricing decisions, assessing scalability, comparing business models, or when user mentions unit economics, CAC/LTV ratio, contribution margin, customer profitability, break-even analysis, or needs to determine if a business can be profitable at scale.

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

Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).

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