publish-kit
Skill1 starsChanged 2 days agoMITView on GitHub
Manual publish kit for platforms without permitted automation — files, text, links and one specific action for the human. Use at stage 7.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- EternalNight996/publish-kittheir own version, first seen Aug 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- EternalNight996/publish-kit★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-visualizationSkill
- approval-packSkill
- content-atomizationSkill
- dispatchSkill
- fact-checkSkill
- ffmpeg-skillSkill
- hook-storylineSkill
- idea-diceSkill
- jurySkill
- memory-compactionSkill
- perf-loopSkill
- seamless-insertSkill
- setupSkill
- shoot-briefSkill
- sound-designSkill
- source-skeletonSkill
- style-memorySkill
- treg-gatewaySkill
- trend-scoutSkill
- utmSkill
- video-codeSkill
- weekly-cycleSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
When to publish (date and time from the plan).
- Distinctive: line 20
After the human publishes, they send the link, and the publisher records it in the log.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Manual publish kit
Folder weeks/<W>/07-kits/<channel>/ + an entry in 07-publications.md with status kit_ready.
Contents
- Media with clear names:
01_W44-R03_cover.png,02_W44-R03.mp4. post.txt— text ready to copy (with line breaks suited to the platform).- A link with UTM, hashtags or a board, if needed.
- When to publish (date and time from the plan).
- One action for the human: "Open the VK group → New post → paste post.txt → attach 01, 02 → Publish".
- Checklist: AI label in place · link checked · cover chosen.
Delivery
A short message listing the week's kits with a link to the folder (Drive or repository). After the human publishes, they send the link, and the publisher records it in the log.
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.

