2,643 件 ・ 関連度順
概要と使いどころ
Escreve copy para redes sociais — post avulso, carrossel, thread e legenda — respeitando limite, formato e cultura de cada plataforma. Use quando o usuário disser "post para", "legenda", "conteúdo para LinkedIn", "carrossel", "social media", "adaptar para as redes", "texto do Instagram". Para o gancho isolado ver copy-hooks; para derivar de material existente ver copy-repurpose.
日本語の概要は準備中です。原文の説明を表示しています。
Escreve sequências e e-mails isolados — onboarding, nutrição, recuperação de carrinho, lançamento, newsletter e cold email. Use quando o usuário disser "e-mail marketing", "sequência de e-mails", "newsletter", "cold email", "fluxo de nutrição", "recuperação de carrinho", "automação de e-mail".
日本語の概要は準備中です。原文の説明を表示しています。
Responsive GNOME layouts: AdwBreakpoint conditions, BreakpointBin, MultiLayoutView, BottomSheet, narrow/wide layout swaps. Use when making an app work on phones or narrow windows.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a concise, executive-ready performance summary covering key metrics, trends, and what's driving movement. Use this skill when someone needs to produce a briefing, executive summary, performance narrative, or stakeholder readout — for example, "write an exec summary of last week's performance," "create a performance briefing for our leadership team," "produce a monthly business review summary," "what should I tell executives about our metrics," or "generate a performance narrative." Also trigger for "QBR summary," "weekly business review," or "stakeholder briefing."
日本語の概要は準備中です。原文の説明を表示しています。
Generates a polished, leadership-ready performance briefing with KPI tiles, executive narrative bullets, and a driver analysis — all as a print-ready HTML document. Always use this skill when someone asks for an executive summary, performance briefing, leadership readout, stakeholder update, or business review — even if they don't say "executive" explicitly. Trigger phrases include: "write a summary of last week's performance," "create a briefing for our leadership team," "produce a monthly business review," "what should I tell executives about our metrics," "generate a performance narrative," "QBR summary," "weekly business review," "board update," "stakeholder briefing," "how did we do last week," or "give me a performance snapshot." When in doubt, use this skill — it is always better to produce a polished briefing than a raw data dump.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes single-cell pooled CRISPR screens (Perturb-seq, CROP-seq, Perturb-CITE-seq, ECCITE-seq, multiome) where each cell carries an sgRNA and a scRNA-seq / surface-protein / chromatin readout. Covers experimental design (direct-capture Perturb-seq Dixit 2016 vs CROP-seq 3'UTR-barcoded Datlinger 2017 vs ECCITE-seq vs Multiome), MOI for sgRNA assignment, escaper-cell filtering (Mixscape, Papalexi 2021), SCEPTRE NB GLM + permutation for low-MOI (Barry 2024 Genome Biol 25:124), the Pertpy framework, factor decomposition, genome-scale Perturb-seq (Replogle 2022 Cell, 2.5M cells), and per-perturbation single-cell DE. Use when running a single-cell CRISPR screen, choosing direct-capture vs CROP-seq architecture, filtering escaper cells, performing single-cell DE, integrating Perturb-seq with pathway analysis, scaling to GW CRISPRi via Replogle protocol, or analyzing multi-omics screens.
日本語の概要は準備中です。原文の説明を表示しています。
Query and download from NCBI Gene Expression Omnibus (GEO) and EMBL-EBI's BioStudies/ArrayExpress mirror. Use when finding expression datasets, navigating SuperSeries vs SubSeries, choosing between series-matrix (submitter-normalized) and raw supplementary files, downloading via GEOparse (Python) or GEOquery (R/Bioconductor), linking GEO to SRA for raw reads, or distinguishing GSE/GSM/GPL/GDS record types. Encodes the SuperSeries trap, the series-matrix normalization-trust caveat, GEOmetadb deprecation, ArrayExpress migration to BioStudies, and processed-vs-raw decision matrix.
日本語の概要は準備中です。原文の説明を表示しています。
Calls ChIP-seq peaks with MACS3, MACS2, HOMER, or SPP across narrow (TF) and broad (histone) modes. Handles input control matching, fragment-size modeling vs --nomodel, effective genome size, ENCODE-style IDR vs naive overlap, hyper-ChIPable artifacts, and aligner-specific shifts. Use when calling peaks from ChIP-seq alignments, choosing between narrow vs broad mode for a histone mark, deciding model vs nomodel for low-depth data, applying ENCODE pseudoreplicate IDR, or reconciling MACS vs HOMER vs SPP results.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes CUT&RUN (Skene Henikoff 2017) and CUT&Tag (Kaya-Okur 2019) chromatin profiling data. Handles SEACR vs MACS2 peak calling (with the btaf375 2025 benchmark guidance), pA-MNase vs pA-Tn5 vs pAG-Tn5 chimera differences, E. coli spike-in carryover normalization, IgG-only control logic (no input), characteristic fragment-size signatures (25-75 bp for CUT&Tag), and lower depth requirements (5M reads typical vs 25M for ChIP). Use when calling peaks from CUT&RUN/CUT&Tag, scaling by E. coli spike-in carryover, choosing SEACR norm mode, or comparing CUT&RUN/Tag results to traditional ChIP.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about passenger-carrying CMVs — buses, motorcoaches, charter operations, school buses, limousines, shuttle services. Covers different HOS rules (10-hour driving / 15-hour on-duty / no 34-restart), Class C CDL with P endorsement, S endorsement for school bus, FMCSA Hours-of-Service for passenger vehicles, $5M insurance minimum, BMC-32 filing, accessibility requirements, and how passenger ops differ from property. Cite 49 CFR 395.5 + 387.33.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a driver or carrier asks about trucker mental health — depression, isolation, stress, fatigue, suicide risk, addiction, EAP programs, or wellness benefits. Covers evidence-based programs, hotlines, carrier-side EAP design, and how mental health affects safety and retention.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about getting/maintaining motor carrier operating authority — USDOT number, MC number, BOC-3 process agent, insurance filing (MCS-90, BMC-91/91X), Unified Carrier Registration (UCR), International Registration Plan (IRP), International Fuel Tax Agreement (IFTA), state-level permits (NY HUT, KY weight distance, OR weight-mile, NM weight distance), new entrant safety audit, intra vs interstate, for-hire vs private. Cite 49 CFR 365, 387, 390.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier asks how to spec a new tractor — engine choice (X15 vs DD16 vs PACCAR MX), transmission (manual vs automated manual vs automatic), axle ratio, sleeper size, fuel tanks, aerodynamic options, electronic features, warranty, fleet-spec vs premium-spec tradeoffs, and how spec choices affect resale value.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier asks about trailer types — dry van, reefer, flatbed, step-deck, conestoga, tanker, dump, lowboy, intermodal chassis, auto-hauler. Covers length / weight rules, common specs, reefer unit options (Carrier vs Thermo King), liftgate options, kingpin setting, and trailer-to-tractor matching.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks where to find specific information at fmcsa.dot.gov — the SAFER (Safety and Fitness Electronic Records System), Carrier Snapshot, Compliance Safety Accountability (CSA) data, PSP (Pre-Employment Screening Program), Clearinghouse, Unified Carrier Registration (UCR), MCS-150 update, complaints, DataQs, and the FMCSA Portal login. Reference fmcsa.dot.gov.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about FMCSA financial assistance + grants — Motor Carrier Safety Assistance Program (MCSAP), High Priority Grants, CMV Operator Apprenticeship Program (CMV-DAP), workforce development funding, hazmat preparedness grants, small carrier financial relief, and state-level grants for trucking infrastructure. Reference fmcsa.dot.gov/grants.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when buying another carrier and inheriting their drivers' DQF library. Covers the legal transfer of DQ records, what new owner must verify, and gaps that commonly require remediation.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about cybersecurity for a trucking carrier — protecting ELD data, customer information, financial systems, EDI integrations, fleet telematics, ransomware risk, vendor / shipper data sharing, incident response, and FMCSA cyber-recommendations. Reference NIST + CISA cybersecurity frameworks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier asks how to calculate cost-per-mile (CPM) at the fleet, truck, lane, or driver level — separating fixed vs variable costs, allocating overhead, accounting for empty miles, and using CPM to negotiate rates, build pricing tiers, or evaluate lane profitability.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier asks about autonomous trucks — current state of Level 4 development, major programs (Aurora, Kodiak, Plus, Waymo Via, Embark history), regulatory status, operational implications, hub-to-hub model, driver impact, insurance, and what carriers should be doing now (or not doing) to prepare.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier asks about disaster recovery (DR) and business continuity planning (BCP) — cyber incident, natural disaster, terminal loss, key-person departure, financial liquidity event, major customer loss, insurance crisis, or fuel supply disruption. Covers risk assessment, continuity strategy, communication plans, and recovery time objectives.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks how to manage a trucking carrier's public reputation — handling a major accident in the news, social media + Glassdoor + Indeed reviews, customer disputes that escalate, employee disputes, regulator perception, and how to communicate during a crisis. Reference industry PR + crisis communication practices.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks the difference between a freight broker, freight forwarder, and motor carrier (49 CFR 371 + 373) — required authority for each, bond requirements (BMC-84 broker bond, BMC-85 freight forwarder bond), broker-carrier agreements, factoring + commissions, double brokering, and how to identify each role on a Bill of Lading. Cite 49 CFR 371 + 373.
日本語の概要は準備中です。原文の説明を表示しています。
Locate CCSPlayer_ItemServices::SetWearables in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the WeaponPaints gamedata entry "CCSPlayer_ItemServices::SetWearables" (symbol CCSPlayer_ItemServices_SetWearables). VIRTUAL function, but WeaponPaints consumes it as a byte signature. Resolve the CCSPlayer_ItemServices vtable via RTTI to locate the slot, then generate a function-head byte signature of the resolved function. The body copies wearable item handles into the pawn's wearable array (m_Item wearables netvar array) and marks state changed. Trigger: CCSPlayer_ItemServices_SetWearables, CCSPlayer_ItemServices::SetWearables
日本語の概要は準備中です。原文の説明を表示しています。