Ccfddl X Posts

CCFDDL X Posts

Create up to two English digests per publication day: one AI, one Data Systems, with concise countdown text, a matching readable PNG, and https://ccfddl.com.

Campaign contract

• Use exactly the verified X account @ccfddl. Do not treat a display name, brand name, or workspace as account proof.
• Include CCF A and CCF B conferences plus explicit ICLR and MLSys exceptions. Classify sub: AI as AI and all remaining source subjects as Data Systems. This is the requested campaign grouping, not a claim about the source taxonomy.
• Publish in the morning in America/Los_Angeles, with automatic daylight-saving changes. Prefer flexible scheduling around 08:00 local; do not impose an exact time unless requested.
• Use English as the stated operational default. Preserve later user changes in campaign configuration.
• Publish at most one digest per category per local calendar day. Choose future abstract or paper deadlines within the configured 120-day horizon, up to six text rows. Show only the first three rows in the image, followed by an ellipsis when more eligible rows exist. Keep all candidates when they fit; on overflow, retain representation of both eligible CCF A and CCF B tiers instead of allowing nearer B deadlines to displace every A conference. Record any omissions in the manifest and surface material omissions rather than silently hiding a tier. Skip empty categories.
• Include no unrelated posts, replies, DMs, follows, or engagement actions. Do not put credentials, account identifiers beyond the public handle, private state, or publication ledgers in the public source repository.
• Treat this skill as the workflow, not proof that a schedule or publishing connection exists. Never report live posting as enabled without verifying the actual provider and schedule.

Read references/config.json for editable campaign settings. Read references/source-and-publishing.md for source mapping, identity, conflict handling, provider checks, and state transitions.

1. Check the connection and authorization

Before creating a scheduled task, perform a harmless read through the intended publishing route and verify an authenticated X account whose exact normalized handle is ccfddl. Prefer a suitable connected provider; an authorized authenticated X browser is an alternative when no suitable provider is available. For a provider, discover its tools and supported media/publication operations; do not guess them. For a browser route, inspect the actual signed-in profile and composer and verify that the scheduling environment can use that authenticated session. Never assume the current browser login will be available to a future task.

If the chosen route is unconnected, unauthenticated, or points at another account, prepare previews and report the precise blocker. Use the supported plugin or browser login setup flow. Respect cancelled login/setup requests and wait for the user to continue rather than automatically reopening them. Metricool is optional; do not require it or subscribe to a paid service without authorization. For Metricool, a connected plugin alone is insufficient: read brand settings and verify an actual connected X network. Do not guess the info JSON schema or media-file format for createScheduledPost; inspect current tool documentation and official provider documentation first. Do not request or store an API key or password in chat. Installing this skill does not connect X.

For Buffer API/MCP, require a verified public-image hosting route before enabling this image-post campaign: local PNG files cannot be attached directly, and the image URL must remain accessible until publication completes. Never submit a private Library download or signed URL. If this media gate is unresolved, keep publication blocked; do not silently post text alone or claim end-to-end setup is complete. See the Buffer media gate in the source-and-publishing reference.

Use the user's bounded authorization for this recurring campaign. Ask before expanding its audience, topic, account, or scope. Obtain any additional action-specific confirmations required by the platform or applicable policy. Do not publish a preview merely to test the connector.

2. Acquire a coherent current source

Use the verified canonical source: https://github.com/ccfddl/ccf-deadlines, directory conference/. Fetch the latest default-branch commit read-only and pin every YAML file to that same full 40-character SHA. Verify the source against official CFP/date pages whenever a record changes, an ambiguity appears, or a known conflict needs resolution.

Use the bundled snapshot command on a fresh, read-only checkout, or construct the same snapshot with authorized connector results. Do not edit the conference repository as a side effect of publication.

python3 <skill>/scripts/countdown.py snapshot --repo <fresh-read-only-source-checkout> --output <run>/snapshot.json

The snapshot stores repository, commit, fetched_at_utc, complete_catalog, and files (path, exact UTF-8 content, SHA256). When assembling with a connector, set complete_catalog: true only after confirming all conference YAML paths at that commit were retrieved. Sample subsets must have complete_catalog: false and remain previews. snapshot reads committed Git objects, never uncommitted working files.

Never convert TBD, historical patterns, website estimates, conference dates, decisions, rebuttals, or camera-ready dates into submission deadlines. Preserve source seconds. Resolve AoE as UTC−12, fixed UTC offsets explicitly, and IANA zones with date-specific DST. Reject incomplete dates and ambiguous/nonexistent local DST times. Interpret PT as America/Los_Angeles. Quarantine unknown timezone labels rather than guessing.

Apply only the explicitly evidenced, exact-fingerprint EDBT 2027 official clock correction in the config; recheck its official page before publication, retain the original value in the private manifest, and stop for review if the source fingerprint changes to an unrecognized instant. Do not silently publish the known-bad AoE value.

Keep the existing MLSys 2027 exact-clock quarantine until the conflicting official sources agree or the organizer resolves it. Report the discrepancy without selecting whichever time is convenient. Retain MLSys in the campaign scope for other verified editions.

3. Build and inspect

Use a current explicit UTC as-of time. Require Python 3.10+, PyYAML, Pillow, and Liberation Sans (Arial-compatible). Use the executor's existing packages or an authorized reputable package source; do not silently install from an unknown source.

python3 <skill>/scripts/countdown.py build \
  --snapshot <run>/snapshot.json --config <skill>/references/config.json \
  --as-of <current-UTC-ISO8601> --output <run>/posts --preview

For an actual publication run, omit --preview after all gates are satisfied. A non-preview build requires a complete catalog, confirmed editorial configuration, and a snapshot fetched within 15 minutes. Recheck latest source SHA immediately before sending; if it changed, regenerate the affected content before posting.

Inspect every final PNG with an image-view tool. Confirm legible text, no overlaps/clipping, correct category, approved heading and event labels, exact deadline and zone, branding, and no crossed-out footer elements. Keep as-of UTC and source SHA in the private manifest only; retain the canonical link in tweet text, not in the image. Adapt the live repository email reminder template (worker/src/email_reminders.js) for social cards: gray page, white bordered cards, brick-red reminder accent, Arial-compatible sans-serif typography, and countdown → event title → exact deadline hierarchy. Use exactly NAME YEAR Abstract Deadline for abstract events and NAME YEAR Deadline for paper events, retaining a meaningful round label. Do not display an abstract closed warning in tweet text, cards, or alt text; keep the factual flag in the private manifest only. Set the card heading to the exact tweet heading. Remove the in-image website CTA and the visible as-of/source footer; preserve top branding, REMINDER, DEADLINE NOTICE, and the good-luck/team closing. Use the final category-specific plain-text contract below for tweet wording and retain category names on the attached cards. Omit unsubscribe/settings controls and retain ccfddl.com in tweet text only. Preserve precise elapsed-time countdowns rather than copying email calendar-day arithmetic. Every countdown is a snapshot, not a live clock.

Inspect the manifest and each tweet. Honor the skipped-for-review list. Preserve round labels and distinguish abstract from paper. Keep the passed-abstract fact internally, but omit its public qualifier as requested. Such paper deadlines apply to already-registered submissions; do not claim a new submission is still possible. Keep stage_selection: nearest as the default: select the next future deadline per timeline round deterministically. When multiple stages are explicitly selected, support separate rows with stage_selection: all_future; do not change the campaign default merely because the wording changed. Preserve every selected stage and display every abstract_deadline as abstract in both text and card, even when the official site calls it registration. Keep the official term only in source provenance, never as a reg/registration display override.

Keep the full selected digest in the text (up to six rows). Render only its first three rows in the card and add an ellipsis if additional eligible entries exist. Do not add an ellipsis when there are no additional entries. Preserve events (all text rows), card_events (visible image rows), and card_has_more separately in the manifest. Make alt text describe only the visible image rows and the ellipsis, without claiming all text rows are pictured. Keep the default digests concise. Treat the script's weighted-length count and 280-character advisory as editorial diagnostics, not a universal hard limit: the connected account may support Premium long posts. Check the actual provider/account capability. Keep the current approved six-row compact style within the verified account limit; if it does not fit, report the tradeoff instead of silently dropping CCF A entries or changing the requested format. The script counts the canonical URL as 23 characters, NFC-normalizes Unicode, and conservatively overcounts complex emoji. Never use a naive character count, silently truncate, or automatically split a digest into a thread. If the provider returns a text-too-long error, report the exact error and do not rewrite and retry without new authorization. Include alt text from the manifest when the selected route supports it.