'execution' 검색 결과

Design, analyze, and optimize cold outbound email campaigns on Instantly. Handles end-to-end ICP definition, expert panel scoring (recursive to 90+), sequence copywriting, infrastructure audit, capacity planning, and an implementation/strategy doc for human review. Use when asked to build cold outbound sequences, optimize cold email, audit an outbound motion, write sales sequences, or design cold email campaigns. Supports "start from scratch" and "optimize existing" modes. Execution skill — it produces copy, math, and a doc; it does not auto-send. Requires Instantly for audit/send features.

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

Use to structure a vague marketing request into a well-scoped brief before any real work begins. Triggers on "shape this campaign", "plan this launch", "scope this content", "marketing plan", "growth plan", "content strategy", "outbound plan", or when invoked as the /mshape slash command. Produces a filled brief (campaign, content, optimization, research, or pipeline) that downstream marketing skills can act on. Do not use for work already well-defined — go straight to execution. For engineering task shaping see prompt-shaper; for game-design intake see game-design-shaper.

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

Eng manager-mode plan review. Lock in the execution plan, data flow, diagrams, edge cases.

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

Generate code context for coding tasks. Run before code changes, bug fixes, or refactoring to get execution paths, key files, symbols, tests, and snippets.

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

Generate synthetic code context for LLM coding tasks. Automatically use this before making code changes, fixing bugs, refactoring, or answering questions about the codebase. Provides execution paths, relevant files, symbols, tests, and code snippets.

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

Build or review dygo durable Jobs, Job Executions, queues, workers, retries, idempotency, and Schedules. Use for background or recurring business work.

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

Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.

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

Debug LangChain and LangGraph agents by fetching execution traces from LangSmith. Analyze agent behavior, investigate errors, and review tool calls and performance metrics.

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

Analyze cryptographic code to detect operations that leak secret data through execution timing variations.

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

Reference for MCP Jupyter tools (kernel management, cell execution, Papermill). Use when executing notebooks, managing kernels, or running code interactively via MCP.

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

Use when stuck on a hard problem, decomposition is unclear, a related problem is needed, or explicit looking-back review will improve transfer. NOT for routine execution with a known procedure, rote checklist work, or domain questions that need specialized subject matter expertise instead of heuristic search.

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

Design dashboards for migrations and runtimes. Use for authority drift, verifier status, burn-down, runtime health, or pain panels. NOT for vanity analytics, ad hoc charts, or duplicate reporting.

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

Use for sensemaking, frame revision, anomaly handling, questioning strategy, and ambiguity diagnosis with the Data/Frame model before action is chosen. NOT for deterministic classification, settled execution planning, or situations where the frame is already stable.

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

Decompose DAGs into execution chains using width bounds, stratification, virtual nodes, and matching. Use when minimizing workflow lanes in dependency graphs. NOT for cyclic graphs, generic scheduling, or one-off queries with no preprocessing payoff.

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

ALIAS for dag-orchestrator. The original DAG execution skill, now unified with orchestrator into dag-orchestrator. Use dag-orchestrator for the full HTDAG experience.

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

Identifies when task outputs require iteration based on quality signals, unmet requirements, or explicit feedback. Triggers appropriate re-execution strategies. Activate on 'needs iteration', 'retry needed', 'not good enough', 'try again', 'refine output'. NOT for feedback generation (use dag-feedback-synthesizer) or convergence tracking (use dag-convergence-monitor).

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

Combines and synthesizes outputs from parallel DAG branches. Handles merge strategies, conflict resolution, and result formatting. Activate on 'aggregate results', 'combine outputs', 'merge branches', 'synthesize results', 'fan-in'. NOT for execution (use dag-parallel-executor) or scheduling (use dag-task-scheduler).

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

Synthesizes actionable feedback from validation results, confidence scores, and iteration triggers. Creates structured improvement guidance for re-execution. Activate on 'synthesize feedback', 'improvement suggestions', 'actionable feedback', 'iteration guidance', 'feedback generation'. NOT for iteration detection (use dag-iteration-detector) or convergence tracking (use dag-convergence-monitor).

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

Modifies DAG structure during execution in response to failures, new requirements, or runtime discoveries. Supports node insertion, removal, and dependency rewiring. Activate on 'replan dag', 'modify workflow', 'add node', 'remove node', 'dynamic modification'. NOT for initial DAG building (use dag-graph-builder) or scheduling (use dag-task-scheduler).

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

Manages context passing between DAG nodes and spawned agents. Handles context summarization, selective forwarding, and token budget optimization. Activate on 'bridge context', 'pass context', 'summarize context', 'context management', 'agent context'. NOT for execution (use dag-parallel-executor) or aggregation (use dag-result-aggregator).

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

Algorithms for decomposing DAGs into chains for parallel execution and resource optimization

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

Use when applying Cloudflare D1 migrations, fighting Supabase migration history vs SQL execution, choosing direct psql over CLI, designing idempotent migrations, debugging schema drift between local and remote, or recovering after a half-applied migration. Triggers: supabase migration repair instructions appearing, table missing after "applied" status, "Tenant or user not found" when running psql, --remote vs --local D1 confusion, NOT NULL on a populated column, foreign key constraint failures, drift between staging and prod schemas. NOT for Mongo/document migrations, ORM-managed migrations specifically (Prisma/Drizzle have their own conventions), or pure data backfills.

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

Choose, compare, and decompose work into the right coordination topology: dag, workflow, manager-driven team, swarm, blackboard, team-builder, or recurring loop. Use when the coordination shape is unclear, when you need topology-native breakdown instructions instead of a generic DAG, or when planning topology and runtime topology may differ. NOT for actual execution, node-level skill matching, or framework/tool installation.

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

Track real-time API cost accrual during LLM execution. Activate on 'cost tracking', 'token usage', 'API costs', 'budget monitoring', 'usage metrics'. NOT for cost estimation, pricing tiers, or billing systems.

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