Agent Workflow Skill: Adding a "Single-Slot Gate" to Daily Publications

In automated content systems, the most easily overlooked risk is not "no publication at all," but "double publication." If a failed draft has already been written to the production database, and a correct version is subsequently published, two `published` records will appear for the same day and category. While the page might still load, integrity checks, indexing, recommendations, and subsequent analytics will become unreliable.

The "single-slot gate" approach is straightforward: before any publication action begins, query whether a `published` record already exists for the same category, date, and language. If one exists, halt the automatic publication and route the task to manual remediation or an explicit override process. This check must occur before writing to the database, rather than relying on post-publication audits to detect issues.

This skill is suitable for scenarios such as daily articles, daily reports, product announcements, release notes, model evaluation reports, and any content scheduled by date. It is not appropriate for open-ended repositories, which may inherently allow multiple entries per day. However, if the business semantics dictate "one entry per category per day," this should be enforced as a hard rule.

A practical checklist:

• Query for existing `published` rows for the target date before publishing.
• If a record already exists, output the specific ID and slug, and do not proceed with writing.
• If backfilling a historical gap is necessary, an explicit `override` flag must be passed.
• After publication, run an audit for the same date and category to confirm that only one set of slugs exists across all three languages.
• Do not delete failed drafts; archive them as `archived` to preserve troubleshooting evidence.

The value of this gate lies in shifting duplicate publications from "online data repair issues" to "local pre-publication failures." The longer the automation pipeline, the more essential such small but rigid rules become. This approach does not aim for intelligent judgment; it simply enforces a baseline: one business slot can only have one official result.