Ae1
High
- Category
- analysis-evasion
- Content
2. **Pick a loop** from the catalog in `references/loop-catalog.md` — or adapt the closest one.
- Confidence
- 100% confidence
- Finding
- Referenced artifact was not completely inspected
Security audit
Security checks for vulnerabilities and agentic risk
This markdown-only skill helps plan scheduled marketing workflows and clearly includes review gates, stop conditions, state limits, and kill switches for risky actions.
Before installing, users should treat this as a planning/orchestration skill for marketing automation, not as permission to let an agent spend money, send messages, publish posts, or modify live systems without explicit caps, allowlists, review queues, compliance checks, and a documented way to turn loops off.
2. **Pick a loop** from the catalog in `references/loop-catalog.md` — or adapt the closest one.
2. **Pick a loop** from the catalog in `references/loop-catalog.md` — or adapt the closest one.
{
"id": 6,
"prompt": "We keep losing customers to failed payments and expired cards. Set up something to recover that revenue automatically.",
"expected_output": "Should select the failed-payment/dunning loop. Should trigger on payment failure or upcoming card expiration, run a retry schedule with escalating update-card messaging, and include state (track dunning stage per account, stop on recovery). Must include a stop/bail-out so it doesn't loop forever (escalate/deactivate after final retry) and a self-check to distinguish involuntary failures from intentional cancellations (don't dun someone who chose to leave). Should reference revops and emails skills. May note this is often the highest-ROI retention loop.",
"assertions": [
"Selects the failed-payment/dunning loop",
"Triggers on failed payment or card expiration",{
"id": 6,
"prompt": "We keep losing customers to failed payments and expired cards. Set up something to recover that revenue automatically.",
"expected_output": "Should select the failed-payment/dunning loop. Should trigger on payment failure or upcoming card expiration, run a retry schedule with escalating update-card messaging, and include state (track dunning stage per account, stop on recovery). Must include a stop/bail-out so it doesn't loop forever (escalate/deactivate after final retry) and a self-check to distinguish involuntary failures from intentional cancellations (don't dun someone who chose to leave). Should reference revops and emails skills. May note this is often the highest-ROI retention loop.",
"assertions": [
"Selects the failed-payment/dunning loop",
"Triggers on failed payment or card expiration",{
"id": 6,
"prompt": "We keep losing customers to failed payments and expired cards. Set up something to recover that revenue automatically.",
"expected_output": "Should select the failed-payment/dunning loop. Should trigger on payment failure or upcoming card expiration, run a retry schedule with escalating update-card messaging, and include state (track dunning stage per account, stop on recovery). Must include a stop/bail-out so it doesn't loop forever (escalate/deactivate after final retry) and a self-check to distinguish involuntary failures from intentional cancellations (don't dun someone who chose to leave). Should reference revops and emails skills. May note this is often the highest-ROI retention loop.",
"assertions": [
"Selects the failed-payment/dunning loop",
"Triggers on failed payment or card expiration",No suspicious patterns detected.