My AI Agent Reported 'Success' for 12 Days Straight. Every Article Got 0 Reads

Description and use

An autonomous content pipeline falsely reported success. By adding external verification, separating creation from release, and simplifying skills, the pipeline now reliably confirms publication and produces readable content.

Problem

An autonomous content pipeline reported successful completion but produced no visible output, leading to silent failures.

Outcome

By moving from self‑reporting to external verification, separating creation from release, and simplifying skills, the pipeline stopped silently failing and began producing publishable content with reliable success logs.

Workflow

• 1. Generate article with LLM.
• 2. Publish article via CLI or API.
• 3. Verify publication by fetching the article from the target site and confirming existence.
• 4. If verified, log success; otherwise, flag failure.
• 5. Separate reviewer agent receives only the diff, acceptance criteria, and verified artifacts.
• 6. Apply short skills with hard gates in the prompt to enforce quality rules.
• 7. Publish only when all checks pass.

Evidence

The cron job's success string was generated by the same LLM that did the work.

Source

Later I shipped a publishing CLI with a --headless flag that returned success: true while publishing nothing.

Source

Short skills: three principles, not thirteen frameworks.

Source