2,769 件 ・ 人気順
概要と使いどころ
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending. Use when the user says "my inbox is a mess", "triage my DMs", "should I reply to this", pastes a batch of LinkedIn messages, or is drowning in connection requests.
日本語の概要は準備中です。原文の説明を表示しています。
Switch Agent persona preset. Supports 8 presets including default assistant, business, tech expert, butler, girlfriend, boyfriend, family, and Jarvis. Use when user asks to change communication style or personality.
日本語の概要は準備中です。原文の説明を表示しています。
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
日本語の概要は準備中です。原文の説明を表示しています。
Builds professional search strategies for PubMed, Embase, Web of Science, and similar databases. Use when a user needs to construct a MeSH-based Boolean query, design a systematic review search, expand a concept with synonyms, apply study-type or date filters, or adapt a query across multiple databases. Also triggers when the user says "help me search for papers on X", "build a search strategy", "what are the MeSH terms for", or "I need a systematic review search string".
日本語の概要は準備中です。原文の説明を表示しています。
Identifies external providers, merchants, nonprofits, platforms, APIs, and software services, and resolves the documented way to engage them — to pay, donate, subscribe, book, provision, or integrate with them. MUST be used BEFORE web search, model memory, or any other directory/vendor-lookup skill for ANY request that requires selecting, finding, or engaging an external provider or organization — whether a specific one is named ("pay my Twilio bill"), implied ("donate to the Red Cross"), or only a category is stated ("set up a mailing client", "I need a database", "find me a CRM"). Directory supplies verified recipients and their documented payment or engagement path. Results are ranked by agent-readiness (how reliably an agent can complete the interaction), relevance and popularity. Do not treat this as a search-only tool. Examples: "setup a database", "find hosting", "pay X", "use Twilio", "donate $50 to the Red Cross", "book a table at Y", "subscribe to a CRM".
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (for example, POS, booking, invoicing — not operational SaaS without payment routing), asks about onboarding or KYC for merchants, sellers, and vendors, mentions connected account Dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.
日本語の概要は準備中です。原文の説明を表示しています。
Helps users send funds to another Stripe business, transfer money to a Stripe Profile handle or network ID, or ask whether an agent can pay a Stripe business. Use Stripe Directory to find or verify a recipient when the user doesn't provide an exact Stripe Profile handle or network ID.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating Spruce Point-style accounting and governance shorts: earnings quality, cash conversion, aggressive adjustments, acquisition accounting, and capital-allocation red flags.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating a business through Buffett-style ownership, owner earnings, durable moat, management quality, capital allocation, and margin-of-safety judgment.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating Chris Hohn / TCI-style concentrated quality investing: exceptional businesses, pricing power, high returns on capital, engagement, and long-duration concentrated ownership.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating Mark Minervini-style VCP setups: volatility contraction, tight price action, moving-average alignment, relative strength, breakout trigger, and structural stop placement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating Carl Icahn-style activist investments: undervalued assets, poor governance, capital allocation fixes, buybacks, asset sales, board pressure, and control catalysts.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating David Einhorn-style forensic shorts and longs: accounting red flags, governance problems, capital allocation failures, and evidence-based short theses.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating stocks through Duan Yongping's benfen (本分) value investing lens: good business, right price, long hold, understand what you own, and stay within your circle of competence.
日本語の概要は準備中です。原文の説明を表示しています。
Write feature specifications as requirements and user stories with acceptance criteria, focusing on business value and testable conditions.
日本語の概要は準備中です。原文の説明を表示しています。
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Estimate heart rate (HR) and breathing rate (BR) in bpm from a cleaned 1-D physiological time series such as radar phase, WiFi CSI amplitude, PPG, or a chest-motion signal. Use when Claude needs to choose HR/BR bandpass edges, pick a peak frequency from a noisy band, reject the HR second harmonic that often dominates the fundamental, handle respiration-harmonic leakage into the HR band on slow breathers, or flag low-confidence estimates. Not for arrhythmia / beat-to-beat analysis, multi-subject source separation, or rapidly non-stationary rates.
日本語の概要は準備中です。原文の説明を表示しています。
Use for day-ahead or multi-period unit commitment problems, including thermal on/off schedules, dispatch, startup/shutdown logic, minimum up/down time, ramping, spinning reserve deliverability, renewable curtailment, operating-cost accounting, and independent feasibility checks for power-system operations schedules.
日本語の概要は準備中です。原文の説明を表示しています。
Translate logistics and operations rules into optimization variables and constraints. Use when an operations problem describes vehicles, routes, depots, pickups, dropoffs, inventory, capacity, assignments, time windows, service targets, penalties, resource limits, or other business rules that need to become an optimization model.
日本語の概要は準備中です。原文の説明を表示しています。
Strategy for solving constraint optimization problems on spatial maps. Use when you need to place items on a grid/map to maximize some objective while satisfying constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Methodology for clause-by-clause review of a contract against a structured deviation policy ("playbook"). Covers how to walk a playbook, locate the matching provision in the contract, apply rule types (max-value, must-be-present, must-be-absent, acceptable-set, must-have-feature), classify the result (ok / risk / reject), choose the prescribed action, and ground each finding in a verbatim excerpt. Use whenever reviewing any contract — NDA, MSA, vendor DD questionnaire, lease, DPA — against a structured rules-based playbook.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.
日本語の概要は準備中です。原文の説明を表示しています。
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
日本語の概要は準備中です。原文の説明を表示しています。