Menu
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
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.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/notque/vexjoy-agent --skill content-calendarLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Basé sur la classification professionnelle SOC
Affichage de SKILL.md
| name | content-calendar |
| description | Manage editorial content through 6 pipeline stages. |
| user-invocable | false |
| allowed-tools | ["Read","Write","Bash","Grep","Glob","Edit"] |
| routing | {"triggers":["content pipeline","editorial calendar","publishing schedule","content schedule","publication plan","plan series","multi-part content","content series","article series","content arc","brainstorm topics","content ideas","blog topic ideas","what to write about","angles","story angles","headline","headline options","headline for","headlines","article title","title options","subject line","better title","repurpose this","adapt for social","turn this into posts","content from article","content from demo","content from doc","write variants for","social content from","platform variants","repurpose for","news collection","collect news","qualify news items","news triage","filter news feed","check news freshness"],"not_for":"general research reports — that is research-pipeline. Pick this when the input is a stream of news items to qualify for a content pipeline.","category":"content-creation","pairs_with":["publish","voice-writer","x-api","fact-check"]} |
Manage editorial content through 6 pipeline stages: Ideas, Outlined, Drafted, Editing, Ready, Published. All pipeline state lives in a single content-calendar.md file -- this is the sole source of truth, never store state elsewhere.
| Signal | Load These Files | Why |
|---|---|---|
| calendar file location, template, section formats | calendar-format.md | Loads detailed guidance from calendar-format.md. |
| errors, error handling | error-handling.md | Loads detailed guidance from error-handling.md. |
| velocity tracking and stuck-content detection | metrics.md | Loads detailed guidance from metrics.md. |
| series planning: multi-part structure, cross-linking, cadence | series-planner.md | Series planning domain from folded series-planner skill. |
| topic brainstorming: problem mining, gap analysis, scoring | topic-brainstormer.md | Topic ideation domain from folded topic-brainstormer skill. |
| headlines: charge, volume, tighten, format adaptation | headlines.md | Headline generation domain from folded headlines skill. |
| content repurposing: platform-native social variants | content-engine.md | Content repurposing domain from folded content-engine skill. |
| news collection: item qualification, freshness forensics | news-collection.md | News collection domain from folded news-collection skill. |
| executing view, add, move, schedule, archive operations | operations.md | Loads detailed guidance from operations.md. |
| stage definitions and transition rules | pipeline-stages.md | Loads detailed guidance from pipeline-stages.md. |
Goal: Load and validate the current calendar state before any mutation.
Memory of pipeline state is unreliable -- always read the actual file, because assumed state leads to overwrites of changes made by other processes or manual edits.
content-calendar.md from the project root. Also read the repository CLAUDE.md to ensure compliance with project-specific rules.Gate: Calendar file loaded and parsed successfully. All sections accounted for. Proceed only when gate passes.
Goal: Perform the requested pipeline operation -- only the operation requested. No speculative reorganization, no "while I'm here" reformatting of unrelated sections.
- [ ] [Topic name] to Ideas sectionContent moves forward through defined stages only -- each transition represents real editorial work completed, so skipping stages misrepresents progress.
(outline: YYYY-MM-DD)(draft: YYYY-MM-DD)(editing: YYYY-MM-DD)(ready: YYYY-MM-DD) -- prompt for a scheduled publication date because content without a date clogs the pipeline and goes stale(published: YYYY-MM-DD)Scheduled: YYYY-MM-DD to entryArchive prevents the Published section from growing unbounded, which makes the dashboard cluttered and counts misleading.
### YYYY-MM section in HistoricalGate: Operation executed with all validations passing. Proceed only when gate passes.
Goal: Persist changes and verify the write succeeded.
Read the full calendar file before writing -- never truncate or lose existing entries.
Gate: File written, re-read confirms changes persisted. Operation complete.
Cause: content-calendar.md does not exist in the project
Solution:
Cause: User referenced a topic name that does not match any entry Solution:
Cause: User attempted to skip a stage (e.g., Ideas directly to Ready) Solution:
| Task | Load |
|---|---|
| Stage definitions, transition criteria | ${CLAUDE_SKILL_DIR}/references/pipeline-stages.md |
| File format, section structure, date fields | ${CLAUDE_SKILL_DIR}/references/calendar-format.md |
| Command reference, edge cases per operation | ${CLAUDE_SKILL_DIR}/references/operations.md |
| File not found, corrupt sections, count drift, malformed dates | ${CLAUDE_SKILL_DIR}/references/error-handling.md |
| Velocity metrics, stuck content, pipeline health dashboard | ${CLAUDE_SKILL_DIR}/references/metrics.md |