1,162 件 ・ 関連度順
概要と使いどころ
Query openFDA REST API for adverse events (FAERS), labeling, product info, recalls, enforcement. Search by drug name, ingredient, MedDRA, or NDC. 1k req/day no key; 120k with free key. For trials use clinicaltrials-database-search; for structures use drugbank-database-access or chembl-database-bioactivity.
日本語の概要は準備中です。原文の説明を表示しています。
Query FDA drug labels (DailyMed) via REST API. Search structured product labels (SPLs) by name, NDC, set ID, or RxCUI; get indications, dosage, warnings, adverse reactions, packaging. No auth. For adverse events use fda-database; for DDIs use ddinter-database.
日本語の概要は準備中です。原文の説明を表示しています。
Parse/write FCS (Flow Cytometry) files v2.0-3.1. Events as NumPy, channel metadata, multi-dataset files, CSV/FCS export. Use FlowKit for gating/compensation.
日本語の概要は準備中です。原文の説明を表示しています。
Generate tactical collar strategy reports for protecting PMCC positions through earnings or high-risk events. Requires TWS or IB Gateway running locally.
日本語の概要は準備中です。原文の説明を表示しています。
Canonical rules for finding, creating, and updating Shift GitHub issues. Use whenever the user asks to file, create, open, update, triage, or search for an issue, or when substantial work needs an issue before a pull request. Prevents duplicates and defines acceptance criteria and pull-request closure semantics.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze pipeline health, identify stalled deals, predict close probability, and suggest actions to move deals forward. Improves forecast accuracy and prevents revenue leakage. Use when deals get stuck or forecast accuracy is poor.
日本語の概要は準備中です。原文の説明を表示しています。
API reference: EventKit. Query for EKEventStore, EKEvent, EKReminder, calendar access.
日本語の概要は準備中です。原文の説明を表示しています。
POS (Point of Sale) architecture and patterns. Use when writing, editing, exploring, debugging, fixing bugs, implementing features, or reviewing WooPos-prefixed classes or files under ui/woopos/. POS uses a different architecture than the main app — plain ViewModel (not ScopedViewModel), pure Compose (no Fragments), Compose Navigation (no nav graphs), parent-child SharedFlow event bus. Loading this skill prevents applying main-app patterns that would be wrong for POS. For analytics use `pos-analytics`, for tests use `pos-tests`.
日本語の概要は準備中です。原文の説明を表示しています。
Guides the periodic DPIA review lifecycle including trigger identification for regulatory changes, new data categories, technology changes, and breach incidents. Covers version control, stakeholder sign-off procedures, and DPIA register management per Art. 35(11). Keywords: DPIA review, PIA update, review cadence, version control, Art. 35(11), periodic review, trigger events, stakeholder sign-off.
日本語の概要は準備中です。原文の説明を表示しています。
Manages legal hold and data preservation processes including triggering events, custodian notification, hold-in-place technical implementation, release procedures, and interaction with retention schedules. Covers litigation hold registers, compliance monitoring, and Art. 17(3)(e) exception documentation. Activate for legal hold, litigation preservation, data freeze, e-discovery hold queries.
日本語の概要は準備中です。原文の説明を表示しています。
Use when defining or debugging Spring Boot 4 database transaction boundaries, rollback, propagation, optimistic-lock retries, or commit-bound events. For duplicate HTTP commands use idempotency-patterns; for reactive transactions use webflux-reactive-patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evolving aggregate invariants, value objects or domain events in an existing DDD-style Spring Boot 3 application, or when DDD is explicitly requested. Preserve existing API identifiers and architecture when changing domain behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Use when organizing or verifying a modular Spring Boot monolith with Spring Modulith, including module APIs, dependency rules and reliable module events. Do not restructure an application into modules for an unrelated endpoint change.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evolving aggregate invariants, value objects or domain events in an existing DDD-style Spring Boot 4 application, or when DDD is explicitly requested. Preserve existing API identifiers and architecture when changing domain behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Use when generating or modifying any Spring Boot class — controllers, services, repositories, DTOs, mappers, or configuration. Enforces strict layer separation and prevents business logic from leaking across boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the project follows hexagonal (ports & adapters) architecture. Prevents domain code from depending on Spring or JPA. Use when you see packages like domain/, application/, infrastructure/, or adapters/ in the project structure.
日本語の概要は準備中です。原文の説明を表示しています。
Use when defining or debugging Spring Boot 3 database transaction boundaries, rollback, propagation, optimistic-lock retries, or commit-bound events. For duplicate HTTP commands use idempotency-patterns; for reactive transactions use webflux-reactive-patterns.
日本語の概要は準備中です。原文の説明を表示しています。
A meta-skill that understands task requirements, dynamically selects appropriate skills, tracks successful skill combinations using agent-memory-mcp, and prevents skill overuse for simple tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Build AI-focused SRE incident response practices for LLM outages, degraded quality, runaway cost events, and safety regressions.
日本語の概要は準備中です。原文の説明を表示しています。
Scores a riso film or reworks its score. Designs the cue list from the film's FILM.md events, builds a deterministic renderAudio() from the sound kit in studies/sound.html, iterates with tools/audio.mjs, gates determinism, length, loudness and sync, and records measured results in FILM.md. Use for "score this film", "add sound/music", "the climax is too loud", "fix the handoff at 16 s", "check the mix", sound effects, foley or a soundtrack on a riso film. Not for drawing or motion (riso-film) or changing tools/.
日本語の概要は準備中です。原文の説明を表示しています。
Design a Seedance 2.0 two-player co-op game menu or opening animation with stable character bindings, approved visual direction, readable UI copy, coordinated palette, explicit interaction events, and a clean final menu state. Use for game concepts and character-led social intros; not for playable game development or copying commercial game branding.
日本語の概要は準備中です。原文の説明を表示しています。
Plan Seedance 2.0 music-video clips where performance, camera, scene changes, spatial lyric typography, and transitions respond to a locked music window. Use for 4–15 second hooks or longer multi-clip MVs with explicit audio/lyric ownership, subject and scene references, beat-led events, and assembly handoffs; not for ordinary caption cleanup or unlicensed lyric copying.
日本語の概要は準備中です。原文の説明を表示しています。