「eth」の検索結果

Expert-level differential equations knowledge. Use when working with ordinary differential equations, partial differential equations, systems of ODEs, Laplace transforms, Fourier methods, boundary value problems, stability analysis, or numerical methods for ODEs. Also use when the user mentions 'ODE', 'PDE', 'initial value problem', 'boundary value problem', 'Laplace transform', 'separation of variables', 'eigenvalue problem', 'heat equation', 'wave equation', 'Laplace equation', 'stability', or 'phase plane'.

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

Expert-level analytical chemistry knowledge. Use when working with chromatography, spectroscopy, electroanalytical methods, sample preparation, quantitative analysis, calibration, statistics, or instrumental analysis. Also use when the user mentions 'HPLC', 'GC', 'mass spectrometry', 'atomic absorption', 'ICP', 'titration', 'calibration curve', 'detection limit', 'NMR', 'chromatography', 'electrochemistry', 'sample preparation', or 'method validation'.

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

Publish a proposal, offer, or pitch as a tracked link and report back whether it's getting read (view analytics after sending). Use when the user says "send the proposal", "did they open it", "track whether they read it", "share the offer". Not for recurring client reports (use client-reporter) or general research shares (use report-publisher).

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

Use when you need to inspect NuGet package APIs, list public types, or decompile method/property signatures. Keywords: inspect package API, list types, decompile type, method signatures, NuGet interface.

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

Critically analyze whether a product, repo, skill, plugin, harness, or architecture vision still fits the real application, user intent, implementation, evidence, and likely future direction. Use when asked to assess vision vs application, predict future fit, critique roadmap direction, analyze strategic intent, or decide whether to keep, refine, pivot, or kill a plan.

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

Run before building anything new — a pre-build gate that decides whether an idea deserves its own tool, judged from both the agent lens (legible, drivable, automatable) and the human lens (will I touch it, do I want to maintain it). Trigger on "should I build X", "starting a new project / app / tool / repo", "is this worth making", "want to spin up", or any new-build intent — even if the word "checklist" never appears. Outputs a backed GATE.md with checkmarks and a one-line verdict note in the project root docs. Do NOT load for small config tweaks, one-off scripts, bug fixes on existing things, or anything that is clearly a feature of something you already run.

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

Triage a GitHub issue that already has the cc-issue-created label and is assumed to be ready to start. First inspect the comment history to decide whether human confirmation is needed (cc-need-human-check, highest priority); otherwise decide whether the issue should be closed as not needed, unanswered confirmation items remain (cc-answer-issue-questions), the description is stale relative to settled comment-history content and must be refreshed before execution (cc-update-issue), or it can move to execution (cc-exec-issue). Dependency checks are out of scope.

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

copy_tuner_client v2.0.0 への移行で、削除された独自ヘルパー tt の呼び出しを Rails 標準の t（translate）へ 置換するスキル。tt は PR #122 で存在理由を失い gem から削除されたため、残った tt(...) は NoMethodError に なる。大半は機械的に tt( → t( で済むが、訳文を文字列加工している箇所（→ I18n.t へ）と label 系ヘルパーの 第一引数に渡している箇所（→ 引数構造を分離）だけは別扱いで、開発環境のマーカートークン残留バグを避けるため 1 件ずつ確認する。対象は app 配下の .rb / .haml / .erb。

Web search, content extraction, crawling, and deep research via the Tavily CLI. Use this skill whenever the user wants to search the web, find articles, research a topic, look something up online, extract content from a URL, grab text from a webpage, crawl documentation, download a site's pages, discover URLs on a domain, or conduct in-depth research with citations. Also use when they say "fetch this page", "pull the content from", "get the page at https://", "find me articles about", or reference extracting data from external websites. This provides LLM-optimized web search, content extraction, site crawling, URL discovery, and AI-powered deep research — capabilities beyond what agents can do natively. Do NOT trigger for local file operations, git commands, deployments, or code editing tasks.

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

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

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

Discover and list all URLs on a website without extracting content, via the Tavily CLI. Use this skill when the user wants to find a specific page on a large site, list all URLs, see the site structure, find where something is on a domain, or says "map the site", "find the URL for", "what pages are on", "list all pages", or "site structure". Faster than crawling — returns URLs only. Essential when you know the site but not the exact page. Combine with extract for targeted content retrieval.

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

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

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

Cite-or-Block 架构的基石原子 skill。把报告里的 citation 锚点 (例如 [guideline:CSCO-2024-NSCLC:§5.5.2] / [pmid:12345678:abstract]) 解析为源文件片段,并核对事实声明里的关键词是否在引用源原文里出现。 Foundation atomic skill for the Cite-or-Block architecture. Resolves citation anchors (e.g. [guideline:CSCO-2024-NSCLC:§5.5.2] / [pmid:12345678:abstract]) to raw source text fragments, and verifies whether claim keywords actually appear in the cited source. 使用场景 / Use when: 1. 报告生成后要做 fact-check (resolve_citation + verify_claim_against_source) 2. content-verification-layer 要扫全报告锚点 (parse_citations_in_text) 3. drug-citation-verifier / 任何 cross-check skill 需要"锚点 → 源原文" P0 守护:本 skill **绝不维护任何已知字典**。源里没有 = verified=False, 无例外、无 fallback、无"已知答案兜底"。 P0 guard: this skill **never maintains any built-in dictionary**. Not in source = verified=False. No fallback, no built-in answers.

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

Use when work produces a deliverable, factual claim, dataset, code change, decision, publication, deployment, automation, or irreversible action whose failure would matter; when the user asks for a quality gate, acceptance criteria, QA, completeness, validation, audit, evidence, preflight, release readiness, or a definition of done; or before claiming completion on medium- or high-risk work. Automatically decide whether a formal gate is warranted, derive task-specific pass/fail criteria, gather evidence, and block unsupported completion. Make sure to use this skill even when the user does not say "quality gate" if consequential work needs acceptance criteria or completion evidence. Skip formal gating for trivial, reversible, low-impact requests.

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

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

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

Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships. Use when output must clear two independent adversarial reviewers before it ships.

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

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

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

Codex adapter for Garry Tan's full gstack methodology across CEO/product pressure, CTO architecture, design, engineering, QA, security, shipping, documentation, and retrospectives. Use when the 总控/CEO or 架构/CTO role needs gstack method routing, implementation-plan hardening, or the user says gstack should help a role.

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

Generates ideas with named methods from creative practice (SCAMPER, lateral provocations, constraints, pataphysics, and more), routed to the user's situation. Use for open-ended generative or selective requests: "I want to make or start something", "I'm stuck", "inspire me", "make this weirder", "help me pick", or inventing a research question.

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

Cloudflare Durable Objects の実装とレビューに使用する。チャットルーム、マルチプレイ、予約システムなどの状態を持つ協調処理、RPC methods、SQLite storage、alarms、WebSockets、Workers統合、wrangler設定、Vitestでのテストを扱う。事前学習の知識より最新のCloudflare docsの取得を優先する。

Strategy map analysis using the Eterdis two-directional causal chain. Use this skill to diagnose whether strategy is coherent by building two chains — bottom-up from resources to results, top-down from expectations to requirements — and finding where they don't connect. Runs in three modes — full diagnostic for deep sessions, review mode for quick re-assessment, and alert triggers for early-warning signals. Updates company-context.md after every run. Triggers on questions about strategic alignment, why the strategy isn't working, what to invest in, how the business creates value, whether the plan is realistic, or where the biggest gap is. Based on practice by Eterdis (eterdis.com).

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

Culture assessment and monitoring with three modes — Diagnostic for a deep session surfacing the gap between declared culture and actual culture, Review for periodic check-ins on whether behavior is shifting, and Alert Triggers for setting tripwires around culture-strategy misalignment, regression, and integration risk. Not a culture change programme — a mirror. Updates company-context.md after every run. Triggers on questions about culture, values, team dynamics, how decisions really get made, why change efforts stall, merger integration, or whether the organisation can actually execute its strategy. Based on practice by Eterdis (eterdis.com).

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

VRIO resource analysis combined with Dynamic Capabilities assessment. Use this skill to identify real competitive advantages (Barney VRIO framework), then test whether the organisation can sense new opportunities, seize them, and transform itself to stay ahead (Teece dynamic capabilities). Runs in three modes — full diagnostic for deep first-use sessions, review mode for quick re-assessment, and alert triggers for defining early-warning signals. Updates company-context.md after every run. Triggers on questions about competitive advantage, defensibility, resource assessment, why competitors are gaining ground, organisational agility, or whether advantages will hold. Based on practice by Eterdis (eterdis.com).

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

Competitive positioning diagnostic — figures out where you actually stand relative to competitors and whether that position is defensible. Use this skill when someone needs to understand their real competitive position (not the one on the slide deck), when a new competitor has entered the market, when customers are switching and nobody can explain why, when pricing power is eroding, when a strategic investment depends on knowing whether the moat is real, or when leadership says "we're differentiated" but can't explain how. Draws on Playing to Win, Porter's generic strategies, and Blue Ocean thinking — applied as diagnosis, not planning. Based on practice by Eterdis (eterdis.com).

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