Extract line items and delivery details from a customer purchase order PDF, then generate a formatted order confirmation PDF ready to send back to the buyer.
日本語の概要は準備中です。原文の説明を表示しています。
1,006 件 ・ 関連度順
概要と使いどころ
Extract line items and delivery details from a customer purchase order PDF, then generate a formatted order confirmation PDF ready to send back to the buyer.
日本語の概要は準備中です。原文の説明を表示しています。
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Map a thesis's position in its value chain — who it buys from, sells to, and competes with; where the bottleneck and pricing power sit; and whether it owns a critical layer. Use when user says "value chain", "supply chain position", "where does [TICKER] sit", or "who are [TICKER]'s suppliers/customers".
日本語の概要は準備中です。原文の説明を表示しています。
Extract a thesis's dependency fingerprint — the external variables its bull case actually rests on (key customers, suppliers/inputs, technology transitions, macro drivers, single points of failure). Use when user says "dependency map", "what does [TICKER] depend on", "dependency fingerprint", or "map exposures for [TICKER]".
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
日本語の概要は準備中です。原文の説明を表示しています。
Braintree Automation: manage payment processing via Stripe-compatible tools for customers, subscriptions, payment methods, and transactions
日本語の概要は準備中です。原文の説明を表示しています。
Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier asks which KPIs to track, how to build a fleet dashboard, what targets to set, cadence for reviewing metrics (daily / weekly / monthly / quarterly), and how to operationalize data into actions. Covers safety, operations, financial, driver, and customer KPIs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a dispatcher, operations manager, or owner asks how to plan loads to minimize empty (deadhead) miles, sequence freight efficiently, balance regional capacity, design dedicated loops, or build a load-pairing strategy across customers. Covers loaded-ratio math, lane balance, region-pair pricing, and software-supported optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier (asset-based, brokerage, or 3PL) asks how to respond to a shipper RFP / RFQ — bid packaging, lane analysis, rate strategy, SOPs/SOWs, qualifications response, insurance compliance, EDI requirements, and how to win competitive bids without leaving margin on the table.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about CMV operation types — Dedicated, OTR (Over-the-Road), Regional, Local, and the differences in driver lifestyle, pay, equipment, home time, hours, and customer mix. Reference industry segmentation conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about trucking dispatch software — McLeod, TMW (Trimble), Tailwind, Truckbase, AscendTMS — vs load boards — DAT, Truckstop, 123Loadboard, Convoy, Uber Freight. Covers the workflow (find load, book, dispatch, run, settle), how dispatch software integrates with ELDs + accounting + customer EDI, and what small fleets vs larger fleets typically use.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a manager, dispatcher, or safety director needs to have a coaching conversation with a driver — about a safety event (harsh brake, hard turn, distraction), an HOS violation, a customer complaint, a missed delivery, repeated minor incidents, or to deliver positive recognition. Covers conversation structure, language, documentation, and escalation.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about buying or selling a trucking company — valuation drivers (revenue, fleet age, CSA scores, customer concentration), asset purchase vs stock purchase, FMCSA authority transfer, due diligence checklist, common deal structures (cash, earnout, seller-financed), and what changes operationally after acquisition. Reference 49 CFR 365.401 (authority transfer).
日本語の概要は準備中です。原文の説明を表示しています。
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 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 market a trucking company — sales channels, prospecting, website + brand, industry directories (D&B Hoovers, ZoomInfo), referral programs, content marketing, and ROI of different acquisition channels. Reference industry sales practices.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to explain to customers/sales prospects why FMCSA CSA scores are not available in real-time. Covers the SAFER refresh cycle and what 'real-time' actually means for CSA data.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Connect a customer agent to Coval and complete a small first evaluation with inspected voice or chat results. Use when no usable evaluation exists yet; reuse existing recordings and resources when available.
日本語の概要は準備中です。原文の説明を表示しています。
Improve Coval trace quality after basic ingestion works. Use when traces are sparse, missing useful STT/LLM/TTS/tool spans, missing attributes needed for Coval built-in metrics, or when a customer wants maximum debugging and observability value from agent traces.
日本語の概要は準備中です。原文の説明を表示しています。