원클릭으로
stall-recovery
Execute a stall deal check — query stalled deals, send follow-ups per stage policy, archive long-inactive deals as Lost.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Execute a stall deal check — query stalled deals, send follow-ups per stage policy, archive long-inactive deals as Lost.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | stall-recovery |
| description | Execute a stall deal check — query stalled deals, send follow-ups per stage policy, archive long-inactive deals as Lost. |
When triggered for stall deal check:
/sales-pipeline/stall-deals-policy — get stall_days, archive_days, outreach_cutoff_stage_id, stage_actions.erp_table_data(table_name="crm_deal", options={
"filters": {"AND": [
"contact.contact_last_outbound_ts:<:STALL_TS",
"contact.contact_last_inbound_ts:<:STALL_TS",
]},
"include": ["contact"],
})
deal_details.last_followup_stage). Load the template from template_path in the stage_actions entry (cat that policy document); if absent, use a short generic follow-up. After sending, record last_followup_stage in deal_details to prevent duplicates. Use email_send() tool to do it, and log the activity after (fetch log-crm-activity skill for details).print_widget(type="start_chat", expert="default", text="Stage [stage_name] has stalled deals but no action defined — click to decide what to do.")
Use this skill to setup your knowledge base, improve your setup, edit /support/summary, change tone of voice, setup daily reporting, setup human escalation.
Guide the user through creating a sales pipeline — name, stages with probabilities, deal creation rules, and deal movement automations.
Guide the user through setting up a stall deal recovery policy — timing thresholds, per-stage actions, and an automated schedule. Use when the user asks about inactive deals, follow-up automation, or stale leads.
Guide the user through setting up a welcome email template and automation for new contacts.
Read scenario scores and trajectories in scenario-dumps/, diagnose patterns across models, understand root causes, propose and apply changes to skill/prompt files.
How to log CRM activities (conversations, emails, calls) using erp_table_crud on the crm_activity table. Fetch when you need to record an interaction with a contact.