Communitygithub.com

jeremylongshore/tons-of-skills-marketplace

Operate an evidence-backed editorial queue, balance topic and format coverage, schedule approved drafts, and reconcile backlog state with the publishing system. Use when choosing or scheduling the next blog work. Trigger with "show the editorial calendar" or "pick the next topic".

What is tons-of-skills-marketplace?

tons-of-skills-marketplace is a Claude Code agent skill that operate an evidence-backed editorial queue, balance topic and format coverage, schedule approved drafts, and reconcile backlog state with the publishing system. Use when choosing or scheduling the next blog work. Trigger with "show the editorial calendar" or "pick the next topic".

Works with✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/HEAD/plugins/productivity/publishing-skills/skills/blog-editorial-calendar

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Editorial Calendar Operations

Overview

Maintain a durable editorial backlog and select the next work from evidence rather than intuition. This skill balances configured topic clusters and post formats, reserves publishing slots, and reconciles local state with the real CMS before changing the queue.

It coordinates blog-topic-research and seo-blog-writer; it does not replace their research, drafting, review, or publishing controls.

Prerequisites

  • An approved config.json defining target_platform, author, UTC cadence, cluster targets, format targets, and CMS tag mappings
  • A writable backlog.json with stable IDs, titles, clusters, formats, evidence URLs, priorities, statuses, and scheduled timestamps
  • Read-only CMS listing access for sync; separate approved write access only when the user requests scheduling or publication
  • blog-topic-research for backlog replenishment and seo-blog-writer for draft production
  • Topic and format target weights that each total approximately 1.0

Tool Discipline

Use Read to inspect configuration and backlog state. Use WebSearch and WebFetch only to confirm public evidence or read the authorized CMS inventory. Use Write or Edit for reviewed, secretless state updates; never write credentials, raw access tokens, or unpublished sensitive content into receipts.

Instructions

  1. Parse the requested action: status, next, add, mark-done, or sync. Reject unknown actions and mutually incompatible scheduling flags.
  2. Read and validate config.json and backlog.json. Confirm unique IDs, valid statuses, parseable UTC timestamps, nonnegative priorities, and target weights near 1.0.
  3. Run a read-only reconciliation before selection. Match CMS records by stable CMS ID first, canonical URL second, and normalized slug only as a last resort. Report ambiguous matches instead of guessing.
  4. For next, score only eligible ready items. Rank cluster deficit first, then format deficit, evidence strength, explicit priority, and oldest creation time. Record the score factors so the choice is reproducible.
  5. Reserve the selected item with a stable run ID. For --draft, invoke the writer without a publish time. Otherwise choose the next free configured UTC slot or validate each explicit slot.
  6. Require review before any live publish or schedule mutation. Pass the topic scaffold and approved target to seo-blog-writer; do not copy CMS credentials into the handoff.
  7. Commit the state transition only after the downstream operation returns a durable draft ID, CMS ID, or explicit failure. Move ready -> reserved -> drafted -> scheduled -> published; never skip directly to published without CMS evidence.
  8. For add, normalize the title and compare it with existing titles, slugs, canonical URLs, and distinctive error/version tokens. Add only evidence-backed, nonduplicate topics.
  9. For mark-done, require a matching live URL or an owner-approved manual receipt. For sync, preserve local notes while updating only fields supported by CMS evidence.
  10. Return the chosen work, schedule, state changes, conflicts, and next eligible slot. Leave failed or ambiguous items recoverable.

Selection Contract

Each backlog record should include:

{
  "id": "topic-0042",
  "title": "How to diagnose webhook signature failures",
  "cluster": "integrations",
  "format": "how-to-fix",
  "status": "ready",
  "priority": 2,
  "evidence_urls": ["https://example.com/verified-source"],
  "scheduled_at": null,
  "cms_id": null,
  "canonical_url": null
}

Selection must be deterministic for the same configuration, backlog, and CMS snapshot. Never fabricate traffic, demand, availability, or publication evidence.

Approval Boundaries

Ask for owner approval before scheduling, publishing, rescheduling, deleting, bulk-mutating, or overwriting reconciled backlog state. A read-only status or dry-run selection does not require CMS write access. Default to draft when publication intent is absent.

Output

Return a compact operational receipt containing:

  • action, run ID, timestamp, and configuration checksum
  • selected IDs and score factors
  • old and new statuses
  • draft, schedule, CMS ID, and canonical URL when available
  • conflicts, skipped duplicates, shortfalls, and required approvals
  • next eligible slot and recommended follow-up

Error Handling

ConditionResponse
Missing or invalid configurationStop before mutation and list the exact invalid keys or totals.
CMS inventory is unavailableMark reconciliation unverified; allow local dry-run status but do not claim a slot is free or a post is live.
Two records match one CMS postPreserve both records, report the collision, and require an owner decision.
Downstream drafting failsRelease the reservation or mark it blocked with the failure receipt; do not consume the slot.
Queue has no eligible topicsReport the shortfall and invoke blog-topic-research only with the approved cluster and count.
Concurrent update changes the backlogRe-read, recompute, and require confirmation if the selected item or slot changes.

Examples

Dry-run the next two selections without publishing:

request: next 2 --draft --dry-run
result: topic-0042 (integrations deficit 0.08), topic-0017 (use-cases deficit 0.05)
mutation: none
next_slot_utc: 2026-09-12T06:00:00Z

Reconcile an already published item:

request: sync
matched: topic-0042 -> cms_id=post_918 by canonical_url
transition: scheduled -> published
conflicts: 0

Verification

  • Re-run status and confirm the recorded counts equal the backlog totals.
  • Confirm no two active records share a CMS ID or canonical URL.
  • Confirm every scheduled timestamp fits a configured slot and no slot is double-booked.
  • Confirm every published record has a CMS-derived ID or owner-approved receipt.
  • Confirm a second dry-run against unchanged inputs returns the same ranking.

Resources

Next Steps

Review target weights monthly against actual business priorities and search performance. Revalidate platform APIs before changing the reconciliation adapter.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

jeremylongshore/tons-of-skills-marketplace

Use when asked to structure a landing page for positioning, plan a conversion-optimized page layout, or design a launch page. Examples: "landing page for product launch", "conversion-optimized layout for SaaS

jeremylongshore/tons-of-skills-marketplace

Use when asked to design growth-optimized landing pages, activation funnel layouts, or experiment-friendly page structures. Examples: "growth-optimized landing", "activation funnel layout", "A/B testable page

jeremylongshore/tons-of-skills-marketplace

Use when asked to structure a landing page, design page layout for conversion, or plan landing page information architecture. Examples: "landing page structure for SaaS", "conversion-optimized layout

jeremylongshore/tons-of-skills-marketplace

Generate polished demo videos from a single prompt. Use when the user asks to create a demo video, product walkthrough, feature showcase, or animated presentation. Trigger with "make a demo video", "create a product video", "demo walkthrough", or "feature showcase video".

jeremylongshore/tons-of-skills-marketplace

Track cryptocurrency portfolio with real-time valuations, allocation analysis, and P&L tracking. Use when checking portfolio value, viewing holdings breakdown, analyzing allocations, or exporting portfolio data. Trigger with phrases like "show my portfolio", "check crypto holdings", "portfolio allocation", "track my crypto", or "export portfolio".

jeremylongshore/tons-of-skills-marketplace

Runs the full release workflow for the current project. Commits any uncommitted changes, pushes to remote, creates and merges a PR if on a feature branch, determines the next semver version from conventional commits, creates an annotated git tag and GitHub release with generated notes, cleans up merged branches, and returns to a clean main. Use when the user says promote, ship, release, commit and push, tag and release, or get back to main.

jeremylongshore/tons-of-skills-marketplace

Agent skill at plugins/productivity/content-multiplier/skills/channel-formats/SKILL.md

jeremylongshore/tons-of-skills-marketplace

Configure CI/CD pipeline for AppFolio property management integrations. Trigger: "appfolio CI".

jeremylongshore/tons-of-skills-marketplace

Diagnose and fix common AppFolio API integration errors. Trigger: "appfolio error".

jeremylongshore/tons-of-skills-marketplace

Build property management dashboard with AppFolio API data. Trigger: "appfolio property dashboard".

jeremylongshore/tons-of-skills-marketplace

Automate tenant management and lease operations with AppFolio. Trigger: "appfolio tenant management".

jeremylongshore/tons-of-skills-marketplace

Collect AppFolio API debug evidence for support tickets. Trigger: "appfolio debug".

jeremylongshore/tons-of-skills-marketplace

Deploy AppFolio integration service to cloud infrastructure. Trigger: "deploy appfolio".

jeremylongshore/tons-of-skills-marketplace

Query AppFolio properties, units, and tenants via REST API. Trigger: "appfolio hello world".

jeremylongshore/tons-of-skills-marketplace

Configure AppFolio Stack API authentication with OAuth 2.0. Use when setting up property management API access, registering as an AppFolio Stack partner, or configuring client credentials for API calls. Trigger: "install appfolio", "setup appfolio", "appfolio auth", "appfolio API key".

jeremylongshore/tons-of-skills-marketplace

Set up local development for AppFolio property management API integration. Trigger: "appfolio local dev".

jeremylongshore/tons-of-skills-marketplace

Production readiness checklist for AppFolio integrations. Trigger: "appfolio production checklist".

jeremylongshore/tons-of-skills-marketplace

Handle AppFolio API rate limits with throttling and backoff. Trigger: "appfolio rate limit".

jeremylongshore/tons-of-skills-marketplace

Reference architecture for AppFolio property management integration. Trigger: "appfolio architecture".

jeremylongshore/tons-of-skills-marketplace

Apply production-ready patterns for AppFolio REST API integration. Trigger: "appfolio patterns".

Related Skills