← ClaudeAtlas

citely-connectlisted

Connect a website to Citely so published articles appear on the site immediately. Use when the user wants to receive blog content from Citely (citely-seo.com), build a reader for the Citely read-API, implement a CPP webhook receiver, wire a deploy hook, or debug articles that publish in Citely but take hours to appear on the site. Pairs with the blog-builder skill for rendering.
stephenpham68/citely-blog-kit · ★ 0 · DevOps & Infrastructure · score 72
Install: claude install-skill stephenpham68/citely-blog-kit
# Citely Connect — receive articles, show them instantly Wire the user's site to Citely so that **one publish in Citely = article live on the site within seconds to ~1 minute**. Rendering quality is the `blog-builder` skill's job; this skill covers transport and freshness. ## Source of truth: fetch the live spec first Before writing any code, fetch the canonical integration spec — it is versioned and maintained by Citely; do not rely on memorized field lists: ``` Fetch https://citely-seo.com/connect/v1/agent.md ``` Everything below is decision guidance layered on top of that spec, not a replacement for it. ## When to use - The site should display articles written/published in Citely. - Building the reader (Mode A) or webhook receiver (Mode B/C) for Citely Connect. - Articles publish in Citely but appear on the site late (minutes–hours) — see `references/instant-publish.md`. ## When NOT to use - Designing/styling the blog UI itself → `blog-builder` skill (use both together: this skill delivers the data, blog-builder renders it). - WordPress sites — Citely has a native WP plugin; no custom integration needed. ## Required inputs (ask if missing) 1. **Stack + hosting** — Next.js/Astro/Hugo/…, and whether pages are SSG (static export), SSR/on-demand, or ISR. This decides the mode *and* the freshness wiring. 2. **Site token + read-key** — from the user's Citely dashboard (Websites → Connect). The read-key is **server-side only** (`CITELY_READ_KEY` env); it must never rea