「sales」の検索結果

Create interactive AI role-play training activities as self-contained HTML. Use when the user asks to generate a role-play, persona practice, sales simulation, customer conversation drill, compliance scenario, or any learner-vs-AI-character training exercise.

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

Analyze Amazon product, sales, Amazon Ads, retail-readiness, and Best Seller Rank data to find commercially actionable growth opportunities. Use when Codex needs to identify which ASINs, campaigns, keywords, search terms, product targets, placements, categories, or BSR movements deserve more investment, optimization, harvesting, bid/budget changes, retail-readiness fixes, investigation, protection, or controlled scaling across Sponsored Products, Sponsored Brands, Sponsored Display, search term reports, targeting reports, campaign reports, placement reports, advertised/purchased product reports, Business Reports, organic performance, and BSR history.

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

Diagnose why Amazon advertising performance declined for a product, ASIN, campaign, marketplace, or account. Use when the user asks why sales, orders, ROAS, ACOS, TACoS, profit, BSR, rank, traffic, conversion rate, or campaign performance dropped, asks for dropped campaigns, says investigate drop/drop analysis, or asks about wasted spend, negative keywords, negative targets, keywords, targets, or search terms in a drop context.

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

Generate conservative, editable English outreach drafts for foreign-trade sales from structured lead inputs and customer-intel signals. Use when an operator needs a first-touch or follow-up email draft that calls confirmed recent/customer-market signals from the customer-intel Skill, with subject options, review notes, and explicit reminders not to present unconfirmed facts as facts.

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

OpenClaw-native SIEGER-aligned customer intelligence. Use a structured evidence bundle to produce a bilingual report with claim-level evidence, decision gates, industry-specific analysis, and proposed sales angles that require explicit approval before email drafting.

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

Monetization strategies for indie developers, solopreneurs, and small teams. Covers freemium models, SaaS pricing, sponsorships, donations, email list building, and passive income for developer tools, content sites, and educational apps. Activate on 'monetization', 'make money', 'pricing', 'freemium', 'SaaS', 'sponsorship', 'donations', 'passive income', 'indie hacker'. NOT for enterprise sales, B2B outbound, VC fundraising, or large-scale advertising (use enterprise/marketing skills).

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

Enterprise-specific view across CopilotKit + AG-UI. "Enterprise" here = CopilotKit's COMMERCIAL surfaces (Premium / CopilotKit Enterprise / Intelligence Platform / paid tiers), NOT CopilotKit running inside a big company. Tracks the commercial product surfaces (from product-surface-scan — Enterprise Intelligence, Cloud, self-host license, threads/persistence tier, Inspector, premium UI/Angular SDK, analytics, security bundle, Slack/Teams), applies the free-vs-paid classifier to decide if an issue belongs here, surfaces cross-page product contradictions, and tracks enterprise questions/complaints, community-sourced prospects (with a sales owner), and enterprise reporters with prior-week trend. Elevated to the top of the weekly report. Runs standalone ("who's at enterprise this week") or invoked by weekly-report. Triggers on "enterprise report", "enterprise signals", "enterprise status", "who at enterprise this week".

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

Use when designing or auditing a sales pipeline — stage exit criteria, per-cell conversion, coverage reasoning, leak detection. Triggers on 'tighten our pipeline', 'where is the leak'.

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

CRM-lite for managing GEO agency prospects and clients. Track leads through the full sales pipeline: Lead → Qualified → Proposal Sent → Won → Lost. Store audit history, notes, deal values, and generate pipeline summaries. Use when user says "prospect", "lead", "client", "pipeline", "crm", "nuovo prospect", "aggiungi cliente", or when managing the business side of GEO services.

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

Assists users in crafting high-impact pitches, presentations, and sales communications using the "STRONG" method and Frame Control. Use when users want to pitch an idea to investors, sell a product to a client, or need to overcome objections and command attention in business meetings.

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

Pre-share leak scanner for Claude Code skills (or any folder). Scans BEFORE you publish for secrets (API keys, tokens, private keys, .env values, high-entropy strings), PII (emails/phones), local machine paths (C:\Users\<name>, /home/<name>, /Users/<name>, UNC, internal hostnames), and client/proper-noun names from a LOCAL private dictionary; also flags service-specific code (jira/github/gitlab/slack/salesforce/notion/linear/ stripe/aws/google) that should be split into a dedicated service plugin. Use when the user says "sanitize this skill", "before sharing a skill", "check for leaks", "is this skill clean", "is this safe to commit/publish/ open-source", "scrub secrets", "redact before commit", or "pre-push leak check". Cross-platform, stdlib-only Python, fail-closed.

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

This skill should be used when creating UAT (User Acceptance Testing) test cases in Excel format for Salesforce CRM projects. It generates standardized test case documents with summary sheets and detailed test case lists, following a specific format structure with test case ID, priority, category, scenario, preconditions, test steps, expected results, and acceptance criteria.

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

自社の価値記述が十分な売上・利益を上げられるか検証

売上・利益観点での検証結果に基づいて自社の価値記述を洗練・修正する

Scores inbound leads against the qualification rubric the user supplies (criteria, scale, weights, thresholds and disqualifiers as given): one DRAFT scorecard per lead with the evidence quoted per criterion, UNKNOWN wherever the lead's information is missing, totals shown with and without the UNKNOWN criteria, a ranked list and a suggested next step such as a qualification call, a request for missing details, nurture or a courteous decline. Use when the user asks to "score these inbound leads", "qualify this lead against our rubric", "run the web form submissions through our lead criteria", "which of these leads should sales call first" or "build a lead scorecard". Do not use for preparing the first call with a lead, use discovery-call-prep instead; for an existing account's growth plan use account-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as a Chief Business Officer archetype, covering commercial model, partnerships, deal structure, market positioning, strategic fit and opportunity cost, and returns a DRAFT review with a verdict, findings that cite the exact passage, commercial risks and five interrogation questions. Use when the user asks to "run a CBO review", "pressure-test this partnership", "check the deal structure" or "what would a commercial executive say about this". Do not use for pipeline, quota, sales-motion or forecast reviews, use cro-reviewer instead. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as a Chief Marketing Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to specific passages, marketing risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CMO review", "pressure-test the positioning", "what would a CMO say about this", "challenge the launch plan" or "check the messaging and audience". Do not use for price economics, margins or payback, use cfo-reviewer instead; for sales pipeline mechanics, use cro-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck, pricing plan, go-to-market plan or forecast in character as a Chief Revenue Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to exact passages, revenue risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CRO review", "pressure-test the revenue plan", "what would sales leadership say about this" or "challenge this forecast". Do not use for partnership, deal-structure or market-positioning reviews, use cbo-reviewer instead; for the finance seat use cfo-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Operate Lemon Squeezy — the Merchant of Record for digital products and SaaS — via its JSON:API REST endpoints. Covers stores, products, variants, checkouts, orders, subscriptions, customers, and license keys. Use when the user wants MoR billing (EU VAT, chargebacks, sales tax all handled for ~5% + fees) instead of rolling their own with Stripe.

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

Manage the NV oOS Pro Toolkit CRM — leads, deals, companies, contacts, customers, activities, and support tickets. Covers the complete sales pipeline from lead capture through qualification, deal management, and post-conversion customer tracking with BANT/MEDDIC scoring, activity logging, and workflow automation. Use when working with CRM records, managing pipeline stages, qualifying leads, creating company profiles, logging calls/emails/meetings, or troubleshooting CRM data issues.

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

Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline's creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same story lands consistently everywhere. Not for writing the finished surface copy — use each discipline creative builder; not for the tier-scoped launch asset manifest — use launch-asset-packager; not for scoring cross-surface consistency — use narrative-quality-auditor; not for claim adjudication — use offer-claims-registry. 叙事落地/逐面消息一致/创意交接简报/画布传导

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

Route complex marketing work across strategy, narrative, SEO/GEO, CRO, lifecycle, paid, social, influencer, launch, sales and measurement. Use for broad marketing plans, multi-channel work, or when the right specialist skill is unclear.

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

Compatibility skill for geo proposal. Use when a user or upstream workflow invokes this name; route the task to `sales-enablement` while preserving the requested scope and source-specific intent.

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

Use when platform-reported conversions disagree with GA4/ecommerce, when you suspect Meta and Google are double-counting the same sales, or for a standing (monthly) reconciliation workbook that de-dups stacked credit against an order-ID truth set, normalizes attribution windows and currency, compares attribution models, and reads incrementality from a geo/holdout test. Not for the point-in-time R2 veto or RQS gate — use ad-account-auditor; not for the ROI/ROAS ratio math itself — use roi-calculator; not for organic dark-social share attribution or GA4 direct-traffic decomposition — use dark-social-attributor. 付费广告归因对账/去重/增量

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