Cross-channel campaign performance analysis with blended CAC and budget recommendations
日本語の概要は準備中です。原文の説明を表示しています。
8,388 件 ・ 関連度順
概要と使いどころ
Cross-channel campaign performance analysis with blended CAC and budget recommendations
日本語の概要は準備中です。原文の説明を表示しています。
Builds Quarterly Business Review decks for active clients. Pulls metrics, generates structured QBR with wins, challenges, roadmap, and recommendations. Uses crm-writer to read client data.
日本語の概要は準備中です。原文の説明を表示しています。
Turns client wins into structured case studies in multiple formats. Gathers before/after metrics, structures as Problem-Solution-Results, and outputs landing page copy, one-pager, social snippets, and email insert.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-touch attribution analysis across marketing channels with multiple models
日本語の概要は準備中です。原文の説明を表示しています。
Generate formatted video scripts from transcripts, outlines, or topics with visual and audio columns
日本語の概要は準備中です。原文の説明を表示しています。
Analyze conversion funnel drop-offs and identify biggest leak points with impact-ranked recommendations
日本語の概要は準備中です。原文の説明を表示しています。
Transform raw transcripts, notes, or topics into polished long-form articles in the founder's voice
日本語の概要は準備中です。原文の説明を表示しています。
Analyze A/B test results for statistical significance with ship, extend, or kill recommendations
日本語の概要は準備中です。原文の説明を表示しています。
OneClickVirt operations skill for managing containers, virtual machines, provider nodes, health checks, and metrics through MCP.
日本語の概要は準備中です。原文の説明を表示しています。
Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.
日本語の概要は準備中です。原文の説明を表示しています。
Gates whether a new test should exist and forces it to be efficient, protecting CI from low-value test bloat. Use before any change to what a pytest, Jest, or Playwright test asserts or sets up, down to one fixture or one assertion added to an existing block. Front-loads the value bar (every test must catch a realistic regression no existing test already catches; extend the nearest existing test before writing a new standalone one; test behavior through the public interface, not implementation details; collapse near-duplicates into parameterized cases) and the efficiency bar (deterministic, isolated, fast; pick the cheapest test level; Django TestCase over TransactionTestCase; no sleeps, no real network; no time bombs from absolute dates left to age against the real clock; no database a test never uses). Includes a "don't write it" decision tree. For fixing an existing flaky test use `/fixing-flaky-tests`; after this gate says a Playwright test is warranted, use `/playwright-test` for mechanics.
日本語の概要は準備中です。原文の説明を表示しています。
Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run, Depot runner, workflow, job, shard, merge queue kick, flaky test, lint failure, typecheck failure, snapshot diff, migration check, generated types drift, or skills build failure. Start with the `hogli ci:insights` digest (cross-run CI history from engineering analytics), then guides read-only inspection, failure classification, smallest local reproduction with hogli, and safe reporting without rerunning CI or posting to GitHub. Running unattended as the "Master-red diagnosis" workflow: see references/master-red-incident.md.
日本語の概要は準備中です。原文の説明を表示しています。