「eth」の検索結果

Cross-method decision tree for calling hits in pooled CRISPR screens. Catalogs statistical models (MAGeCK RRA, MAGeCK MLE, BAGEL2, drugZ, JACKS, Chronos, CERES), experimental designs each is built for, failure modes outside design domain, reconciliation when methods disagree, multiple-testing and effect-size thresholds, the order of operations (count -> QC -> CN-correct -> hit-call -> validate), the second-best-sgRNA conservative rule, and consensus-hit strategy. Use when choosing among MAGeCK / BAGEL2 / drugZ / JACKS / Chronos for a given design, reconciling disagreement across two or three methods on the same screen, deciding whether to require consensus, gating downstream validation by hit-confidence tier, or interpreting unstable hit lists across reruns.

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

Recommends performing a dexamethasone suppression test to evaluate for autonomous cortisol secretion in patients with primary aldosteronism and adrenal adenoma. Triggered when a clinician considers whether to perform a dexamethasone suppression test in a patient with PA and adrenal adenoma.

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

Use when the user describes a problem, decision or stuck situation but names no method: "how should I approach this?", "help me think this through", "we can't decide", "where do I start?". Picks the best-fit thinking method and runs it. Skip for plain execution tasks or when a method is named.

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

Steward public stories about any work — creation ethics, application ethics, and maintenance of the story plus its disclosures (generated, drafted, curated, authored). Use when writing a public article, origin story, talk, README narrative, or showcase about how work was made; when publishing ethics and decisions; or when asked who generated vs curated a text. Do not use for ADRs, FAQs, skill citations, or marketing hype.

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

匠Methodでビジネス企画をモデリングする際に使用。ステークホルダーモデル、価値デザインモデル、価値分析モデル、要求分析ツリーの知識を提供。

匠MethodのDrawIOモデル（コアモデル + ビジネスコンテキストフロー）を全て作成する。

匠Methodの全成果物（コアモデル、価値マネジメント評価、企画立案）を一括作成する

匠Methodのコアモデルのテキストデータを全て作成する。

匠MethodのコアモデルのDrawIOモデルを作成する。

匠Methodの全成果物（テキストデータ + DrawIOモデル）を一括作成する。

匠Method Agentの使い方を説明する

匠Method全体の概要と各フェーズの関係を説明する

Prepares a DRAFT data incident impact brief from the incident notes and data inventory the user provides: the timeline as stated, systems involved matched to the inventory, data categories held and evidenced as involved, people and record counts potentially affected with the source and method behind every figure, third parties, notification questions for legal and the data protection officer, and every UNKNOWN with the evidence that would settle it. No legal determination: it never states whether the incident is a reportable breach, whether notice is due, to whom or by when. Use when the user asks to "prepare the impact brief for this incident", "what data was involved", "how many people are affected", "map the incident to our data inventory" or "pull together what legal needs on the incident". Do not use for the blameless postmortem or root-cause timeline, use incident-postmortem-drafter instead. Drafts for human review; never approves, authorises or signs off.

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

倫理的かつ効率的な英語論文執筆を支援するスキル（水本 2025; langtech.jp/ai-writing/ に基づく）。 論文の英語化，校正，構成相談，査読対応，AI利用申告の作成を，学術的誠実性のガードレール付きで行う。 以下のような場面で必ず使用すること： 「論文の英語を直して」「英語論文を書きたい」「この段落を校正して」「査読コメントに返事を書きたい」 「AI利用の申告文を作りたい」「Introduction/Methods/Results/Discussionを書きたい」 「カバーレターを書きたい」「論文の構成を相談したい」「英文を洗練したい」 「日本語を英語にしたい」「表現の候補を出して」「時制をチェックして」 英語論文に関するあらゆる執筆支援タスクで使用する。

End-to-end bisulfite sequencing workflow from FASTQ to differentially methylated regions. Covers Bismark alignment, methylation calling, and DMR detection with methylKit. Use when analyzing bisulfite sequencing data.

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

Add authorization methods for a new entity to AuthorizationService. Use after creating a resource service. Triggers on "add permissions", "authorization methods", "entity permissions", "add auth methods".

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

Help a user talk through whether to change jobs, stay, or change something in their current work, starting from uncertainty, distress, a vague sense of stagnation, an offer in hand, a counter-offer from the current employer, or pressure from family or colleagues. Clarify what matters, separate deadlines that order the next steps from the decision itself, compare conditional options, and agree on a small next step and a time to revisit it. Use when someone asks whether they should quit, wonders whether leaving is just running away, has second thoughts after receiving an offer or being asked to stay, feels stuck because others say it would be a waste, wants to leave soon after joining, or wants advice before deciding to start a job search; do not make the final stay-or-leave decision, evaluate offer terms, plan the resignation, or predict hiring outcomes.

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

Sort incoming scout messages and agent-forwarded openings by what they actually disclose: whether the employer is named at all, which of pay, location, employment type, and duties are stated, whether the message refers to the applicant's own history or reads as a mass send, whether a stated salary is an offer or a "up to" figure, and whether the same employer has arrived through more than one route. Use when a user has a backlog of scout messages and wants to know which ones can be researched, what to ask before replying, and what to settle before handing over a resume; do not use to rate how promising an opening is, to judge an employer or an agent, or to reply on the user's behalf.

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

Check whether a user may start side work alongside their current job, by reading the employer's own rules and contract clause by clause: whether side work is prohibited, needs prior permission, or only a notification, and which duties the planned side work could touch (non-compete, confidentiality, exclusive attention to the main job, use of company assets and information, combined working hours). Separate what is confirmed in a document from what is hearsay, and produce the questions to ask the employer plus the facts an application or notification will need. Use when someone with a main job is considering side work, freelance or gyomu-itaku work, a second part-time job, or paid trial work for another company, and needs to know what their own employer's rules require first; do not use to rule on whether a clause is lawful or enforceable, to help conceal side work from an employer or avoid filing obligations, to predict whether permission will be granted, or to submit the application or contact the employer.

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

Cross-method decision tree for calling hits in pooled CRISPR screens. Catalogs statistical models (MAGeCK RRA, MAGeCK MLE, BAGEL2, drugZ, JACKS, Chronos, CERES), experimental designs each is built for, failure modes outside design domain, reconciliation when methods disagree, multiple-testing and effect-size thresholds, the order of operations (count -> QC -> CN-correct -> hit-call -> validate), the second-best-sgRNA conservative rule, and consensus-hit strategy. Use when choosing among MAGeCK / BAGEL2 / drugZ / JACKS / Chronos for a given design, reconciling disagreement across two or three methods on the same screen, deciding whether to require consensus, gating downstream validation by hit-confidence tier, or interpreting unstable hit lists across reruns.

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

Cross-method decision tree for calling hits in pooled CRISPR screens. Catalogs statistical models (MAGeCK RRA, MAGeCK MLE, BAGEL2, drugZ, JACKS, Chronos, CERES), experimental designs each is built for, failure modes outside design domain, reconciliation when methods disagree, multiple-testing and effect-size thresholds, the order of operations (count -> QC -> CN-correct -> hit-call -> validate), the second-best-sgRNA conservative rule, and consensus-hit strategy. Use when choosing among MAGeCK / BAGEL2 / drugZ / JACKS / Chronos for a given design, reconciling disagreement across two or three methods on the same screen, deciding whether to require consensus, gating downstream validation by hit-confidence tier, or interpreting unstable hit lists across reruns.

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

This skill should be used when the user asks to "最小再現環境を作って", "再現環境を構築して", "問題を切り分けたい", "パッケージの不具合か確認したい", "create a minimal reproduction", "isolate the issue", "build a repro environment", "reproduce this bug", "narrow down the cause", "is this a package bug or my code", "このPRの問題を再現して", "this commit broke something", or wants to determine whether a bug is caused by a package, the environment, or application code. Accepts PR URLs, commit hashes, or branch names as input.

Test naming conventions and best practices specialized skill. Used when naming test methods, improving test readability, and establishing naming standards. Covers three-part naming method, Chinese naming recommendations, test class naming, etc. Keywords: test naming, test naming, naming conventions, naming conventions, three-part naming, three-part naming, method_scenario_expected, method_scenario_expected, how to name tests, test readability, naming best practices, test report, test documentation

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

ECCを通じてNasiko CLIの導入状況を確認し、固定バージョンのインストールと管理対象の削除を、事前プレビューや利用者の同意を踏まえて進めるスキル。

• Nasiko CLIの導入状況を調べたいとき
• 検証済みバージョンの導入前確認
• ECC管理下のCLIを削除したいとき