publish-metadata
Skill0 starsChanged 5 months agoMITView on GitHub
Write the publish metadata for a finished content item — title variants, SEO description, tags, chapters, and the finalized pinned/engagement comment. Runs at the publish stage of a content-pipeline project, after the render is approved. Use when completing publish.md for a stockpiled item.
In this repository57 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-mattSkill
- cast-memberSkill
- check-feedbackSkill
- codebase-designSkill
- content-pipeline-initSkill
- content-pipelineSkill
- data-analystSkill
- decision-mappingSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- draft-asset-promptsSkill
- edit-articleSkill
- fableSkill
- game-concept-interviewSkill
- git-guardrails-claude-codeSkill
- global-guidelinesSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- karpathy-guidelinesSkill
- launch-sessionSkill
- lesson-reviewSkill
- link-claude-skillsSkill
- loop-meSkill
- migrate-to-shoehornSkill
- obsidian-vaultSkill
- opusSkill
- prototypeSkill
- resolving-merge-conflictsSkill
- retrieve-lessonsSkill
- reviewSkill
- rotate-sessionSkill
- run-buildSkill
- run-clipsSkill
- scaffold-exercisesSkill
- session-sandboxSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- setup-status-lineSkill
- showrunner-shortSkill
- sonnetSkill
- tddSkill
- teachSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- verify-outputsSkill
- wrap-allSkill
- wrapSkill
- writing-beatsSkill
- writing-fragmentsSkill
- writing-great-skillsSkill
- writing-shapeSkill
The file
Files
Complete publish.md for one finished item so it's ready to upload. Metadata
optimizer role: read the final script.txt and the charter, then write copy that
earns the click and the comment without over-promising what the video delivers.
Read first
- Final
script.txt— the actual content, hook, and payoff. project.md+context.md— niche, voice, the engagement mechanic, any title/tag conventions.context.mdoverrides on conflict.- The draft pinned/engagement comment already in
publish.md(from the script stage) — finalize it, don't start over.
Write into publish.md
- Title variants (2–3) — front-load the hook/curiosity; match the platform's length norm; no clickbait the video doesn't pay off.
- Description — a tight SEO-aware opener (first line does the work), then any standing channel boilerplate the charter specifies.
- Tags — drawn from the actual subject/mechanic, not generic filler.
- Chapters — only if the format is long enough to warrant them.
- Finalized engagement comment — the polarizing question / CTA, tuned against the final Trap/payoff.
Upload itself is manual and out of scope. When done, tell the orchestrator the item
is ready to be marked complete (e.g. stockpiled); the orchestrator owns
pipeline.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.