'one' 검색 결과

Full pipeline from signal detection to scored lead in CRM. Chains signal-scanner, lead-scorer, and crm-writer into one flow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Repurpose one piece of content across six formats while maintaining brand voice

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Extract and codify brand voice from existing content for consistent messaging

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate structured call scripts by persona and lead context

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

One-time CRM initialization. Reads agency.config.json, creates Google Sheet tabs with correct headers, and deploys the webhook Apps Script. Run this once after agency-setup to bootstrap your CRM.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Two-phase Apollo.io prospecting: free People Search to discover ICP-matching leads, then selective enrichment to reveal emails/phones (credits per contact). Deduplicates against CRM (Google Sheets). Supports Apollo API and MCP tools.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ScepticAgent internal architecture reference. Use whenever the user asks how the extension works, wants to add a new AI provider, add a new highlight category, debug communication between components, understand the agent loop or streaming, or work with provider routing and the Gemini CORS proxy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Undo a haircut trim. Puts back the skills, commands, subagents, MCP servers, hooks, plugins and files that haircut parked into a dated bag, using the receipt it wrote at the time. Use this skill whenever the user says undo the cleanup, undo the haircut, put my config back, restore what was trimmed, I need that MCP server again, that skill is gone and I want it back, roll the trim back, what is in the bag, or which files were moved. Use it also when something stopped working right after a config cleanup and they suspect the cleanup caused it, and whenever they ask how to reverse a config cleanup they regret.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn a Git repository URL or local path into one elegant, self-contained HTML learning page that teaches the project's value, architecture, and operating principles top-down with diagrams. Use when the user wants to understand, learn, onboard, explain, map, or study a repository.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use before declaring any coding task complete, done, or finished.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when asked to deploy, release, publish, or ship OpenMeld to production — workers, Web, CLI, or local components. Routes to the guarded release lanes; never deploy raw.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.