「vendor」の検索結果

A platform decision framework for experimentation. When to use Statsig vs PostHog vs GrowthBook vs Optimizely vs Amplitude vs Eppo vs Kameleoon. How to migrate between them. How to coordinate when multi-platform is genuinely warranted. The decisions that compound for years and the ones you can defer. Triggers on which experimentation platform, choose Statsig vs PostHog, evaluate experimentation tools, switch experimentation platform, migrate from Optimizely, consolidate experimentation tools, multi-platform experimentation, experimentation platform decision, ab test platform selection, feature flag platform vs experiment platform, warehouse-native experiments, vendor lock-in experimentation. Also triggers when a team is asking about cost, governance, or migration cost across experimentation tools, or when an evaluation is starting.

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

Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts. Use this skill whenever the user wants to create brand guidelines, document an existing brand, build a brand book, audit an existing style guide for completeness, or produce the artifact that other teams will reference for years. Triggers on style guide, brand guidelines, brand book, brand standards, brand manual, style sheet, brand documentation, brand reference. Also triggers when the brand identity is finished and needs to be documented for handoff to designers, developers, vendors, or future team members.

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

Self-update mechanism. Detects git vs vendored install. Auto-upgrade option with escalating snooze backoff. Syncs global and local copies. Extracts CHANGELOG bullets post-upgrade.

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

Categorize invoices and receipts by vendor, expense, and tax bucket, detect duplicates, and produce a tax-ready monthly summary. Use during bookkeeping, tax prep, or expense reimbursement.

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

Contract review assistant analyzing agreements against playbooks. GREEN/YELLOW/RED severity. Use when reviewing vendor contracts, SaaS agreements, service agreements, or generating redline suggestions.

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

Operations management across process optimization, efficiency, and continuous improvement. Use when designing workflows, building capacity plans, evaluating vendors, running Lean Six Sigma DMAIC projects, or optimizing cost-per-unit.

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

Operations leadership advisor on business operations, process optimization, and scaling infrastructure. Use when designing operational processes, planning headcount capacity, optimizing vendors, or scaling operations.

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

Cut software and services spend through seat-utilisation analysis, redundant-tool detection, and renewal-timing leverage. Use when auditing SaaS spend, preparing a renewal negotiation, or hunting a budget-reduction target.

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

Security leadership for growth-stage companies. Use when building security programs, selecting compliance frameworks (SOC 2, ISO 27001, HIPAA, GDPR), managing incidents, or assessing vendor risk.

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

Pick the right LLM for CONTRACT REVIEW — reviewing an existing agreement for risk, deviations from standard, missing protections, and internal contradictions, and proposing redlines. Vendor-neutral routing grounded in mid-2026 legal benchmarks. Contract review is a COMPOSITE skill (extraction + reasoning + redlining + conflict-detection), so this routes by the dominant sub-task. Asks up to 4 quick questions (cost, speed, accuracy/stakes, privacy/jurisdiction/ language), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model to review this contract / NDA / MSA", "best AI to redline", "route this contract review", or is about to review an agreement without a fixed model.

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

Pick the right LLM for LEGAL TRANSLATION — translating contracts, statutes, case law, and legal correspondence across languages, including Arabic/MENA. Vendor-neutral routing triangulated from mid-2026 evidence (WMT25 human eval, SwiLTra-Bench legal-MT, multilingual-reasoning proxies, ArabLegalEval). There is NO clean legal-translation leaderboard, so this vertical is directional and treats human legal-linguist review as mandatory. Asks up to 4 quick questions (language pair, cost, speed, privacy/certification), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model to translate this contract/statute", "best AI for legal translation", "translate this legal doc to/from Arabic", or is about to machine-translate legal text without a fixed model.

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

Pick the right LLM for LEGAL INFO EXTRACTION — pulling facts, clauses, dates, parties, obligations, and structured fields out of contracts and legal documents. Vendor-neutral routing grounded in mid-2026 benchmarks (legalbenchmarks.ai Info Extraction; CUAD/MAUD/ACORD). Asks up to 4 quick questions (cost, speed, accuracy/stakes, privacy/jurisdiction/language), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model should I use to extract clauses/data from these documents", "best AI for contract data extraction", "route this extraction task", or is about to pull structured fields from legal docs without a fixed model.

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

Pick the right LLM for LEGAL RESEARCH & ANALYSIS — issue-spotting, rule application, case/statute analysis, memos, and multi-step agentic research. Vendor-neutral routing grounded in mid-2026 benchmarks (Vals AI LegalBench across 124 models; Harvey Legal Agent Benchmark for agentic work). Asks up to 4 quick questions (cost, speed, accuracy/stakes, privacy/jurisdiction/language), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model for legal research / case analysis / a memo", "best AI for legal reasoning", "route this research task", or is starting legal analysis without a fixed model.

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

Pick the right LLM for CONTRACT DRAFTING — generating, redlining, or rewriting contract language from instructions. Vendor-neutral routing grounded in mid-2026 legal benchmarks (legalbenchmarks.ai Contract Drafting). Asks up to 4 quick questions (cost, speed, accuracy/ stakes, privacy/jurisdiction/language), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model should I use to draft this clause/agreement", "best AI for drafting contracts", "route this drafting task", or is about to generate/redline contract text and hasn't fixed a model.

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

Review contracts against your organization's negotiation playbook, flagging deviations and generating redline suggestions. Use when reviewing vendor contracts, customer agreements, or any commercial agreement where you need clause-by-clause analysis against standard positions.

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

Performs structured compliance review, clause redlining, and drafting suggestions for legal documents (privacy policies, data processing agreements, vendor and SaaS contracts) against India's DPDPA 2023 and the EU GDPR. Flags clauses as compliant, at-risk, or non-compliant with reasoning, and proposes ready-to-use model replacement language.

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

Generate templated responses for common legal inquiries and identify when situations require individualized attention. Use when responding to routine legal questions — data subject requests, vendor inquiries, NDA requests, discovery holds — or when managing response templates.

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

Probe IoT/embedded targets for exposed SWD/JTAG debug interfaces using a SEGGER J-Link. Detects whether debug is OPEN, LOCKED (readout-protected), or DEAD (fused off). Use when assessing whether a target's on-chip debug port can be reached, identifying the silicon vendor from DPIDR/IDCODE, and confirming halt+memory access for full debugger control.

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

A parser for mzIdentML files implemented using the XML package. The parser tries to be general and able to handle all types of mzIdentML files with the drawback of having less 'pretty' output than a vendor specific parser. Please contact th

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

Dung khi can GIAO VIEC cho tung nguoi trong team marketing hoac chuan bi hop — task cu the, deadline theo gio, definition of done, rang buoc, diem check-in, kem template agenda va bien ban hop lien phong ban co action item. Kich hoat khi user nhac 'giao task cho team', 'brief cho nhan vien', 'phan cong cong viec', 'brief 1:1', 'definition of done', 'template hop', 'agenda hop marketing', 'giao viec xong lam sai y'. Khong dung cho — brief tong the ca chien dich thi dung skill 02-brief-chien-dich; duyet output nguoi ta nop len thi dung skill 62-marketing-review; danh gia hieu suat dinh ky thi dung skill 65-team-performance-review; giao viec ra ben ngoai thi dung skill 67-agency-vendor-brief.

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

Dung khi da co y tuong va can huong dan NGUOI QUAY hoac NGUOI DUNG PHIM — storyboard tung beat, footage phai quay, chu chay tren man hinh, nhac, nhip cat, end-frame CTA va spec xuat theo kenh. Khac script video: script la loi thoai, day la huong dan dung. Kich hoat khi user nhac 'brief video', 'brief editor', 'storyboard', 'brief dung phim', 'huong dan cat video', 'brief videographer', 'editor cat khong dung y', 'video dai qua can cat lai'. Khong dung cho — viet loi thoai va hook noi truoc camera thi dung skill 04-script-video; nho khach hoac nhan vien tu quay thi dung skill 06-brief-ugc-egc; thue production house tron goi thi dung skill 67-agency-vendor-brief.

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

Dung khi can brief NGUOI KHAC quay video ho — khach hang lam UGC, nhan vien lam EGC, hoac KOC va creator tra phi: tieu chi chon nguoi, huong dan quay tung canh, viec nen va khong nen lam, quyen su dung hinh anh, bang quan ly batch va cach do hieu qua. Kich hoat khi user nhac 'brief UGC', 'brief EGC', 'brief KOC', 'thue creator quay', 'huong dan nhan vien quay video', 'tim KOC o dau', 'creator quay sai y', 'hop dong quyen su dung video'. Khong dung cho — viet loi thoai kich ban video thi dung skill 04-script-video; huong dan editor dung phim thi dung skill 44-brief-video-editor; rai comment seeding duoi bai dang thi dung skill 38-seeding-plan; thue agency hoac production house lam tron goi thi dung skill 67-agency-vendor-brief.

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

Use when a leader assigns work to a marketing team member or runs a cross-functional meeting — a task brief with concrete deliverables, a deadline with time and timezone, a definition of done, constraints, and check-in points, plus an async-first meeting agenda and action-item template. Trigger on 'assign a task', 'brief for my team', 'team brief', 'definition of done', 'meeting agenda template', 'my team keeps delivering the wrong thing'. Also use when the user says nobody knows who owns what. Not for — the campaign brief the whole team executes from, see `02-campaign-brief-global`; briefing an external agency or freelancer, see `67-agency-vendor-brief-global`; evaluating performance, see `65-team-performance-review-global`.

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

Generate a Disaster Recovery plan with RTO/RPO targets. Use when someone asks to "create a DR plan", "disaster recovery", "business continuity", or "RTO RPO". Do NOT use for step-by-step restoration runbooks — use /pmstudio-recovery instead. Designed for SaaS platform products where Coco Inc is the customer — focuses on service continuity, data recovery, and vendor dependency management rather than infrastructure rebuild.

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