Content Schedule
wolfganghuang0083/content-schedule
Calendário editorial inteligente que prioriza e agenda conteúdo sem colisões
Ver no GitHubSkill Claude que implementa um calendário editorial agnóstico de marca para gestão de conteúdo. Pontua artigos rascunhados por importância (0-100), reserva os de maior impacto nos primeiros slots livres do CMS e rescreve o cronograma na planilha para evitar conflitos entre múltiplos publishedores.
Instalação
npx convez-ai wolfganghuang0083/content-schedule1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Agendar publicações de artigos em CMS WordPress respeitando prioridades estratégicas
- Coordenar calendário compartilhado entre múltiplos autores/editores em uma equipe
- Pontuar conteúdo por importância (papel estratégico, estágio do funil, oportunidade de busca)
Veredito

Ferramenta robusta para orquestração de fluxos de conteúdo em escala, com scoring transparente e integração WordPress pronta. Exige setup técnico (OAuth Google, credenciais CMS) mas resolve completamente o problema de agendamento colaborativo sem conflitos.
README
A tradução para o português deste README ainda está na fila.
content-schedule
📖 手把手 fork + 使用教學(GitHub Pages):https://wolfganghuang0083.github.io/content-ops-toolkit/
A reusable Claude Code / Claude Agent skill — the editorial calendar / scheduling layer for a content map. It scores each drafted article by importance and books it into a CMS publish slot (future), then writes the schedule back to the map so every publisher shares one calendar and nothing collides.
Part of a 4-skill content-ops toolkit: content-map-builder (plan what to write) → content-pipeline (write & draft it) → content-schedule (decide when it goes live) → internal-linking (weave the cluster).
What it does
- Scores importance 0–100 from your content-map columns (strategic role, funnel stage, search opportunity / quick-wins, decision intent, timeliness).
- Books the highest-impact drafts first into the earliest free slots (P0 jumps the queue).
- One shared calendar — reads already-occupied slots (the map's schedule column + existing CMS
futureposts) so multiple publishers never double-book. - Writes back status / scheduled-time / admin-edit link to the map.
Quick start
git clone https://github.com/wolfganghuang0083/content-schedule.git ~/.claude/skills/content-schedule
SHEET=<your content-map sheet id>
BASE=https://your-site.com/wp-json
SITE=https://your-site.com
# 1) See current rows + importance scores (writes nothing)
python3 ~/.claude/skills/content-schedule/scripts/schedule.py --list --sheet-id "$SHEET"
# 2) Plan the calendar (prints, writes nothing)
python3 ~/.claude/skills/content-schedule/scripts/schedule.py --plan --sheet-id "$SHEET" --start 2026-06-13 --per-day 1
# 3) Apply — set CMS future + write back to the map (needs CMS creds in env)
WP_USER=<user> WP_APP_PW='xxxx xxxx xxxx' \
python3 ~/.claude/skills/content-schedule/scripts/schedule.py --apply \
--sheet-id "$SHEET" --base "$BASE" --site "$SITE" --start 2026-06-13 --per-day 1
Setup
- Google access: an OAuth token JSON with the
spreadsheetsscope (default~/.config/google/token.json, override--token/GOOGLE_TOKEN). Requiresgoogle-api-python-client. - CMS auth: env vars
WP_USER/WP_APP_PW(WordPress application password). Never hardcoded. - Column mapping:
scripts/schedule.pyhas aCOLblock at the top — line it up with your content map (the content-map-builder template layout is the default). - CMS swap: WordPress REST is the reference implementation; to use another CMS, replace the
wp()calls.
Scoring rubric (tweak in the CONFIG block)
| Signal | Weight |
|---|---|
| Strategic role | core +35 / blue-ocean +28 / flank +22 / long-tail +12 |
| Funnel stage (time-to-value) | BOFU +25 / MOFU +18 / TOFU +8 |
| Search quick-win | +min(20, impressions/80); +10 if impressions≥200 & CTR<2% |
| Has conversion goal | +6 |
| Decision-intent keyword | +10 |
| Timely topic | +6 |
→ P0 ≥70 · P1 55–69 · P2 40–54 · P3 <40. P0 books the earliest slot; P3 goes to the backlog tail.
License
MIT.