doc-writing
Skill0 starsChanged 3 months agoNo licenceView on GitHub
Business document writing, review, and rewriting methodology for Chinese/English workplace docs. Use when Codex needs to draft, improve, critique, summarize, or structure business documents, recurring updates, meeting materials, decision memos, story lines, strategy narratives, problem-analysis docs, or alignment/consensus documents; especially when the user asks for 写文档, 文档写作, 故事线, 业务汇报, 例会材料, 决策材料, 问题分析材料, 文档润色, or 文档 review.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- cormacc/dotagentstheir own version, first seen Nov 1, 2026
- ly0o0o/codex-engineering-skillstheir own version, first seen Aug 7, 2026
- addxai/enterprise-harness-engineeringtheir own version, first seen Apr 17, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- addxai/enterprise-harness-engineering★ 44same name
- ly0o0o/codex-engineering-skills★ 2same name
- cormacc/dotagents★ 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 repository2 other files it gives its agents.
- de-ai-writingSkill
- douyin-product-link-parserSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.