「to」の検索結果

管理咨询 (管理咨询 (Management Consulting) — 战略与管理咨询的职业认知操作系统，从业者/咨询顾问/想入行者/采购咨询服务的客户视角。覆盖: (a) 第一性张力 — 假设驱动 (hypothesis-driven / answer-first / Day-1 answer) 的「先有答案再验证」⇄ 数据驱动 (data-led / bottom-up) 的「先穷尽事实再归纳」，这行的核心张力是「先射箭再画靶 vs 先画靶再射箭」，资深人偏 top-down 假设树减少 boil-the-ocean，但要时刻防 confirmation bias; 以及更深层的张力 — 「卖洞见 (insight / so-what) vs 卖工时 (analysis / 体力)」，「客户影响 (client impact / 落地) vs 智识严谨 (intellectual rigor / 漂亮 deck)」; (b) 方法论正典 (最标准化、最易蒸出高质量) — MECE (相互独立完全穷尽)、issue tree / logic tree (问题树/逻辑树)、hypothesis-driven problem solving (假设驱动)、Pyramid Principle (Minto 金字塔原理: SCQA 情境-冲突-疑问-回答 + 结论先行 + 自上而下 + 归纳/演绎)、80/20 (帕累托/抓大放小)、so-what (所以呢/洞见提炼)、storyline (故事线/ghost deck 鬼影稿)、driver tree / profit tree、2x2 矩阵、value chain、frameworks (Porter 五力/3C/4P/7S/BCG 矩阵/价值链) 既是脚手架也是陷阱 (套框架 vs 真洞见); (c) 行业结构 — MBB (McKinsey/BCG/Bain 战略三巨头) vs Big Four 咨询臂 (Deloitte/PwC Strategy&/EY-Parthenon/KPMG) vs 精品战略所 (Oliver Wyman/Kearney/Roland Berger/L.E.K./Arthur D. Little) vs 专业/职能 boutique (运营/数字化/PE 尽调); up-or-out (非升即走)、leverage model (杠杆模型: 1 个合伙人带多个 EM/咨询师/分析师的金字塔)、partner/principal/EM(项目经理)/associate(咨询师)/analyst(分析师) 职级; (d) 项目交付模型 (the case/study/engagement) — 提案/SOW (scope of work)、problem definition (问题定义/真问题 vs 表象问题)、workplan (工作计划)、hypothesis tree (假设树)、analysis (分析/建模)、synthesis (综合)、recommendation (建议)、implementation (落地); 客户管理 (steering committee 指导委员会、stakeholder 利益相关方、对齐); (e) 产出物 — the deck (PPT 幻灯片是咨询的母语)、executive summary、action title (行动标题/每页一句话结论)、ghost deck (先搭骨架后填数据)、Excel 财务模型、framework 图; (f) 职业/招聘 — case interview 生态 (案例面试: Victor Cheng LOMS/Case in Point/market sizing 市场估算/估算题/fit 行为面)、网申-笔试-案例面、up-or-out、exit options (退出路径: PE/VC/corp dev 企业发展/战略岗/创业/industry); (g) 争议/批判 — 咨询的价值之辩 (「借你的表告诉你时间」「frameworks 是剧场表演 vs 真洞见」Matthew Stewart《The Management Myth》)、McKinsey 的丑闻 (Purdue 阿片类/独裁政府/ICE/利益冲突, Bogdanich & Forsythe《When McKinsey Comes to Town》)、咨询 vs 自建战略部、generalist 通才 vs specialist 专才之争、AI/GenAI 对初级分析师工作的冲击; (h) 流派 — 战略经典 (Porter 定位学派/五力 vs 资源基础观 RBV vs 蓝海战略 Kim&Mauborgne vs 颠覆式创新 Christensen vs Mintzberg 应急战略批判 planning school); 三巨头气质分野 (McKinsey 事实驱动/CEO 信任/通才, BCG 概念/思想领导力/经验曲线/增长-份额矩阵, Bain 结果导向/NPS 净推荐值/PE 关系/与客户深度绑定)。不含: 投行 M&A/财务顾问 (估值/承销超出范畴)、纯 IT 实施/系统集成 (SI 人力外包)、纯审计/税务、纯人力 RPO/猎头、内部战略部 only (虽相关但本 skill 聚焦专业服务咨询的外部视角)。) Master OS — automated mastery of 管理咨询 (Management Consulting) — 战略与管理咨询的职业认知操作系统，从业者/咨询顾问/想入行者/采购咨询服务的客户视角。覆盖: (a) 第一性张力 — 假设驱动 (hypothesis-driven / answer-first / Day-1 answer) 的「先有答案再验证」⇄ 数据驱动 (data-led / bottom-up) 的「先穷尽事实再归纳」，这行的核心张力是「先射箭再画靶 vs 先画靶再射箭」，资深人偏 top-down 假设树减少 boil-the-ocean，但要时刻防 confirmation bias; 以及更深层的张力 — 「卖洞见 (insight / so-what) vs 卖工时 (analysis / 体力)」，「客户影响 (client impact / 落地) vs 智识严谨 (intellectual rigor / 漂亮 deck)」; (b) 方法论正典 (最标准化、最易蒸出高质量) — MECE (相互独立完全穷尽)、issue tree / logic tree (问题树/逻辑树)、hypothesis-driven problem solving (假设驱动)、Pyramid Principle (Minto 金字塔原理: SCQA 情境-冲突-疑问-回答 + 结论先行 + 自上而下 + 归纳/演绎)、80/20 (帕累托/抓大放小)、so-what (所以呢/洞见提炼)、storyline (故事线/ghost deck 鬼影稿)、driver tree / profit tree、2x2 矩阵、value chain、frameworks (Porter 五力/3C/4P/7S/BCG 矩阵/价值链) 既是脚手架也是陷阱 (套框架 vs 真洞见); (c) 行业结构 — MBB (McKinsey/BCG/Bain 战略三巨头) vs Big Four 咨询臂 (Deloitte/PwC Strategy&/EY-Parthenon/KPMG) vs 精品战略所 (Oliver Wyman/Kearney/Roland Berger/L.E.K./Arthur D. Little) vs 专业/职能 boutique (运营/数字化/PE 尽调); up-or-out (非升即走)、leverage model (杠杆模型: 1 个合伙人带多个 EM/咨询师/分析师的金字塔)、partner/principal/EM(项目经理)/associate(咨询师)/analyst(分析师) 职级; (d) 项目交付模型 (the case/study/engagement) — 提案/SOW (scope of work)、problem definition (问题定义/真问题 vs 表象问题)、workplan (工作计划)、hypothesis tree (假设树)、analysis (分析/建模)、synthesis (综合)、recommendation (建议)、implementation (落地); 客户管理 (steering committee 指导委员会、stakeholder 利益相关方、对齐); (e) 产出物 — the deck (PPT 幻灯片是咨询的母语)、executive summary、action title (行动标题/每页一句话结论)、ghost deck (先搭骨架后填数据)、Excel 财务模型、framework 图; (f) 职业/招聘 — case interview 生态 (案例面试: Victor Cheng LOMS/Case in Point/market sizing 市场估算/估算题/fit 行为面)、网申-笔试-案例面、up-or-out、exit options (退出路径: PE/VC/corp dev 企业发展/战略岗/创业/industry); (g) 争议/批判 — 咨询的

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

Read this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for "computer use". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before a conversation is linked there may be no such tools, only an enable__mcp__remote-devices__Claude_Browser tool, which links it. It covers getting linked, picking the right tool, the access flow, and what to do when computer use is off or out of reach. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.

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

Find Amazon same-niche competitors by ASIN, with multi-dimensional filtering by click conversion rate, composite conversion rate, click volume, sales volume, reviews, ratings, price, and gross margin to identify potential competitors. Triggered when users mention same-niche competitors, ASIN competitor mining, niche competitor analysis, similar product benchmarking, ASIN benchmarking, niche market competitor list, high-conversion competitor screening, Nexscope product mining, niche competitor by ASIN, ASIN competitor analysis, same niche products, similar products discovery, conversion rate comparison, potential competitor screening, Nexscope ASIN mining. Even if users do not explicitly mention "niche" or "same niche", this skill should be triggered whenever the task involves discovering competitor lists or screening potential competitors based on a specific ASIN within the same market segment.

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

Use this skill when building, debugging, or answering questions about Liveblocks. Liveblocks gives you the building blocks and infrastructure to enable people and AI to work together inside your app, powering realtime collaboration. Liveblocks features include collaboration, rooms, organizations, workspaces, comments, composer, threads, notifications, multiplayer, conflict resolution, realtime presence, avatar stacks, AI collaborators, AI agents, text editors, Tiptap, BlockNote, Lexical, React Flow, Chat SDK. Common components include AiChat, Thread, InboxNotification, Composer, Toolbar (for Lexical Tiptap), FloatingToolbar, FloatingComposer, FloatingThreads, AnchoredThreads. Common hooks include useThreads, useStorage, useMutation, useOthers, useInboxNotifications, useAiChats. Common issues are related to authentication (ID tokens vs access tokens), permissions, room limits, connection errors, user info.

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

🇺🇸 UGC Matrix Growth Playbook — Scale user-generated content with AI + real creators. Complete SOP for UGC flywheel, creator recruitment, incentive design, multi-platform publishing. Proven at CPM $0.5, $10M ARR in 60 days with 70M impressions. Includes a full anonymized client case study. 🇨🇳 UGC矩阵号增长实操手册 — AI+真人创作者规模化用户生成内容。完整的UGC飞轮SOP、创作者招募、激励机制设计、多平台分发策略。已验证CPM $0.5，60天$1000万ARR，7000万曝光。含完整客户案例拆解（已脱敏）。 🇯🇵 UGCマトリックス成長プレイブック — AI＋リアルクリエイターでUGCをスケール。フライホイールSOP、クリエイター採用、インセンティブ設計、マルチプラットフォーム配信。CPM $0.5、60日で$10M ARR、7000万インプレッション実証済み。匿名化クライアント事例付き。 🇰🇷 UGC 매트릭스 성장 플레이북 — AI + 실제 크리에이터로 UGC 스케일링. 플라이휠 SOP, 크리에이터 모집, 인센티브 설계, 멀티플랫폼 배포. CPM $0.5, 60일 $10M ARR, 7000만 노출 검증 완료. 익명화된 클라이언트 사례 포함. Triggers: "UGC" | "UGC matrix" | "user generated content" | "creator program" | "creator economy" | "AI UGC" | "matrix accounts" | "矩阵号" | "UGC运营" | "创作者招募" | "UGC Program" | "content matrix" | "TikTok UGC" | "Instagram UGC"

Image generation, photo editing, background removal — transparent PNG images, cutouts, ecommerce packshots, product catalogs, lifestyle shots via Bria.ai. Build store-ready e-commerce catalogs at scale — shadows, product dimensions images, lifestyle scenes, marketplace listing variants. ALWAYS use this skill when the user wants to generate, edit, or transform any image — hero images, banners, social media visuals, product photos, illustrations, icons, thumbnails, ad creatives, or marketing materials — or to build a product catalog, create a packshot, stage a lifestyle shot, remove a background, make transparent PNGs, or batch-process product photos. Triggers on packshot, product catalog, product shot creator, lifestyle shot, cutout, product dimensions image, inpainting, outpainting, object removal, upscale, photo restoration, style transfer, relight, reseason, sketch-to-photo. Commercially safe, royalty-free.

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

Scout the TouchDesigner community for what's HYPED right now — community showcases, recent tutorials, generative-AI bridges, hardware interaction trends, visual-aesthetic trends of 2025-2026 — then propose tdmcp tools that ride those trends AND are easy to build. Use whenever the user wants to brainstorm new feature ideas based on what's trending in TouchDesigner, asks for 'hype' or 'trending' features, asks 'what are people doing in TD right now / what's hot / what's hype', wants tools inspired by community trends, asks to scout TD trends/aesthetics/integrations, or says things like 'ideias hype', 'novas ideias', 'o que está em alta', 'criar ferramentas para o que está bombando', 'tendências do TouchDesigner'. Also for follow-ups: refresh, rescout one surface, re-rank under another profile, deepen a trend, or filter for buildable-easy items. This is an EXTERNAL trend ideation harness — complementary to tdmcp-feature-discovery (which is INTERNAL gap analysis). It produces `_workspace/hype-scout/HYPE_TOOL_BACKLOG.md` ranked by Hype × Build-Ease; it does NOT build. Once a feature is chosen from the backlog, hand it to tdmcp-pipeline.

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

Build a custom MCP (Model Context Protocol) server that exposes domain-specific tools to AI assistants. Covers server implementation in Node.js or R, tool definitions, the resources and prompts primitives, transport configuration, and testing with Claude Code. Use when you need to expose custom functionality beyond what mcptools provides, when building specialized domain-specific AI integrations, or when wrapping existing APIs or services as MCP tools.

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

Before committing any non-trivial change, dispatch the diff to a reviewer runtime via ATO (`ato dispatch <reviewer> --session <id>`), parse the numbered/severity-tagged findings, apply or defer each one with a recorded justification, then commit. Fights the "build passes therefore ship it" failure mode — what Garry Tan calls the AI agent complexity ratchet. Place in the v2.16 stack: this skill is the LAST gate. `ato-warroom` decides the design; `ato-mission` runs the multi-step work and produces the diff; `ato-review` checks the diff before commit. When the review is part of a Mission, dispatch the review with `--require-tools read_file,grep,git_diff,git_log` so the reviewer can walk the source itself instead of reasoning from a paraphrase (PR-1.5 tool surface). Receipts land in `execution_logs` and the Mission narrative. Fires automatically before commits touching public surface (CLI subcommands, Tauri commands, MCP tools, schema migrations, security boundaries) or whenever a diff exceeds ~50 LOC of behavior change.

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

Deep-dive ONE competitor's organic footprint — exact ranking keywords and URLs, content themes, backlink profile, and exploitable gaps — with findings written into brand/competitors.md. Use this skill when the user names a competitor and wants to know what to learn from them, counter, or outrank, including head-to-head comparisons against the user's own domain. For market-level mapping first, use openseo-competitive-landscape. Triggers: "analyze competitor", "competitor keywords", "competitor backlinks", "beat <competitor>", "competitor seo teardown".

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

Generate Apple App Store screenshot pages as a Next.js app with html-to-image export at required resolutions. Screenshots are advertisements, not documentation — every screenshot sells one idea. Use when building App Store screenshots, generating exportable marketing screenshots for iOS apps, or creating programmatic screenshot generators. Triggers on 'app store screenshots', 'App Store', 'screenshot generator', 'iOS screenshots', 'marketing screenshots', 'phone mockup', 'ASO screenshots', 'app store assets', 'app listing', 'app store page', or 'app preview images'. Also use when someone is about to submit an app and needs store assets, or when they say 'make my app store page look good'. Includes iPhone and iPad mockup components with pre-measured dimensions.

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

Produce a complete narrated MYTHIC SHORT FILM end-to-end on Unsora MCP in the layered cut-paper diorama style — stacked matte cardstock worlds, a strict three-colour palette, exposure that swings, paper wipes hiding every seam, landing on a face. Animation-movie storytelling, not an explainer: gods, monsters, heroes, folklore, origin myths and transformations, told in ten-second story beats with a mythic narrator, native paper foley, and one assembled MP4. Use whenever the user wants a myth, legend, fable, folktale or fairy-tale short, a cut-paper or papercraft animated story, "tell the story of X" as a video, a stop-motion-look mythic film, or says "run the cardstock diorama myth animation" or "run the diorama myth pipeline" — even with no story given, since the skill proposes myths itself. NOT for fact-driven explainers with charts and statistics (that is vox-motion-graphics).

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

Deep OAuth 2.0 / OpenID Connect security assessment. Covers the full attack surface: redirect_uri validation bypass (path traversal, open redirect chains, subdomain confusion, URL parsing tricks, parameter pollution, response mode switching), missing/broken state parameter CSRF, PKCE downgrade and absent-challenge attacks, implicit grant token leakage (Referer, browser history, XSS fragment theft), authorization code injection, scope escalation, client confusion attacks, mutable-claims account takeover (iss+sub confusion, email-keyed identity merging), pre-account takeover via unverified registration, OpenID Connect dynamic client registration SSRF (logo_uri, jwks_uri, sector_identifier_uri, request_uri), nonce replay, ID token validation failures, Device Code phishing flow, mobile custom URI scheme hijacking, refresh token persistence, token introspection enumeration, consent screen clickjacking, host header injection, and cross-IdP mix-up attacks. Uses KOAuth, jwt_tool, nuclei oauth templates, and manual http(action="request", ...) payloads. Every technique includes actual request payloads and verification logic. Chains from /pentester or /api-security when OAuth endpoints are discovered. Chains into /web-exploit for open redirect, XSS, and SSRF chaining. Chains into /post-exploit when full account takeover is achieved. Chains into /credential-audit when access tokens or refresh tokens are recovered.

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

Use when designing or reviewing Agentforce topic (renamed subagent in April 2026) structure, including topic boundaries, instruction quality, handoff rules, out-of-scope behavior, and topic-selector strategy. Triggers: 'agentforce subagents (formerly topics)', 'topic design', 'topic selector', 'agent scope boundary', 'handoff conditions'. NOT for restricting what the agent may do or say (topic Scope, action filters, abuse prevention) — use agentforce/agentforce-guardrails. NOT for the mechanics of transferring a live conversation out — Omni-Channel routing and the context package — use agentforce/agentforce-agent-handoff-patterns.

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

Use this skill when designing, auditing, or troubleshooting behavioral boundaries for Agentforce agents — including topic (now subagent) Scope fields, agent-level system instructions, topic/action filters, the Escalation topic, restricted topics, and Instruction Adherence monitoring. Trigger keywords: agent guardrails, agent out of scope, restrict agent behavior, topic scope, subagent scope, agent fallback, Escalation topic, abuse prevention, action filters. NOT for Trust Layer content filtering (Einstein Trust Layer is a separate product concern), NOT for general topic routing design (use agentforce/agent-topic-design), NOT for prompt template construction (use agentforce/prompt-builder-templates).

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

Configuring Salesforce Email-to-Case: Standard vs On-Demand mode selection, routing address setup, email threading via Lightning tokens, auto-response rules, attachment limits, and per-address case field defaults. Trigger keywords: email-to-case, routing address, on-demand email-to-case, email threading, case from email, email agent, routing address setup, Case.settings-meta.xml, EmailToCaseRoutingAddress, emailServicesAddress, isVerified, caseOrigin, enableThreadTokenInBody, useEmailHeadersForThreading, overEmailLimitAction, unauthorizedSenderAction, enableE2CAttachmentAsFile, saveEmailHeaders, newEntityRecordType, casePriority, EmailMessage.EmailRoutingAddressId, auto-response loop. NOT for the wider case layer (queues, escalation rules, case teams, entitlements) - use admin/case-management-setup. NOT for routing case work items to agents after creation - use admin/omni-channel-routing-setup. NOT for the email templates or letterheads themselves - use admin/email-templates-and-alerts.

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

Use WooCommerce's customer and session APIs correctly — WC ships its own session handler (WC_Session_Handler, single wp_woocommerce_sessions table for both guests and logged-in users) and its own customer object (WC_Customer via WC()->customer), separate from $_SESSION / native PHP sessions / wp_get_current_user. AI consistently reaches for $_SESSION (breaks with page caching, setcookie (no signing, no namespacing), or user_meta for guests (impossible). The correct path is WC()->session->set/get for ephemeral per-visitor data, WC()->customer->get_billing_* for the active customer context including guests, and new WC_Customer($user_id) for one-off loads. Important — WC()->session is auto-initialized only on frontend requests (incl. admin-ajax); REST, cron, and WP-CLI must call wc_load_cart() explicitly. Use when storing per-visitor state, reading the current visitor's billing data, or debugging session loss across page caches / REST / cron. Triggers on WC_Session, WC_Session_Handler,...

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

Per-toolkit hardening audit loop for NV oOS Pro tools. Systematically scans each addons/pro/includes/tools/<toolkit> (and its plugins/nvoos-content-graph-pro mirror) for the four recurring production failure classes — unguarded shell calls that fatal on exec-disabled hosts, calls to nonexistent client methods, string-assuming parsing of provider responses that may be arrays, and provider enum/service mismatches — then fixes, tests (Docker PHPUnit), and validates (phpcs both standards) before moving to the next toolkit. Use when asked to audit a toolkit, review the X tools for similar issues, do the same for the other toolkits, or continue the toolkit audit loop. The first case study (document-generation) found 3 fatal bugs + 1 broken regex.

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

Connect and manage Elementor MCP servers as "MCP Apps" on NV oOS assistants — official Elementor MCP (application passwords, permission inheritance, enable/revoke flows), third-party Elementor MCP plugins, the Pro MCP Apps metabox/slash-command/REST surfaces, the Remote Sites "MCP Server" connection type with assistant connection_ref references, auth-type mapping (basic vs header vs oauth), the host allowlist (Security Center setting, constant, filter), tool discovery/bridging into chat, and troubleshooting (allowlist 403s, restricted hosts, protocol fallback, negative discovery cache, same-site in-process bridge, missing connection_ref). Use when connecting an assistant to Elementor MCP, creating a Remote Sites MCP Server connection, using /mcp-app, fixing Test Connection or Discover Tools failures, allowlisting an Elementor host, or debugging bridged elementor_* tools missing from chat.

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

When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. Use when the user mentions "competitor monitoring", "track competitors", "competitor alert", "competitor changed their title", "watch a competitor app", "competitor weekly report", "competitive intelligence", or "what changed in competitor's listing". For a one-time deep competitive analysis, see competitor-analysis. For market-wide chart movements, see market-movers.

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

Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanics, and building tools people can't resist sharing with friends. Use when: generator tool, quiz maker, name generator, avatar creator, viral tool.

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

Plan a user interview topic in PostHog — pick who to target (cohort, emails, or PostHog distinct IDs), draft what to ask about, and prepare the voice-agent context plus a question list. Use when the user asks to "talk to users", "check how users feel about X", "interview some customers", "set up a user interview", "run a user-research call", "find users to ask about Y", or otherwise wants qualitative feedback through a conversation. Walks the user through targeting (cohorts-list, persons-list, or accepting emails / distinct IDs directly), captures the topic, and prompts for agent context and questions before calling user-interview-topics-create. Cohort targeting is resolved to explicit emails/distinct_ids at create time — topics snapshot their audience and do not re-evaluate cohort membership later. Do NOT trigger when the user is uploading a recorded interview audio file (that's the separate UserInterview/transcript flow) or only browsing existing topics with user-interview-topics-list.

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

Install and configure ToolUniverse for any use case — MCP server (chat-based), CLI (command line with 9 subcommands), or Python SDK (Coding API with 3 calling patterns). Covers uv/uvx setup, MCP configuration for 12+ AI clients (Cursor, Claude Desktop, Windsurf, VS Code, Codex, Gemini CLI, Trae, Cline, etc.), full CLI reference (tu list/grep/find/info/run/test/status/build/serve), Coding API quickstart, agentic tools, code executor, API key walkthrough, skill installation, and upgrading. Use when user asks how to set up ToolUniverse, which access mode to use (MCP vs CLI vs SDK), configuring MCP servers, using the CLI, troubleshooting installation, upgrading, or mentions installing ToolUniverse or setting up scientific tools. Also triggers for "how do I use ToolUniverse", "what's the best way to access tools", "command line", "tu command", "coding API", "tu build".

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

Drug and chemical toxicity assessment via adverse outcome pathways (AOPs), real-world FAERS adverse event signals, FDA labels, and toxicogenomic associations. Triangulates molecular initiating event to cellular outcome to organ-level toxicity to clinical adverse event. Use for hepatotoxicity/cardiotoxicity/nephrotoxicity prediction and toxicology reports.

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