128 件 ・ 関連度順
概要と使いどころ
Rebate Management setup: rebate types, payout calculations, accruals, partner rebates, program setup, compliance reporting. NOT for Sales Agreements or channel revenue management — use integration/manufacturing-cloud-setup. NOT for CPQ discounts on quotes — use admin/cpq-pricing-rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or validating the end-to-end quote-to-cash process on standard Salesforce: Opportunity to Quote to Synced Quote to Approval Process to Quote PDF to Order creation. Trigger keywords: quote approval, discount policy, quote PDF limits, order from quote, quote sync, quote template. NOT for CPQ pricing rules or discount schedules — use admin/cpq-pricing-rules. NOT for building the quote template itself — use admin/quotes-and-quote-templates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when configuring the Salesforce product catalog and pricing structure: creating Product2 records, setting up Standard and custom Pricebooks, managing PricebookEntry junction records, enabling multi-currency pricing, configuring Product Schedules (Revenue and Quantity), or troubleshooting incorrect prices on Opportunity line items and Quotes. Triggers: 'add product to pricebook', 'pricebook entry', 'standard pricebook', 'product catalog', 'multi-currency product pricing', 'product schedule', 'revenue schedule', 'quantity schedule', 'deactivate product'. NOT for bulk catalog loads — use data/product-catalog-data-model. NOT for CPQ bundles and product rules — use admin/cpq-product-catalog-setup.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or troubleshooting Salesforce CPQ (SBQQ) quote templates: building template sections, configuring line columns, conditionally showing sections, generating branded PDFs, or handling multi-language output. Triggers: 'CPQ quote template', 'SBQQ template', 'CPQ PDF', 'line columns', 'quote template sections', 'conditional section', 'CPQ quote document'. NOT for standard non-CPQ quote templates in Setup — use admin/quotes-and-quote-templates. NOT for a Visualforce-built quote PDF — use apex/quote-pdf-customization.
日本語の概要は準備中です。原文の説明を表示しています。
Non-interactive content-production toolkit: mine quotable moments from podcast RSS feeds and meeting notes, discover clip-worthy moments in video transcripts, repurpose long-form source into platform-native drafts (X, LinkedIn, YouTube Shorts, newsletter), and batch-score/gate those drafts before publish. Use when asked to "mine quotes from this podcast", "find clips in this video", "repurpose this into a thread / LinkedIn post / Short", "turn this transcript into posts", "extract viral moments", or "gate this batch of drafts". Runs Python scripts end to end. For interactive expert-panel scoring of a single artifact see content-ops.
日本語の概要は準備中です。原文の説明を表示しています。
Forces Claude to extract exact quotes from files before making claims about them. Prevents hallucinations by grounding every statement in actual text from the codebase. Use when working with large files or unfamiliar code.
日本語の概要は準備中です。原文の説明を表示しています。
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
日本語の概要は準備中です。原文の説明を表示しています。
Bexio Swiss business software API for managing contacts, quotes/offers,.
日本語の概要は準備中です。原文の説明を表示しています。
Format and publish rich Notion documents with structured sections, code blocks, tables, callouts, quotes, mermaid diagrams, and emojis. Use when the user asks to organize, write, or save content to Notion (e.g., "notion에 정리해줘", "notion에 저장해줘"), or when invoked with /notion-format. Detects content type (tech-doc, meeting-notes, analysis, tutorial, bug-report) and applies the appropriate formatting template automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need this project's coding standards (line length, quotes, import order, naming, commit format) — derive them from the REAL tooling config as a pointer + digest, never a guessed claim.
日本語の概要は準備中です。原文の説明を表示しています。
Use when shaping a discovery slice — JTBD-framed interview guide, switch-event focus, verbatim quotes not summaries. Triggers on 'talk to users', 'why did they cancel', 'before we build X'.
日本語の概要は準備中です。原文の説明を表示しています。
Builds DRAFT user personas from the research notes, interview summaries, survey free text and support themes the user provides: for each persona the goals, pains, jobs to be done, context of use, quotes exactly as supplied with their participant codes, and the evidence count behind every attribute, with names, demographics and any detail no participant stated left UNKNOWN rather than invented. Use when the user asks to "build personas from these interviews", "who are our users based on this research", "draft user personas", "turn these research notes into personas" or "update our personas with the new interviews". Do not use for theming a batch of customer feedback into counts, use customer-feedback-theme-synthesis instead; for exit interviews, use exit-interview-synthesis; for the requirements those personas imply, use product-requirements-draft. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts one anonymised DRAFT case study (situation, approach, outcome as evidenced, optional lessons) from engagement notes, status reports, closing reports, emails and metrics extracts the user supplies, with a fact trace to the notes, an evidence grade on every result, quotes only where the user supplied them with speaker role and permission, an anonymisation log and a confidentiality checklist that must be completed before publication. Use when the user asks to "write a case study from these notes", "turn this engagement into a customer story", "draft a success story for the website", "anonymise this project write-up" or "prepare a reference case for the proposal". Do not use for redacting identifiers from an existing document, use document-deidentification-pass instead; for checking whether a document's claims are substantiated, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesises training survey responses and manager notes into a DRAFT training needs report by role: coded needs with record counts per role (n of N), the evidence type behind each count, anonymised quotes cited to record codes, disagreements between what staff report and what managers observe, gaps where a role is under-represented or a required skill has no evidence, and follow-up questions to settle before any course is designed. Never rates an individual, ranks a team or turns a count into a competence verdict. Use when the user asks to "analyse this training survey", "what training do our teams need", "summarise the manager feedback on skills gaps", "build a training needs analysis by role" or "which roles have the biggest skill gaps". Do not use for turning an agreed need into a course, use course-outline-builder instead; for exit interviews, use exit-interview-synthesis. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Answers an employee's or manager's HR policy question strictly from the policy documents the user supplies or the agent can reach as knowledge: a DRAFT answer that quotes the governing clause with its document, version and clause reference, lists the conditions and exceptions the text states, returns UNKNOWN where the documents are silent and names the role to ask. Never invents a rule, fills a gap from general practice or decides an individual's case. Use when the user asks to check a policy, for example "what does the policy say about", "am I entitled to", "how many days of leave do I get", "what is the process for requesting", "does the handbook allow" or "which clause covers". Do not use for comparing two policy versions or briefing a change, use policy-change-briefing instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Turns one meeting transcript or recap into a DRAFT action-items document (decisions, owned and dated action items with verbatim source quotes, open questions), a task list ready for the user to enter into their task tracker, and one DRAFT follow-up email per action owner, all returned in the chat for the user to store, create or send. Use when the user shares, names or points to a meeting transcript or recap and asks to "pull the action items from this transcript", "who owns what after today's call", "draft follow-up emails to each owner" or "turn this recap into tasks". Do not use for full minutes, use meeting-minutes-writer instead; a brief before a meeting is meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a set of questions (form exports, helpdesk logs, meeting Q and A, chat threads, a plain list) plus the source documents the user supplies into a DRAFT FAQ grouped by theme: every answer quoted or paraphrased from a named source with a reference, verbatim quotes for dates, figures, eligibility and obligations, UNKNOWN where the sources are silent, a source register with precedence, a conflicts table and a routing list of unanswered questions to owners. Use when the user asks to "build an FAQ from these documents", "answer these questions from the policy", "turn the Q and A into an FAQ page", "group these questions and answer them from the guide" or "what do our documents say about these questions". Do not use for the manager FAQ of a changed HR policy, use policy-change-briefing instead; for checking whether a document's own claims are evidenced, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesises a batch of customer feedback (survey answers, reviews, ticket and chat comments) into a DRAFT themed report: coded themes with record counts and shares, anonymised verbatim quotes cited to record codes, contradictions and unverified claims, and the follow-up questions to answer next. Produces no sentiment score or percentage positive as fact; ratings appear only as distributions with n. Use when the user asks to "theme this feedback", "what are customers saying", "summarise these survey answers", "analyse these reviews", "find the top complaints in these comments" or "code this voice of the customer data". Do not use for exit interviews, use exit-interview-synthesis instead; for sorting a live queue and drafting replies, use ticket-triage-pack; for project retrospectives, use lessons-learned-synthesis. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "build a media list for my launch", "write a launch press release", or "pitch press under embargo"; produces a three-tier media and analyst list (Tier 1 exclusive candidates, Tier 2 vertical press, Tier 3 communities and newsletters), an embargo pitch timing skeleton keyed to the launch-registry date, a press-release draft in standard structure with no fabricated quotes or numbers, and an analyst briefing outline. Not for press-kit assets — use launch-asset-packager; not for follow-up sequence mechanics — use outreach-manager; not for post-launch news-echo monitoring — use launch-monitor. 媒体名单/禁运期pitch/新闻稿/分析师简报
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "triage launch feedback", "cluster reviews, comments, and board posts into themes", or "set up a you asked, we shipped loop"; produces a feedback theme digest (frequency, severity, representative quotes per theme), an open→planned→started→completed/declined status loop with duplicate-merge and notification rules, shipped-change announcement material, and a compliant social-proof harvest protocol (never incentivized store reviews). Not for repurposing or amplifying the harvested proof — use content-amplifier; not for executing testimonial outreach threads — use outreach-manager. 反馈分诊/状态环/社证收割/评测合规
日本語の概要は準備中です。原文の説明を表示しています。
Stock quotes, history, search, compare, crypto via Yahoo.
日本語の概要は準備中です。原文の説明を表示しています。
Stock quotes, price history, financial news, and analysis
日本語の概要は準備中です。原文の説明を表示しています。
Personal App-in-Skill inbound-inquiry reception desk (Busabase App-in-Skill) for cross-border/foreign-trade sellers, aggregating WhatsApp, Instagram, Messenger, and email inquiries into a pipeline with a product knowledge base, quote worksheet, approval queue, and follow-up reminders. Use when the user invokes $kelly-inquiry or /kelly-inquiry, mentions 询盘, inquiry desk, WhatsApp leads, quote management, 报价, foreign trade sales, follow-up reminders, or a lead pipeline, wants inquiries triaged into new/replied/quoted/negotiating/won/lost stages, agent-drafted replies and quotes reviewed before sending, or stale deals surfaced.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch a URL and save the body to a temp file so you can pipe it through rg / jq / awk instead of dumping the whole page into the conversation. Use this whenever a user gives you a URL to read - articles, docs, PRs, gists, README files, blog posts, anything HTTP. Returns a path on disk; the agent then greps the path for the relevant section and quotes only what matters. Strongly preferred over the built-in webfetch tool when (a) the page is more than a few KB, (b) the user wants to find a specific phrase / table / code block on the page, (c) you need to keep the long page out of context, or (d) you want to inspect raw HTML alongside rendered markdown. Triggers: 'fetch', 'fetch this URL', 'fetch and save', 'fetch the page', 'pull this', 'grab this article', 'read this URL', 'read the docs at', 'mirror this page', 'page is too long', 'save the page so I can grep it', 'put it on disk so I can rg', 'cache this URL'.
日本語の概要は準備中です。原文の説明を表示しています。