「capa」の検索結果

Marketing analytics and data-driven optimization for B2B SaaS campaigns. Use this skill when analyzing marketing performance, optimizing conversion rates, running A/B tests, conducting customer research, creating marketing dashboards, building attribution models, analyzing funnel metrics, or storytelling with data. Also triggers on: marketing ops, performance analytics, CRO, A/B testing, data storytelling, customer insights, tracking plan, event taxonomy, UTM taxonomy, GA4 audit, consent mode, instrumentation contract, sample size calculation, minimum detectable effect, test duration, not enough traffic to A/B test, statistical significance, Bayesian vs frequentist, sample ratio mismatch, experiment feasibility, martech stack, marketing tech stack audit, tool consolidation, build vs buy, vendor evaluation, shadow IT tools, ESP/CRM/platform migration, switching cost, cutover plan, suppression list migration, data portability, customer interviews, survey design, sampling frame, non-response bias, how many people should I interview, thematic saturation, voice of customer, jobs-to-be-done, buyer persona research, is this finding real, data enrichment, which enrichment provider should we buy, waterfall enrichment, contact data quality, match rate, our list data is bad, email verification, catch-all domain, accept-all, bounce rate from bad data, B2B data decay, how often should we re-verify contacts, ZoomInfo vs Apollo vs Clearbit evaluation, cost per usable record, where did this list come from, GDPR Article 14 notice, purchased list compliance, suppression screening, TAM list building, demand planning, marketing plan, how many leads do we need, what pipeline target should marketing carry, funnel model, top-down vs bottom-up plan, plan of record, annual marketing planning, quarterly planning, pipeline coverage we have to create, sales cycle lag, our leads cannot close this quarter, carry-in pipeline, scenario planning, conservative moderate aggressive forecast, stretch target, reforecast, re-forecast triggers, assumption register, capacity ceiling, addressable audience ceiling, marginal cost per lead, blended CPL is wrong, we missed plan and nobody knows why, AI policy for the marketing team, AI governance, AI acceptable use policy, which AI tools are we allowed to use, can I paste customer data into ChatGPT, shadow AI, AI use register, human review of AI output, when can we stop reviewing every AI draft, can the agent send on its own, the AI made a mistake now what, pull back AI autonomy, AI evals, our AI vendor changed the model, AI output went out wrong, prompt injection, can our AI read prospect replies safely, lethal trifecta, the AI leaked internal notes, turn off auto-generated ad assets, auto-applied recommendations, AI literacy training, EU AI Act Article 4, duplicate records in the CRM, dedupe before import, which value wins in a merge, CRM cleanup.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of an Emergency Management Director — activating and staffing an EOC for a developing hazard, sequencing a disaster declaration and FEMA Public Assistance/Individual Assistance request, sizing shelter and resource needs against real population and capacity numbers, designing or critiquing a tabletop exercise, or writing an after-action report and improvement plan.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of an Entertainment and Recreation Manager (theme park, arena, recreation facility, tour operation) — planning attraction/facility capacity against attendance forecasts, evaluating a guest safety or ride-operations decision, pricing admission/season-pass programs, or managing seasonal staffing and weather-driven demand swings.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Conveyor Operator — diagnosing a mistracking belt before it becomes edge damage or spillage, verifying every lockout/tagout isolation point on a conveyor with a gravity take-up or incline before entering the nip zone, calculating each conveyor's actual delivered capacity in a multi-conveyor line to find the true bottleneck, deciding whether a mechanical or vulcanized splice fits a given tension rating, or judging whether a pinch-point guarding gap needs an immediate stop versus a scheduled fix.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Computer Hardware Engineer — designing a power delivery network and selecting decoupling capacitors for a digital IC's core rail, budgeting a high-speed signal's rise time against trace impedance and via stub length, closing static timing on a board-level DDR or SerDes interface, sizing thermal resistance for a package's TDP, or reviewing a PCB layout for signal- or power-integrity risk before fab release.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Conservation Scientist — writing or reviewing a rangeland/forest conservation plan, calculating stocking rate or carrying capacity against a proposed grazing or timber plan, scoping a prescribed-fire prescription, resolving a multi-use land-allocation conflict on public or private land, or assessing range/forest condition trend from monitoring data.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Civil Engineer — sizing stormwater detention/drainage systems, checking foundation bearing capacity against a geotechnical report, verifying IBC/ASCE 7 code compliance for site civil work, reviewing construction RFIs against stamped drawings, or evaluating value-engineering changes for safety-margin impact.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of clergy or a pastoral-care leader — triaging a pastoral-counseling disclosure against a referral to licensed mental-health or medical care, mediating a congregational conflict, navigating clergy-privilege/confidentiality boundaries, planning an officiated ceremony with legal requirements, or right-sizing a volunteer program against committed capacity.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Business Continuity Planner — running a business impact analysis (BIA) to derive recovery time objectives, mapping process dependencies to find single points of failure, evaluating whether current recovery capability meets a process's maximum tolerable downtime, designing or debriefing a tabletop exercise, or building the cost-benefit case for a continuity investment.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of an Art Therapist — matching art media to a client's regulation capacity via the Expressive Therapies Continuum, scoring a standardized directive (PPAT, KFD, DAP) with a validated instrument like FEATS as part of assessment, deciding between a directive and open-studio session structure, navigating informed consent and disposition for client-made artwork, or distinguishing an art-as-therapy approach from an art-psychotherapy approach for a given client.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Farmer, Rancher, or other Agricultural Manager — deciding a planting/breeding mix or acreage shift under price and weather uncertainty, sizing a hedge or crop-insurance coverage level, running break-even and diversification scenarios before a capital or input commitment, or evaluating land/herd management practices against long-term productive capacity.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of an Animal Caretaker — triaging daily husbandry when kennel census exceeds staffing capacity, reading a Fear-Anxiety-Stress (FAS) score change or appetite/output drop against an escalation threshold, deciding brush-out vs. shave-down on a matted coat, or setting isolation and vaccination-lead-time protocol for a new intake or boarding admission.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of an agricultural engineer — sizing a center-pivot or drip irrigation system's peak capacity against crop water demand, computing lateral grain-bin wall pressure with Janssen's equation, sizing a waterway or tile-drainage system with Manning's equation and an NRCS design-storm return period, or building a manure/nutrient first-year availability mass balance against a crop's N requirement.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of an Agricultural Equipment Operator — calibrating planter seed population and singulation, diagnosing combine header or separator loss, sequencing planting or harvest across fields under a weather-constrained window, sizing machinery capacity in acres/hour against a season's acreage, or evaluating PTO/grain-bin entrapment safety on a job site.

日本語の概要は準備中です。原文の説明を表示しています。

List, select, and install Volcengine skills from the volcengine-skills marketplace. Use when a user asks which Volcengine skill or plugin handles a task, wants to browse every available skill, needs an optional skill that is not currently installed, or asks to install or check the installation status of a Volcengine skill. Also use to discover any core skill, including this finder. Use as a fallback during a Volcengine operation when the currently loaded or installed skills cannot cover the required product, tool, or workflow; inspect the full catalog, select the missing capability, and install it.

日本語の概要は準備中です。原文の説明を表示しています。

Query and answer questions about Volcengine API specifications. Use when the user asks about API parameters, error codes, request methods, enum values, required fields, response structures, pagination, parameter dependencies, service capability lists, API availability, or API comparisons, even if they do not explicitly say "API". Typical intent includes checking what an action supports, which fields are required, what values a parameter accepts, why an API returns a specific error, how to pass nested or body parameters, how pagination works, what an API response contains, whether a batch operation exists, what services or versions expose an operation, or how two APIs differ. Use API Explorer data as the authoritative source and preserve constraints, examples, and caveats found in the spec. Answer in Chinese or English. When the user needs runnable SDK code, language-specific examples, or SDK configuration, hand off to volcengine-sdk-generator. When they need CLI operations, hand off to volcengine-cli.

日本語の概要は準備中です。原文の説明を表示しています。

Help users draft and, when authorized, submit feedback to volcengine/volcengine-skills: skill problems, missing capabilities, cloud scenarios, and successful Agent workflows. Use for explicit feedback or sharing requests, or an optional invitation at a natural summary after Volcengine CLI errors or an incompletely solved task. Feedback never blocks the main task.

日本語の概要は準備中です。原文の説明を表示しています。

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.

日本語の概要は準備中です。原文の説明を表示しています。

Guidance for Tauri v2 plugin permission authoring, capability generation, and platform differences.

日本語の概要は準備中です。原文の説明を表示しています。

Guidance for Tauri v2 capabilities, scope configuration, and ACL-based permission control.

日本語の概要は準備中です。原文の説明を表示しています。

Safe systematic dependency upgrade with vulnerability scanning and rollback capability. Detects project ecosystem, audits outdated and vulnerable packages, presents a prioritized upgrade plan, and executes upgrades one at a time with test verification after each. Use when updating dependencies, fixing vulnerability alerts, or performing periodic dependency maintenance.

日本語の概要は準備中です。原文の説明を表示しています。

JLCPCB PCB fabrication and assembly — BOM/CPL generation, basic vs extended parts, assembly constraints, design rules, ordering workflow. Use with KiCad for JLCPCB manufacturing. Use this skill when the user mentions JLCPCB, wants to order PCBs or assembled boards, needs prototype bare PCBs and stencils, wants to know JLCPCB design rules and capabilities, or is asking about PCB manufacturing costs or turnaround times. For gerber/CPL export, stencil ordering, and BOM management, see the `bom` skill.

日本語の概要は準備中です。原文の説明を表示しています。

Design tools for AI agents — clean function interfaces, typed schemas, informative errors, idempotency, and tool documentation. Use when giving an agent new capabilities or fixing flaky tool use.

日本語の概要は準備中です。原文の説明を表示しています。

Use for feedback and feature requests to the Muse team. Whenever your response tells the user you can't do a specific thing they wanted, or accepts them giving up on one, offer once to file feedback in that response. This covers missing integrations you can't do yourself, capabilities you lack, and tasks that keep failing at a specific point. File only on their go-ahead. Also use when asked to send, view, check, or withdraw feedback.

日本語の概要は準備中です。原文の説明を表示しています。