Build qualified prospect lists using an explicit ICP, source provenance, qualification criteria, scoring, enrichment hygiene and outreach-compliance checks.
日本語の概要は準備中です。原文の説明を表示しています。
225 件 ・ 関連度順
概要と使いどころ
Build qualified prospect lists using an explicit ICP, source provenance, qualification criteria, scoring, enrichment hygiene and outreach-compliance checks.
日本語の概要は準備中です。原文の説明を表示しています。
Design revenue operations across lifecycle stages, lead/account routing, scoring, handoffs, pipeline definitions, CRM hygiene and SLA measurement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "figure out where our direct traffic really comes from", "measure dark social", "add a how-did-you-hear-about-us field", or "show social drives signups without click data"; produces a share-link/UTM hygiene spec for owned share surfaces, a self-reported attribution field design that replaces an existing form field (free-text first, coded later), a GA4 direct-traffic decomposition read (deep-URL directs, mobile-app skew, private-push correlation) with every derived number hard-labeled Estimated/proxy, and a branded-search-lift proxy from GSC plus Wikipedia pageviews — the declared dark-social method behind ECHO O2. Not for paid-channel attribution reconciliation (platform-claimed vs analytics conversions) — use attribution-reconciler. 暗社交归因/直接流量分解/自报来源字段/分享链路UTM
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "plan my paid account structure", "pick Search vs PMax", "lay out ad groups / asset groups", or "audit paid-vs-organic cannibalization"; designs campaign-type selection, ad-group/asset-group layout, targeting + match types, negative/exclusion hygiene, and a paid↔organic overlap audit, and scores the ROAS A (Audience) dimension + structure. Not for computing the final RQS — use ad-account-auditor; not for budget split — use budget-optimizer; not for organic site architecture — use site-structure-optimizer. 付费广告账户结构/广告系列规划/否定关键词
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "QA my conversion tracking before launch", "check my UTMs / pixel / event firing", "set up a tracking pre-flight", or "set the dedup rule so Meta and Google stop double-counting"; builds and fixes the measurement plumbing — conversion-event firing, UTM hygiene, cross-platform dedup rules, attribution-window alignment, and offline/iOS-ATT modeled-gap flags — as a pre-flight checklist plus a UTM/event-spec builder. Not for scoring R1/R2 — that is a scored veto in ad-account-auditor; not for account structure — use campaign-architect. 付费广告转化追踪QA/UTM规范/跨平台去重
日本語の概要は準備中です。原文の説明を表示しています。
Use for any code, documentation, config, dependency, test, review, or maintenance task in the Nauthilus repository that needs worktree hygiene, the project documentation map, focused reproducer-first debugging, Makefile-driven validation, and evidence-backed closeout.
日本語の概要は準備中です。原文の説明を表示しています。
Govern FriendlyBet agent values, professional standards, anti-hallucination behavior, truthfulness, risk reporting, AI resource discipline, feedback loops, skill improvement, performance reviews, decision-rights hygiene, and team quality. Use when creating, reviewing, promoting, correcting, or retiring agents; reducing hallucinations or mistakes; reviewing AI/tool usage; handling agent incidents; or aligning work with Eyal's philanthropic user-first approach.
日本語の概要は準備中です。原文の説明を表示しています。
Control FriendlyBet operating cost, free-tier viability, provider/API cost, GitHub Actions/Supabase/Vercel usage, documentation hygiene, company memory updates, playbook maintenance, and skill validation. Use when evaluating cost, operational burden, tooling, internal docs, company memory, or whether agent profiles should become full skills.
日本語の概要は準備中です。原文の説明を表示しています。
Port-scan, deps, permissions, network, password hygiene.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reporting build, test, or deploy results - enforces real tool output over plausible claims.
日本語の概要は準備中です。原文の説明を表示しています。
Core Swift development workflows for Xcode and Swift tooling, including project setup, dependency management, concurrency guidance, language/runtime best practices, and troubleshooting build or package resolution issues. Use when working on Swift tasks across a codebase, especially package/tooling/runtime work and cross-cutting Swift conventions (mutation semantics, naming, enum/file rules, import hygiene), including in SwiftUI projects.
日本語の概要は準備中です。原文の説明を表示しています。
Token budgeting discipline for all agents. Treats tokens as a resource from session start — not just when the buffer hits 60%. Covers prompt compression, context hygiene, handoff packing, and HOT memory pruning.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: analysing a project's debug and reliability health — inline markers, logging hygiene, and error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Check code for standardization, readability, maintenance complexity, and defensive coding practices
日本語の概要は準備中です。原文の説明を表示しています。
Generates standard operating procedures for B2B SaaS marketing operations: campaign naming conventions, UTM governance, tool administration, workflow QA, data hygiene, lead routing, and incident response playbooks. Use when setting up or auditing marketing ops processes, onboarding a new marketing ops hire, standardizing campaign tracking, fixing broken lead routing, cleaning up HubSpot or CRM data, building QA checklists for campaign launches, or creating incident response procedures for marketing system failures. Also use when asked to "fix our UTM mess," "standardize campaign naming," "build a QA checklist," "audit our marketing ops," or "create an ops runbook." Designed for B2B SaaS marketing teams running HubSpot with multi-geo, multi-segment operations.
日本語の概要は準備中です。原文の説明を表示しています。
Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.
日本語の概要は準備中です。原文の説明を表示しています。
Publish the openrind-desktop-orchestrator npm package with clean git hygiene. Triggers when user mentions: - "openrind-desktop-orchestrator npm publish" - "publish openrind-desktop-orchestrator" - "bump openrind-desktop-orchestrator"
日本語の概要は準備中です。原文の説明を表示しています。
Two-phase memory hygiene. Phase 1: scan external Claude Code memory (~/.claude/projects/<slug>/memory/) for durable rules to migrate into the repo and entries already duplicated by repo atoms. Phase 2: audit in-repo memory/, CLAUDE.md, docs/architecture/, and docs/sections/ for dead links, duplication, drift, and bloat.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Harden an application against common security risks — validate inputs at boundaries, least-privilege access, safe secrets handling, dependency hygiene, and secure defaults. Load when shipping user-facing code, adding auth/session flows, handling untrusted data, exposing APIs, or the user asks for "security hardening", "OWASP hardening", "secure this feature". Not for skill-library security gates (use secure-skill family).
日本語の概要は準備中です。原文の説明を表示しています。
Structure git work with atomic commits, conventional messages, short-lived branches, and pre-commit hygiene. Load when committing, branching, resolving merge conflicts, organizing parallel work, or reviewing git history. Also triggers on "git workflow", "commit message", "conventional commits", "atomic commit", "branch strategy", "git worktree", "how should I commit this". Does not replace project-specific hook policies — complements them.
日本語の概要は準備中です。原文の説明を表示しています。
Normalizes GitHub issue and PR titles by removing any bracketed [NemoClaw] tag case-insensitively, even when the tag appears later in the title. Use when cleaning issue tags, bulk-renaming titles, or normalizing repo title hygiene.
日本語の概要は準備中です。原文の説明を表示しています。
Fail-closed security auditing for OpenClaw/ClawHub skills & repos: trufflehog secrets scanning, semgrep SAST, prompt-injection/persistence signals, and supply-chain hygiene checks before enabling or installing.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge and guardrails for the mise + fnox + infisical secrets toolchain, covering secret injection, secret providers, and env var hygiene.
日本語の概要は準備中です。原文の説明を表示しています。