content-package-manager
Skill1 starsChanged 5 months agoMITView on GitHub
Use when preparing platform-neutral content packages, 内容包, 多渠道发布准备, 内容预审, channel package planning, or separating article content from publishing channels.
- Reads credentials
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- csdn-publisherSkill
- juejin-publisherSkill
- xiaohongshu-publisherSkill
- zhihu-publisherSkill
- ddd-java-developerSkill
- doubao-speechSkill
- doubao-videoSkill
- formal-resume-builderSkill
- code-qualitySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Run public-content checks for sensitive information, exaggerated claims, copyright risk, external links, and platform suitability.
- Very specific: line 23
Use content_prepare_package when the user asks to prepare reusable content or publish to multiple platforms.
- Very specific: line 27
Do not read Cookie, Token, password, .env, browser profile, or account files.
- Distinctive: line 28
Do not open publishing platforms.
- Distinctive: line 29
Do not click publish, update, delete, withdraw, comment, or send messages.
- Distinctive: line 30
Treat private work material, customer information, internal addresses, unpublished metrics, and credentials as non-public.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
content-package-manager
Goal
Manage platform-neutral content packages before any channel-specific publishing work.
Responsibilities
- Prepare
content.md,metadata.json,review-checklist.md,channels/, and optionalassets/. - Normalize title, topic, summary, tags, target channels, and source Markdown.
- Run public-content checks for sensitive information, exaggerated claims, copyright risk, external links, and platform suitability.
- Route channel-specific work to channel Skills such as
zhihu-publisher,xiaohongshu-publisher, andjuejin-publisher.
Default Tool
Use content_prepare_package when the user asks to prepare reusable content or publish to multiple platforms.
Safety Rules
- Do not read Cookie, Token, password,
.env, browser profile, or account files. - Do not open publishing platforms.
- Do not click publish, update, delete, withdraw, comment, or send messages.
- Treat private work material, customer information, internal addresses, unpublished metrics, and credentials as non-public.
Output Format
Return:
建议:...
事实:...
已执行:...
内容包:...
目标渠道:...
下一步:...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.

