Builds drip email campaigns for leads not ready to buy. Determines segment and buying stage, selects content per stage, and generates a complete 5-7 email sequence over 30 days with timing and content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
3.2만건 · 관련도순
Builds drip email campaigns for leads not ready to buy. Determines segment and buying stage, selects content per stage, and generates a complete 5-7 email sequence over 30 days with timing and content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define and refine ICP segments with persona cards and validation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find 5 decision makers at a company via Apollo.io UI using Chrome DevTools MCP. No enrichment, no credits used.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Framework-based cold email composer with 3 personalization tiers. Generates subject line, body, and follow-up variants. Never uses templates -- builds from frameworks (PAS, BAB, AIDA, Signal-Proof-Ask).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates personalized proposals for freelance gigs on Upwork, Freelancer, PeoplePerHour, and Guru. References specific project requirements and includes relevant case studies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up GitHub Actions CI pipeline with test, lint, type-check, and build jobs for a Node.js/TypeScript project. Includes output grouping, error annotations, and job summary patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Patterns for writing comprehensive Vitest test suites in TypeScript projects. Covers shared test utilities, vi.mock for module mocking, fixture directories, provider/adapter testing, and state management testing. Tier - generic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or needing current model specifications. Covers SDK usage (google-genai for Python, @google/genai for JavaScript/TypeScript, com.google.genai:google-genai for Java, google.golang.org/genai for Go), model selection, and API capabilities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guidelines for Chrome extension development with Manifest V3, covering security, performance, and best practices
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate multi-agent swarms with agentic-flow for parallel task execution, dynamic topology, and intelligent coordination. Use when scaling beyond single agents, implementing complex workflows, or building distributed AI systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build an app with Remotion
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add Gmail integration to NanoClaw. Can be configured as a tool (agent reads/sends emails when triggered from WhatsApp) or as a full channel (emails can trigger the agent, schedule tasks, and receive replies). Guides through GCP OAuth setup and implements the integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants local voice transcription instead of OpenAI Whisper API. Switches to whisper.cpp running on Apple Silicon. WhatsApp only for now. Requires voice-transcription skill to be applied first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add /compact command for manual context compaction. Solves context rot in long sessions by forwarding the SDK's built-in /compact slash command. Main-group or trusted sender only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Replace OneCLI gateway with the built-in credential proxy. For users who want simple .env-based credential management without installing OneCLI. Reads API key or OAuth token from .env and injects into container API requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Quick read-only health check — session context, workspace mounts, tool availability, and task snapshot. Use when the user asks for system status or runs /status.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when `hogli ci:insights` or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a flaky job, when asked to check Trunk Flaky Tests for a test, PR, or master, or when asked to deflake, stabilize, or fix a flaky Jest, pytest, or Playwright test. Core discipline: reproduce locally before changing anything, fix the root cause (never mask it with sleeps, retries, or bigger timeouts), and prove the fix with an N-run validation loop sized to the observed failure rate. Stabilizing is not the only valid outcome — the skill also gates whether the test should exist, so deleting a test that catches nothing real, or re-leveling one that flakes because of the level it runs at, are first-class endings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.