en un clic
syndly-queue
List the current post queue and its status.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Menu
List the current post queue and its status.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Read-only reference for the Syndly MCP API. Use when an agent hits an MCP error or wants to know what tools are available and how to call them.
Draft a post from a capture using your brand voice profile and the target platform voice.
First-run onboarding. Scaffold ./.syndly/ at the project root and write your brand voice profile plus per-platform tones.
Show news captures that have arrived since your last check.
List, create, edit, and remove content sources that Syndly uses to discover news captures.
Summarise recent post performance with recommendations.
| name | syndly-queue |
| description | List the current post queue and its status. |
Read-only view of what's currently scheduled or queued in Syndly. Use this to check what will go live and when, or to decide whether to back off before running /syndly-draft for a new capture.
Pull the queue. Call the read-only list_posts MCP tool. If you have a post_status filter, use it; otherwise pull everything and filter locally.
Filter to queue-worthy statuses. Keep entries with status ∈ {queued, scheduled}. Verify the actual status strings against src/mcp/schemas/ if there's any doubt — the strings have shifted historically.
Group by channel. Show one section per channel. Within each section, sort by scheduled_for ascending (soonest first). Skip channels with no queued posts.
## X (@acme)
- 09:00 — first-line-of-the-pinned-thread (scheduled)
- 17:00 — capture 2026-07-04 (queued)
## LinkedIn (Acme Engineering)
- 2026-07-08 09:00 — draft v3 (scheduled)
Surface warnings. If the user appears to have many posts queued at the same time on the same channel (≥ 3 posts within a 24h window for X, or any back-to-back LinkedIn posts within 4h), call it out as a question, not a directive — sometimes intentional, sometimes an accident.
Offer follow-ups. After the queue view:
cancel_post or similar); do not invoke it without explicit confirmation/syndly-draft or future ops skills..syndly/drafts/ directly.