704 件 ・ 関連度順
概要と使いどころ
Query the ZINC22 virtual compound library (CartBlanche API, billions of make-on-demand + purchasable molecules). Look up substances by ZINC ID, resolve a SMILES to its ZINC ID (exact match), inspect purchasability/catalogs, and assemble compound sets for docking. Property (MW/logP) filtering is done locally with RDKit. For bioactivity use chembl-database-bioactivity; for approved drugs use drugbank-database-access.
日本語の概要は準備中です。原文の説明を表示しています。
Show Arch Studio help, available skills, agents and host-specific commands. Use for help, how do I use Arch Studio, what is Norma, or a capability directory.
日本語の概要は準備中です。原文の説明を表示しています。
Extract structured FF&E specs from a list of product URLs into a schedule. Use to pull or bulk-import product-page data; not for PDF catalogs.
日本語の概要は準備中です。原文の説明を表示しています。
AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale. Use when working with any AgentCore service including Gateway, Runtime, Memory, Identity, Code Interpreter, Browser, Observability, Agent Registry, or Evaluations. Covers agent deployment, MCP tool integration, credential management, agent discovery, governance workflows, and automated quality assessment. Essential when user mentions AgentCore, agent runtime, agent registry, agent evaluation, MCP gateway, deploy agent, register MCP server, discover agents, evaluate agent quality, agent credentials, or wants to build, deploy, catalog, or monitor AI agents on AWS.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze field progress photos. Catalog, tag, and compare against planned progress.
日本語の概要は準備中です。原文の説明を表示しています。
Browse and search the OpenConstructionERP cost database: classification tree, SQL and semantic search, autocomplete, certainty badges, and the resource catalog. Use when a user wants to explore cost data without building a BOQ yet.
日本語の概要は準備中です。原文の説明を表示しています。
Connect OpenConstructionERP to AI coding assistants via MCP (Model Context Protocol): expose costs, BOQ, BIM and catalog endpoints as MCP tools so Claude Code / Antigravity / OpenCode can drive the platform. Use when wiring an assistant to the ERP.
日本語の概要は準備中です。原文の説明を表示しています。
Load national and market cost bases into OpenConstructionERP: the 8 national bases (Turkey Birim Fiyat, China Dinge, Brazil SINAPI, Spain BCCA, Italy Prezzario Toscana, Greece GGDE, Vietnam Dinh Muc, Indonesia AHSP), the 30 global markets, and 48 PPP market catalogs per base. Use when importing a cost database, repricing into a market, or troubleshooting a load.
日本語の概要は準備中です。原文の説明を表示しています。
Build managed ingestion pipelines into Databricks using Lakeflow Connect. Use when ingesting from SaaS apps (Salesforce, Workday Reports, ServiceNow, Google Analytics 4, HubSpot, Confluence) or databases (SQL Server cloud and on-prem; PostgreSQL/MySQL CDC in PuPr) into Unity Catalog with serverless pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Unity Catalog metric views: define, create, query, and manage governed business metrics in YAML. Use when building standardized KPIs, revenue metrics, order analytics, or any reusable business metrics that need consistent definitions across teams and tools.
日本語の概要は準備中です。原文の説明を表示しています。
Build RAG / unstructured-document evaluation datasets and demo documents (e.g. for Knowledge Assistant) on Databricks: generate synthetic PDFs locally, upload to Unity Catalog volumes, and pair each document with test questions for retrieval evaluation.
日本語の概要は準備中です。原文の説明を表示しています。
Push records from apps, services, devices, or scripts directly into Unity Catalog Delta tables with Zerobus Ingest: SDKs (Python, TypeScript, Go, Java, Rust, C++, .NET), REST, OTLP, MQTT, Arrow Flight, or Apache Kafka-compatible producer APIs, with no message bus to run. Use to stream events, telemetry, logs, IoT data, CDC, or columnar batches into Databricks in near real time; connect existing collectors and log shippers (OpenTelemetry, Debezium, Vector, Telegraf, Cribl); replace a message bus that only feeds the lakehouse; or debug Zerobus auth, schema, throughput, or delivery issues.
日本語の概要は準備中です。原文の説明を表示しています。
Discover, explore, and query Databricks data via Genie — the CLI equivalent of the Genie One MCP. MUST be invoked whenever the user asks to find or locate data ('what tables are in X', 'where does X live', 'which catalog/schema has Y'), answer a natural-language question about the data, or write a SQL query.
日本語の概要は準備中です。原文の説明を表示しています。
Operate and extend GeoNode geospatial content-management deployments, resource APIs, uploads, metadata/catalogues, GeoServer security, harvesting, and administration with explicit service and safety gates.
日本語の概要は準備中です。原文の説明を表示しています。
Routes tasks for discovering NLP datasets in the CLUEDatasetSearch catalogue, including Chinese NLP classification, QA, matching, NER, generation, translation, corpus, and reading-comprehension resources.
日本語の概要は準備中です。原文の説明を表示しています。
Routes AWS SDK for pandas (awswrangler) workflows across S3 lakehouse data, Athena/Glue catalogs, SQL connectors, runtime configuration, and AWS service integrations.
日本語の概要は準備中です。原文の説明を表示しています。
Complete guide to LINDDUN privacy threat modeling methodology covering seven threat categories: Linking, Identifying, Non-repudiation, Detecting, Data Disclosure, Unawareness, and Non-compliance. Includes DFD-based analysis, threat tree catalogs, mitigation mapping to privacy design patterns, and step-by-step process.
日本語の概要は準備中です。原文の説明を表示しています。
Implements automated PII discovery and classification using tools like Microsoft Purview, BigID, OneTrust DataDiscovery, and AWS Macie. Covers scanning schedules, accuracy tuning, false positive management, and integration patterns. Keywords: data discovery, PII scanning, Purview, BigID, Macie, OneTrust, automated classification, data cataloging.
日本語の概要は準備中です。原文の説明を表示しています。
Owns project and build-level work for Compose and Compose Multiplatform apps: bootstrapping a new project, adopting the kit in an existing project, adding or extracting a module, convention plugins in build-logic, the version catalog, and CI plus agent hooks. Use when starting a Compose Multiplatform app, adding a module, or editing settings.gradle.kts, build.gradle.kts, build-logic, libs.versions.toml, or packaging. Do NOT use for routing and architecture choices (compose-architecture), feature code (compose-feature), repositories and persistence (compose-data), composables or resources (compose-ui), or commonMain vs platform code (compose-platform).
日本語の概要は準備中です。原文の説明を表示しています。
想法群聊室 — 调研员角色。被 idea-team 主编排器调用，或用户单独说"调研一下 X"、"X 的现状/竞品/数据"、"找 2026 数据"、"事实底"时触发。**用 WebSearch 拉真实 2026 数据、列竞品、引来源——只给事实，不评判，不建议**。Do NOT use when 用户要评价想法好坏（那是反方）、或要跨界启示（那是类比者）、或已有 PRD 在跑（不需要这种调研）。插件内 skill 会由 `idea-coach` namespace 路由；catalog 用户直接按 skill 名调用。
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding or changing what the rezolus viewer exposes — an /api/v1 endpoint, a dashboard section, the metric catalog, metadata/description derivation, or the frontend data those depend on — or when editing src/viewer/ or crates/viewer/, or reviewing a viewer change. The viewer ships as two separate Rust backends (server + WASM) behind one shared frontend; changing one silently diverges them.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting work in any divine-* repo (divine-web, divine-mobile, divine-funnelcake, keycast, divine-blossom, divine-router, etc.) or when you've learned a cross-repo fact worth sharing back. The shared divine-context handbook at ~/code/divine/divine-context/ is the source of truth for cross-cutting architecture, Nostr usage, terminology, and the project catalog across the ~50 divine-* repos.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect, add, change, remove, repair, or update Claude and Codex configuration from Mizoreww/awesome-agent-config on main. Use for configuration queries and edits, installed skills/plugins/rules/MCP, and changes to this repository's configuration templates or catalogue.
日本語の概要は準備中です。原文の説明を表示しています。
Assign, validate, normalize, and explain Luhmann/Zettelkasten-style project-note codes for Chinese book manuscripts, Obsidian Markdown folders, Mandala-Grid section files, HyperCard Markdown stacks, and project-note JSON to EPUB workflows. Use when Codex needs to scan folders for 部/章/節/項/目 numbering, generate stable card ids, insert branch codes without renumbering existing notes, map letter-coded branches to Obsidian Mandala sections, preserve K### keyword index cards, sanitize private catalogs into public examples, or prepare card IDs for EPUB and HyperCard output.
日本語の概要は準備中です。原文の説明を表示しています。