8,703 件 ・ 関連度順
概要と使いどころ
Identify drug repurposing candidates via target-based, compound-based, and disease-based strategies. Combines drug-target-disease network reasoning with mechanism rationale, clinical-trial precedent, and patent/regulatory feasibility. Use for hypothesis-generating repurposing for orphan diseases, finding existing drugs for new indications, and prioritizing candidates by evidence and feasibility.
日本語の概要は準備中です。原文の説明を表示しています。
Trace drug mechanism of action — primary target → downstream signaling → pathway perturbation → tissue/organ effect → clinical outcome. Uses DrugBank, ChEMBL, KEGG, Reactome, STRING. Use for understanding how a drug works, identifying off-target effects, mechanism-based combination therapy design, and writing mechanism sections of reports.
日本語の概要は準備中です。原文の説明を表示しています。
Literature: retrieve document-level scientific evidence from publications, clinical-trial registries, and patent sources. Use for PubMed records, reproducible searches, trial registrations, patent evidence, abstracts, study metadata, stable identifiers, and citation provenance.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes chemical libraries by scaffold using Bemis-Murcko scaffolds, generic frameworks, cyclic skeletons, matched molecular pair (MMP) analysis via mmpdb, R-group decomposition, Free-Wilson analysis, scaffold hopping, and chemotype-aware ML train/test splits. Use when identifying chemotype clusters in a library, deriving SAR transformation rules, decomposing series into R-groups, performing scaffold-balanced QSAR splits, or planning analog campaigns.
日本語の概要は準備中です。原文の説明を表示しています。
Configure and debug MCP servers for Claude Code, OpenCode, and Codex CLI, including auth headers, scope, and validation checks. Use when MCP tools fail to connect, when an MCP server returns 401/404/HTML, or when adding a new MCP server to this repo.
日本語の概要は準備中です。原文の説明を表示しています。
Configure and debug MCP servers for OpenCode, Codex CLI, and Claude Code, including auth headers, scope, and validation checks. Use when MCP tools fail to connect or when adding a new MCP server.
日本語の概要は準備中です。原文の説明を表示しています。
Walk through the devnet → mainnet deployment checklist for a Soroban contract or Stellar dApp. Use when a user says "deploy to Stellar mainnet", "going live on Stellar", "deploy my Soroban contract", "Stellar production deployment", "mainnet checklist", or "ship it on Stellar". Covers pre-deployment verification, deployment mechanics with stellar CLI, and post-deployment monitoring with Soroban-specific gates.
日本語の概要は準備中です。原文の説明を表示しています。
Stellar dApp / frontend development. Covers the JavaScript stellar-sdk (browser + Node.js), Freighter wallet, Stellar Wallets Kit (multi-wallet), Wallet Standard, smart accounts with passkeys, transaction building / signing / submission, smart contract invocation from the client, simulation, and error handling. Use when building a React/Next.js/Node.js app that talks to Stellar — classic operations or smart contracts.
日本語の概要は準備中です。原文の説明を表示しています。
当用户需要查询掘金分类或热榜、登录掘金、发布 Markdown 文章到掘金，或将掘金文章下载为本地 Markdown 文件时使用此技能。该技能提供共享的 Node.js CLI，并兼容 Claude Code 命令封装。
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial triage of open review findings on a PR. Every finding (Codex, Claude bot, Gemini) is a hostile hypothesis to REFUTE — fix only what is proven real, reachable, in the PR's scope, and above the round's severity bar. The bar rises every review round. Everything else is declined or filed as an issue. Use for 'fix the PR findings', '/fix', '/fix 123', or before any fix commit in a review loop.
日本語の概要は準備中です。原文の説明を表示しています。
Roslyn-powered semantic query CLI for C# solutions. Use when you need to find references, callers, implementations, dependencies, members, or trace call chains in a C# codebase — replaces multi-round grep/read cycles with single precise queries.
日本語の概要は準備中です。原文の説明を表示しています。
Build localized client XAML controls with correct lifecycle, culture refresh, resource references, ownership, and validation.
日本語の概要は準備中です。原文の説明を表示しています。
Implement EUI sessions, shared state and messages, server lifecycle, and client presentation.
日本語の概要は準備中です。原文の説明を表示しています。
Implement replicated appearance data, GenericVisualizer mappings, sprite layers, overlays, and client visual systems.
日本語の概要は準備中です。原文の説明を表示しています。
Place contracts and behavior across authority, prediction, presentation, localization, and assembly boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Implement BUI contracts, server validation, localized client windows, lifecycle cleanup, and state refresh.
日本語の概要は準備中です。原文の説明を表示しています。
Generate an XLSX timesheet with logged hours, hourly rates, per-entry amount formulas, and totals for client billing or payroll.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a branded PDF report with custom client logo placeholder, colors, and content sections for white-label agency delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Extract key clauses from terms and conditions documents, then generate a plain-language PDF summary for client review.
日本語の概要は準備中です。原文の説明を表示しています。
Extract key performance indicators from client documents, then generate a branded PDF report summarizing the results.
日本語の概要は準備中です。原文の説明を表示しています。
Launches a CARLA RPC server a carla.Client can connect to, working out for itself what you pointed it at — a downloaded/extracted release, a package cooked inside a checkout, or a source checkout run through the UE4 editor — headless or windowed, and shuts it down cleanly. ROS2=1 starts it with the native ROS 2 interface active (--ros2, --rmw=fastdds/cyclonedds/zenoh, --ros-domain-id). Use when the user asks to "run/start the CARLA server", "boot CARLA headless", "launch CARLA with a window", "run the CARLA I downloaded", "start CARLA with ROS2 enabled", or "serve a packaged CARLA build".
日本語の概要は準備中です。原文の説明を表示しています。
Gets a custom map into CARLA on UE 5.8 — the four distinct routes and which one to pick — via Util/Tools/Import.py for FBX+OpenDRIVE assets into a source build, CARLA_MAPS_TO_COOK to ship a map inside a package, or client.generate_opendrive_world() for an OpenDRIVE-only map at runtime with no build at all. Covers where imported assets land, why an imported map cannot be loaded from a package by name, and the four capabilities the UE4 skill has that ue58 lacks — standalone asset packages, their installer, semantic-material tagging, and a pedestrian navmesh that is generated but silently skipped. Use when the user asks to "import a map", "add a custom map", "load my .xodr", "package my own town", or "create a standalone map package".
日本語の概要は準備中です。原文の説明を表示しています。
Starts a CARLA UE 5.8 server from a ue58-dev tree — the editor binary in -game mode (the working headless server), the packaged shipping build, or the full editor — with offscreen/nullrhi rendering, custom RPC and streaming ports, and native ROS 2 via the single-dash -ros2 flag. Probes a running server, and stops one cleanly despite the 15-character process-name truncation. Use when the user asks to "run/start CARLA UE5", "launch a ue58 server", "run headless", "publish ROS 2 topics from UE5", or a client cannot reach the simulator.
日本語の概要は準備中です。原文の説明を表示しています。
Answers "can CARLA do X here, and is there a vetted procedure for it" before you promise anything, and detects client/server/tree version skew — a support matrix over the whole collection (covered by a skill / works but undocumented / present but untested / broken or removed), an index of the features that are verified BROKEN on 0.10.0 (gbuffers crash the server, map layers do nothing, Landmark.waypoint is None, standalone asset packages are gone), and a probe that reports what this machine's build flags and running server actually offer. Use when the user asks whether CARLA supports something, when a feature has no skill, when a UE4 tutorial's steps do not exist, or before improvising a procedure.
日本語の概要は準備中です。原文の説明を表示しています。