9,764 件 ・ 関連度順
概要と使いどころ
Use when entering a repository with a .ctx/ hub, or when the user asks about project context, agent instructions, tool configuration, health, candidates, broken shims, repair, or cross-tool context.
日本語の概要は準備中です。原文の説明を表示しています。
Determines all follow-up actions due today across the 10-day outreach cadence. Generates content and delivers automatically via Chrome DevTools MCP. Sends Telegram confirmation after completion.
日本語の概要は準備中です。原文の説明を表示しています。
Repurpose one piece of content across six formats while maintaining brand voice
日本語の概要は準備中です。原文の説明を表示しています。
Generate full prospect audit as a sales tool before demos. Combines company research, CRO audit, and person intel into a presentable document with talking points and opportunity sizing.
日本語の概要は準備中です。原文の説明を表示しています。
Takes raw leads and enriches them to outreach-ready status. Chains company-researcher, cro-auditor, decision-maker-finder, apollo-lead-finder, email-validator, and personalization-enricher.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a weekly social media content calendar across platforms. Chains blog-researcher + linkedin-researcher + social-content-writer to produce 5-7 posts/week with posting schedule.
日本語の概要は準備中です。原文の説明を表示しています。
Audit ad-to-landing-page message match, conversion elements, and UX friction
日本語の概要は準備中です。原文の説明を表示しています。
Weekly churn risk detection across active client accounts. Scans for signals like decreased engagement, missed meetings, delayed payments, and competitor mentions. Scores risk 1-10 and outputs prioritized alert list.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates the full multi-channel outreach cadence for all active leads. Tracks where each lead is, generates appropriate content, manages daily caps, handles weekends, and coordinates across email, LinkedIn, Instagram, and phone.
日本語の概要は準備中です。原文の説明を表示しています。
End-of-day response check and pipeline update. Run at 6 PM via cron. Checks all channels for replies via Chrome DevTools MCP + Zoho MCP, updates lead statuses, pauses cadence for responded leads, sends EOD report via Telegram.
日本語の概要は準備中です。原文の説明を表示しています。
Monitor competitor ads across Meta, Google, and LinkedIn with strategic analysis
日本語の概要は準備中です。原文の説明を表示しています。
Full daily team standup across all 6 verticals: Sales, Social Media, Content, SEO, Creative, and Strategy. Spawns all vertical agents in parallel, collects reports, and presents a unified standup summary. Run at 9 AM daily.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a hyperpersonalization packet for each lead by chaining company-researcher, cro-auditor, and person-researcher. The packet feeds into message-generator for Tier 3 personalized outreach.
日本語の概要は準備中です。原文の説明を表示しています。
Reallocate ad budget across campaigns and channels using ROAS and marginal return analysis
日本語の概要は準備中です。原文の説明を表示しています。
Full daily sales pipeline execution. Run at 9 AM via cron. Scans for signals, enriches company leads, auto-applies to gigs, runs multi-channel outreach, processes follow-ups. All delivery automated via Chrome DevTools MCP.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-touch attribution analysis across marketing channels with multiple models
日本語の概要は準備中です。原文の説明を表示しています。
Extract warm prospects from competitor and industry post engagers across LinkedIn, Twitter, and blogs
日本語の概要は準備中です。原文の説明を表示しています。
Generate conversion-focused landing page copy section by section using proven frameworks
日本語の概要は準備中です。原文の説明を表示しています。
MUST USE when asked to find, read, list, search, inspect, fetch, export, or reconstruct coding-agent sessions across Codex, Claude Code/Desktop, Aside, OpenCode, Senpi/pi, OpenClaw, Factory Droid, Amp, Gemini/Kimi/Qwen CLIs, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, Kiro, Goose, Hermes, Crush, Zed, or unknown local agent logs. Uses the repo-backed TypeScript coding-agent-sessions CLI for transcripts, session IDs, rollout JSONL, state SQLite, Claude histories, Aside messages.jsonl, OpenCode sessions, child linkage, cwd/model/time/token filters, archives, and cost clues.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。