220 件 ・ 関連度順
概要と使いどころ
Use for WooCommerce operations on a WordPress site. Listing, reading, creating, updating, and duplicating products. Managing categories and tags. Reading orders and updating order status. Stock management. Sales reports. Storefront layout edits. Builder-aware throughout. Requires the Respira WooCommerce add-on (paid).
日本語の概要は準備中です。原文の説明を表示しています。
Coordinates large block execution with market impact minimization, counterparty selection, and crossing network utilization. Use when executing block trades, managing large orders, or minimizing market footprint.
日本語の概要は準備中です。原文の説明を表示しています。
Design monochrome ornamental patterns grounded in Alexander Speltz's classical ornament taxonomy. Covers historical period selection, motif structural analysis, prompt construction for line art and silhouette rendering, and AI-assisted image generation via Z-Image. Use when creating decorative borders, medallions, or friezes in a single color, exploring historical ornament styles through generative AI, producing line art or pen-and-ink renderings of classical motifs, or generating reference imagery for design or educational materials.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and fix RFDB data disappearing after compaction, where rfdb-server reports a tiny node count (e.g. "15 nodes") on startup despite manifest_index.json showing hundreds of thousands of nodes and segment files existing on disk. Use when: (1) rfdb-server logs "Default database: N nodes" with N orders of magnitude smaller than recent analysis output, (2) /api/stats returns only the most recent commit's nodes, (3) the issue appears AFTER a compaction event (manifest with l1_node_segments populated and node_segments: []), (4) subsequent commits dropped L1 references. Root cause: ManifestStore::create_manifest() initializes l1_node_segments/l1_edge_segments to Vec::new() instead of cloning from current manifest, so any commit AFTER compaction silently orphans all L1 data even though segment .seg files still exist on disk. Compaction injects L1 fields explicitly after create_manifest, but regular commits do not.
日本語の概要は準備中です。原文の説明を表示しています。
Email and SMS sequences — loyalty program emails, birthday emails, win-back campaigns, special event invites, abandoned cart for online orders
日本語の概要は準備中です。原文の説明を表示しています。
Build Solana DeFi applications combining Jupiter APIs with Helius infrastructure. Covers token swaps (Swap API V2), lending/borrowing (Lend protocol), limit orders (Trigger), DCA (Recurring), token/price data, transaction submission via Sender, fee optimization, real-time streaming, and wallet intelligence.
日本語の概要は準備中です。原文の説明を表示しています。
Run AI agent tasks on a Volcengine (火山引擎) cloud phone via the Mobile Use Agent OpenAPI. Use when the user asks to drive, automate, operate, or test an Android app on a cloud phone for enterprise use cases (e.g. reply to WeCom customer messages, add leads in a CRM, clock in on DingTalk, check invoicing stats, query inventory in a supply-chain app, ship e-commerce orders, approve OA requests) or personal ones (open 小红书 and search, place an order, check nearby places on a map), or to check status, fetch result, cancel, or list a Mobile Use run. Requires one-time setup to store Volcengine AK/SK locally; ProductId and PodId can be saved as a default device during setup, the user prompt is provided per run. Supports optional GPS injection (GpsInfo) with user consent (auto-asked only for location-related tasks).
日本語の概要は準備中です。原文の説明を表示しています。
"Analyze and mitigate the bullwhip effect where demand variability amplifies upstream in supply chains. Use this skill when the user needs to diagnose order variability amplification, quantify the bullwhip ratio, or implement dampening strategies — even if they say 'why are our orders so volatile', 'supply chain variability', or 'demand amplification problem'.".
日本語の概要は準備中です。原文の説明を表示しています。
Search Mouser Electronics for electronic components — secondary source for prototype orders. Find parts, check pricing/stock, download datasheets, analyze specifications. Use with KiCad for BOM creation and part selection. Use this skill when the user specifically mentions Mouser, when DigiKey is out of stock or has worse pricing, when comparing prices across distributors, or when searching for parts that DigiKey doesn't carry. For package cross-reference tables and BOM workflow, see the `bom` skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use Printify to browse catalog data, manage shops and products, and review or create orders.
日本語の概要は準備中です。原文の説明を表示しています。
Set up and operate a Shopify store with Shopify's official MCP server (the installed `shopify` command, NOT the npm Shopify CLI). Use whenever someone wants to sell online, start an online store or business, try Shopify, or manage a Shopify store — even if they do not say "Shopify": "I want to sell candles online", "help me start an online business", "open my first store", "add products", "check my orders", "set inventory", "make a discount", "show my sales", "how did my Shopify Email campaigns do". Before connection it can show relevant mock.shop sample catalogs, suggest business names, check domains, search shopify.dev, and validate GraphQL. The connect flow can create an account and store for a new user. Do the work here rather than only listing setup steps. Keywords: Shopify MCP, ecommerce, sample products, demo store, starter catalog, ShopifyQL, first store, create product.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to design, configure, and troubleshoot Salesforce Entitlement Management on Cases: entitlement processes, milestone definitions, recurrence types, milestone actions (success/warning/violation), business hours assignment, and entitlement templates. Covers the deployable EntitlementProcess / MilestoneType / EntitlementTemplate / EntitlementSettings metadata, signed timeLength time triggers, recurrenceType semantics, process versioning, and how a milestone actually completes. Trigger keywords: entitlement process, milestone, SLA timer, milestone tracker, first response SLA, time trigger, recursChained, CaseMilestone, EntitlementId, SlaProcess, stopped clock. NOT for SLA milestones on Field Service work orders — use admin/fsl-sla-configuration-requirements. NOT for time-based case escalation rules — use admin/escalation-rules. NOT for the business-hours calendar itself — use admin/business-hours-and-holidays.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to configure SLA enforcement for Salesforce Field Service (FSL) using Work Order entitlement processes: designing entitlement processes of type Work Order, defining FSL milestones (response time, on-site arrival, resolution), wiring milestone actions, and aligning Business Hours with service territory Operating Hours. NOT for Case SLAs and Case entitlement processes — use admin/entitlements-and-milestones. NOT for defining the SLA tier table and escalation matrix — use architect/sla-design-and-escalation-matrix.
日本語の概要は準備中です。原文の説明を表示しています。
Configure Salesforce Billing (blng__ managed package) billing schedules, invoice plans, billing policies, and billing treatments on activated Orders. Triggers: 'billing schedule not generating invoices', 'blng__BillingSchedule__c missing after order activation', 'in-advance vs in-arrears billing', 'milestone billing', 'invoice run not picking up order products', 'evergreen billing setup', 'billing treatment configuration'. NOT for revenue schedules, GL transactions and ASC 606 - use admin/revenue-recognition-requirements. NOT for native Revenue Cloud (RLM) BillingSchedule objects - use data/revenue-cloud-data-model.
日本語の概要は準備中です。原文の説明を表示しています。
Neuroscience expert covering brain structure, neural signaling, cognition, and neurological disorders
日本語の概要は準備中です。原文の説明を表示しています。
Dispatch an explicit, user-dictated set of edits that spans TWO OR MORE zones of the GDD — the master spec, systems, content types, and flows — in one ordered pass. Writes nothing itself: it resolves each delta to its (target, zone), orders them so a system change lands before the content or flow that depends on it, delegates each to the owning skill (/unikit-gd-spec, /unikit-gd-system, /unikit-gd-content, /unikit-gd-flow), and closes with one /unikit-gd-verify pass. Use when you already know the changes and they touch more than one part of the design, e.g. "apply these GDD changes", "update the combat system and its loot and the boss flow". It also takes a /unikit-gd-review report file (applies its apply-ready bucket), and a bare /unikit-gd-apply reads the last /unikit-gd-verify output in the session. For a single-zone change call its owner directly; to research an open question use /unikit-gd-explore first.
日本語の概要は準備中です。原文の説明を表示しています。
Generates structured bail hearing summaries from transcripts and case documents, extracting charges, arguments, conditions, and rulings. Use when summarizing bail hearings, pretrial detention decisions, bond hearings, or release condition orders.
日本語の概要は準備中です。原文の説明を表示しています。
Produces a Rule 506(d) bad actor disqualification review for private securities offerings, including a covered persons register, tailored questionnaires mapping to each disqualifying event category, a documented reasonable-care diligence record, and classification analysis of flagged events with remediation or disclosure recommendations. Use this skill when conducting Rule 506(d) diligence, identifying covered persons for a Regulation D offering, drafting bad actor questionnaires, or analyzing potential disqualifying events involving criminal convictions, SEC orders, SRO sanctions, or state regulatory actions. Also trigger when the user mentions bad actor screening, covered persons analysis, Rule 506(d) questionnaire, disqualification waiver, or reasonable care defense. Even if the user just says "bad actor check" or "506(d) diligence," use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Metal/wgpu/WGSL shader surfaces for native Rust gpui apps (Zed-family, pd-console), stockpiled with beautiful copy-pasteable shader-toy examples. Use for custom GPU fragment passes behind/around gpui panes: ocean/water shaders, pixelated waves and boats, a living harbor, dithered chrome borders, sonar sweeps, aurora/starfields, CRT/scanline post. Trigger on: wgsl, wgpu, metal shader, gpui shader, shadertoy, fragment shader, SDF, noise/fbm, ordered dithering, pixelation, render-to-texture, "pixelated waves and boats", living harbor water. NOT for: web/GLSL/three.js shaders (use a web tool), non-shader gpui motion (use rust-gpui-motion), general GUI layout/color (use beautiful-gui-design), CLI/TUI (use beautiful-cli-design).
日本語の概要は準備中です。原文の説明を表示しています。
Assesses genetic health of populations for conservation with Ne estimation across time horizons (LDNe NeEstimator V2 option-file API + SNeP physical-linkage correction; recent trajectory via GONE/GONE2; deep history via Stairway Plot 2 / dadi / fastsimcoal2 / PSMC), F-statistics, runs of homozygosity binned by length class to date inbreeding, genetic-load decomposition (Bertorelle 2022 realized vs masked), the modern 100/1000 Ne rule (Frankham 2014), Ne/Nc 2-6 orders of magnitude in marine fish (Hauser & Carvalho 2008), tree-sequence forward simulations (SLiM 4 + pyslim + tskit), and the Sukumaran-Knowles caveat against MSC methods for management-unit definition. Use when estimating Ne by time horizon, detecting inbreeding via F_ROH, decomposing genetic load, justifying conservation thresholds, distinguishing ESU/MU/DPS, configuring NeEstimator V2, or correcting LDNe physical linkage.
日本語の概要は準備中です。原文の説明を表示しています。
Decide whether commonly-excluded patients (eating disorders, elderly ≥75, upper GI disease) can actually receive a GLP-1 receptor agonist. Use when a clinician asks "can I give semaglutide to a patient with binge eating disorder / anorexia / bulimia", "is liraglutide safe in an 80-year-old", "GLP-1 with GERD or chronic gastritis", "GLP-1 in sarcopenic elderly", or anytime a patient is being ruled out for GLP-1 therapy based on a perceived contraindication. Grounded in Gorgojo-Martínez 2023 §6 (Myths or Reality).
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates basal insulin rates through basal rate testing across different time periods and adjusts as indicated. Triggered by clinician orders to 'Perform basal rate test to verify pump settings' or 'Check basal rates during periodic pump review'.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends bilateral adrenalectomy for patients with Cushing's syndrome when bilateral adrenal pathology is confirmed as the source of hypercortisolism. Clinical triggers include bilateral macronodular adrenal hyperplasia (BMAH), bilateral adrenal adenomas, or bilateral adrenal carcinoma identified by imaging.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends that all patients with Cushing’s syndrome receive monitoring and adjunctive treatment for cortisol-dependent comorbidities including psychiatric disorders, diabetes, hypertension, hypokalemia, infections, dyslipidemia, osteoporosis, and poor physical fitness. Apply when managing any CS patient to address associated health issues; triggers include confirmed or suspected hypercortisolism, preoperative evaluation, postoperative follow‑up, or persistent hypercortisolism despite treatment.
日本語の概要は準備中です。原文の説明を表示しています。