1,159 件 ・ 関連度順
概要と使いどころ
Ranks papers by evidence family, methodological quality tier, validation depth, and claim discipline; assigns anchor, context-setting, mechanistic support, or caution citation roles; prevents prestige-based or design-label-based ranking errors.
日本語の概要は準備中です。原文の説明を表示しています。
Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating customers, contracts, or rate cards, designing billable metric group keys, managing credits and commits, configuring invoicing, syncing invoices with Stripe Billing, billing AI applications for token usage, setting up self-serve (PLG) pricing, reviewing customer health, commit burn, portfolios, or renewals, or migrating from Stripe Billing Meters to Metronome.
日本語の概要は準備中です。原文の説明を表示しています。
Build, modify, or review Stripe Apps and extensions using the relevant documentation and reference guides. Use for custom Stripe Dashboard UI, stripe-app.yaml, @stripe/ui-extension-sdk, @stripe/extensibility-sdk, script extensions, extension interfaces, custom workflow actions, and apps that authenticate to Stripe or react to events. Also use when deciding whether a Stripe extension can support the user's billing or workflow requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Emulated Google OAuth 2.0, OpenID Connect, Gmail, Calendar, and Drive for local development and testing. Use when the user needs to test Google sign-in locally, emulate OIDC discovery, handle Google token exchange, configure Google OAuth clients, work with Gmail messages/drafts/threads/labels, manage Calendar events, upload or list Drive files, or work with Google userinfo without hitting real Google APIs. Triggers include "Google OAuth", "emulate Google", "mock Google login", "test Google sign-in", "OIDC emulator", "Google OIDC", "Gmail API", "Google Calendar", "Google Drive", "local Google auth", or any task requiring a local Google API.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to analyze an existing PostgreSQL database and identify which tables should be converted to Timescale/TimescaleDB hypertables. **Trigger when user asks to:** - Analyze database tables for hypertable conversion potential - Identify time-series or event tables in an existing schema - Evaluate if a table would benefit from Timescale/TimescaleDB - Audit PostgreSQL tables for migration to Timescale/TimescaleDB/TigerData - Score or rank tables for hypertable candidacy **Keywords:** hypertable candidate, table analysis, migration assessment, Timescale, TimescaleDB, time-series detection, insert-heavy tables, event logs, audit tables Provides SQL queries to analyze table statistics, index patterns, and query patterns. Includes scoring criteria (8+ points = good candidate) and pattern recognition for IoT, events, transactions, and sequential data.
日本語の概要は準備中です。原文の説明を表示しています。
Detect flood events by comparing water levels to thresholds. Use when determining if flooding occurred, counting flood days, aggregating instantaneous data to daily values, or classifying flood severity.
日本語の概要は準備中です。原文の説明を表示しています。
An overview of the python package for running the GaMMA earthquake phase association algorithm. The algorithm expects phase picks data and station data as input and produces (through unsupervised clustering) earthquake events with source information like earthquake location, origin time and magnitude. The skill explains commonly used functions and the expected input/output format.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes keyword usage in provided content, calculates density, suggests semantic variations and LSI keywords based on the topic. Prevents over-optimization. Use PROACTIVELY for content optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Prove that the file you are about to send, publish, or hand off IS the thing you mean — before it leaves your hands. Rebuild from source, check integrity, diff the derived artifact against its source, and require the recipient to echo what they received. Use before sending a paper/PDF for review, shipping a release or replication package, handing files to a coauthor or collaborator, uploading anything to an external reviewer or model, or publishing. Prevents an entire review/QA cycle from being spent on defects that exist only in the artifact, not in the work.
日本語の概要は準備中です。原文の説明を表示しています。
Premise, theme, controlling idea, subject selection and logline for scripts (前提/主题/立意/选材/戏核) — merged from Lajos Egri's premise-as-tyrant and dialectic, Robert McKee's controlling idea (value + cause) and idea/counter-idea, Neill Hicks' five premise questions, Lisa Cron's "third rail" (desire vs misbelief, origin scene, what-if), Julian Hoxter's logline and theme-attitude rule, Blake Snyder's logline/genre/title tests, and Lu Jun's Chinese craft chapters on 选材要严/开掘要深/视角要新/戏核要好/情节要奇. Use when turning a vague idea into a premise, finding what a story is really about, choosing a subject and angle, testing a logline, deciding the ending from the theme, or diagnosing a script that "has events but no story".
日本語の概要は準備中です。原文の説明を表示しています。
Writing plays and screenplays in the Chekhovian mode (契诃夫戏剧法) — distilled from the complete plays (没有父亲的人/普拉东诺夫, 伊凡诺夫, 林妖→万尼亚舅舅, 海鸥, 三姊妹, 樱桃园, nine one-acts) plus Chekhov's own letters, Stanislavsky's and Nemirovich-Danchenko's rehearsal notes and 焦菊隐/童道明 criticism. Covers the four-act mood-based structure without central climax, off-stage events, "correct answer stated in Act 1 and refused", the announced event that never happens, three-layer endings (hope monologue + nihilist line + household action), no-villain conflict with environment, every character's object and catchphrase, one-way love chains, half-step-off dialogue, philosophy cut by thirst, the shortest words for the deepest pain, stage-direction and sound discipline, and how Chekhov revised The Wood Demon into Uncle Vanya. Use when the user wants an ensemble drama, a "nothing happens" play, subtext-heavy dialogue, a family estate / provincial story, an anti-climactic structure, or asks how to "Chekhov-ize" a script.
日本語の概要は準備中です。原文の説明を表示しています。
Writing screenplays in the style of Ozu Yasujiro and Noda Kogo (小津安二郎・野田高梧) — distilled from six complete screenplays (晚春 Late Spring, 麦秋 Early Summer, 东京物语 Tokyo Story, 浮草 Floating Weeds, 秋日和 Late Autumn, 秋刀鱼之味 An Autumn Afternoon). Covers the "family member leaves" master plot, off-screen events / on-screen reactions, lie-driven plots, minimal-syllable confessions, go-between characters, faceless suitors, pillow-shot scene breaks, echoing objects, mirror characters, children's subplots as metaphor, displaced quarrels, the single-monologue rule, diminishing endings, Ozu's script format and stage-direction vocabulary. Use when the user wants to write a quiet family drama, a 小津风 / 侘寂 / 日常系 script, a story about marrying off a daughter, aging parents, or wants dialogue that says less and means more.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding Memory Events, Memory Tickets, memory-map.json, vault-references.json, PM Soul memory ownership, or Memory Curator routing to an agent repo.
日本語の概要は準備中です。原文の説明を表示しています。
Compose IRQL (Incident Response Query Language) queries for Kusto cybersecurity investigations. Translates natural language hunting questions into composable IRQL pipelines using Get_*, Extract_*, and Enrich_* functions. WHEN: IRQL query, security hunt, threat hunting KQL, incident response query, compose hunting pipeline, failed logins, phishing investigation, lateral movement, process execution, file creation events.
日本語の概要は準備中です。原文の説明を表示しています。
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch.
日本語の概要は準備中です。原文の説明を表示しています。
Build a PixiJS v8 render layer: create the async Application, load textures with Assets, compose the scene graph with Container and Sprite, drive the ticker loop, wire pointer events, and group draws with render groups. Use when building or debugging PixiJS v8 — when the user mentions PixiJS, Pixi, Application, app.stage, Container, Sprite, Assets.load, app.ticker, or eventMode. Pins the v8 async init() API.
日本語の概要は準備中です。原文の説明を表示しています。
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and call_group. Use when wiring node communication in a Godot project, replacing tight references with signals, emitting/connecting events, or porting 3.x connect("sig", self, "method") code.
日本語の概要は準備中です。原文の説明を表示しています。
Start a cross-team project with the collaboration contract that prevents the classic collisions — who decides what, how work flows between teams, the communication channels and cadence, and what done means — agreed before the first collision instead of during it. Use when asked kick off this cross-team project right, our two teams keep colliding, define how we'll work with the other team, or set up the partnership before we start. Produces the one-page contract: decision rights, interfaces, cadence, and the done-definition.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a content library, docs site, or blog for AI-generated filler that's eroding trust and search performance — and triage what to fix, rewrite, or delete. Use when asked to find slop in a content library, audit AI-written content quality, explain why content engagement or rankings dropped after scaling with AI, or set a quality bar for AI-assisted publishing. Produces an audited inventory with per-piece verdicts, the detection signals used, a triage plan, and a publishing quality gate that prevents recurrence. For a single article's AI-citability use aeo-optimizer; for the strategy itself use content-calendar or seo-content-brief.
日本語の概要は準備中です。原文の説明を表示しています。
Mem0 memory CLI: add memories from messages, semantic search, read or delete memories, poll async events. Trigger phrases: mem0, memory layer, remember this.
日本語の概要は準備中です。原文の説明を表示しています。
Read-only Polymarket market data: events, markets, prices, order books. No trading, no key needed. Trigger phrases: polymarket, prediction markets, market odds, event prices.
日本語の概要は準備中です。原文の説明を表示しています。
Read and write Loops: find and manage email contacts; send events and transactional emails. Trigger phrases: loops, email contacts.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to deal with their inbox — find what needs a response, draft replies, and turn emails into calendar events or reminders. Captures the common email→read→reply→schedule workflow on macOS (Apple Mail, Calendar, Reminders). Powered by LMCP.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to check their calendar, find availability, or create/update/delete events in Apple Calendar on macOS. Powered by LMCP's Calendar tools, which are macOS-only.
日本語の概要は準備中です。原文の説明を表示しています。