agentleFS
Sign inStart free
leishifu666leishifu666/skills/doc-coauthoring/SKILL.md

doc-coauthoring

Skill1 starsChanged 23 days agoNo licenceView on GitHub

协作撰写或迭代技术文档、提案和决策说明；需要梳理结构及验证读者理解时使用。

We split this skill into the rules it gives an agent

60 rules. 54 are common, 0 are distinctive, and 6 are very specific to this project.

  • 54

    Common

    Most of the 165 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 6

    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 measured: kept by at least 6 in 10 of the 165 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

  • Other versions174 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 157

    1. anthropics/skills★ 186k97% same
    2. Galaxy-Dawn/claude-scholar★ 5.9k94% same
    3. moonrepo/moon★ 4.2k97% same
    4. ChenglinPoly/infiAgent★ 1.2k97% same
    5. polyuiislab/infiAgent★ 1.2k97% same
    6. getsentry/skills★ 1.1k97% same
    7. Ohh-889/skyroc-admin★ 79592% same
    8. JetBrains/skills★ 38697% same
    9. xuzeyu91/WebCode★ 27897% same
    10. cohen-liel/hivemind★ 10897% same

    147 more not listed

    Wrote their own version · 17

    1. zephyrwang6/myskill★ 339same name
    2. linxuan-sys/opencode-skills-chinese★ 200same name
    3. Immortalqx/my_codex_skills★ 54same name
    4. MarcelLeon/skills-zh★ 42same name
    5. xopcai/xopc★ 40same name
    6. SpaceZephyr/allSkills★ 14same name
    7. skyfox675/agents-skills★ 11same name
    8. mia-cx/skills★ 5same name
    9. cabernect/caberos★ 2same name
    10. CODE-SAURABH/OpenSkills★ 2same name

    7 more not listed

    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.

  • Used alongsideProjects with it also use context7-efficient, fetch-library-docs and 9 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • hfzarslanSkill

      context7-efficient

      Token-efficient library documentation fetcher using Context7 MCP with 86.8% token savings through intelligent shell pipeline filtering. Fetches code examples, API references, and best practices for JavaScript, Python, Go, Rust, and other libraries. Use when users ask about library documentation, need code examples, want API usage patterns, are learning a new framework, need syntax reference, or troubleshooting with library-specific information. Triggers include questions like "Show me React hooks", "How do I use Prisma", "What's the Next.js routing syntax", or any request for library/framework documentation.

      Also in 5 projects that use this

    • Rehan-Ul-HaqSkill

      fetch-library-docs

      Fetches official documentation for external libraries and frameworks (React, Next.js, Prisma, FastAPI, Express, Tailwind, MongoDB, etc.) with 60-90% token savings via content-type filtering. Use this skill when implementing features using library APIs, debugging library-specific errors, troubleshooting configuration issues, installing or setting up frameworks, integrating third-party packages, upgrading between library versions, or looking up correct API patterns and best practices. Triggers automatically during coding work - fetch docs before writing library code to get correct patterns, not after guessing wrong.

      Also in 4 projects that use this

    • AbdullahMalik17Skill

      configuring-dapr-pubsub

      Configures Dapr pub/sub components for event-driven microservices with Kafka or Redis. Use when wiring agent-to-agent communication, setting up event subscriptions, or integrating Dapr sidecars. Covers component configuration, subscription patterns, publishing events, and Kubernetes deployment. NOT when using direct Kafka clients or non-Dapr messaging patterns.

      Also in 3 projects that use this

    • AbdullahMalik17Skill

      deploying-cloud-k8s

      Deploys applications to cloud Kubernetes (AKS/GKE/DOKS) with CI/CD pipelines. Use when deploying to production, setting up GitHub Actions, troubleshooting deployments. Covers build-time vs runtime vars, architecture matching, and battle-tested debugging.

      Also in 3 projects that use this

    • AnthropicSkill

      academy-guide

      Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

      Also in 4 projects that use this

    • AnthropicSkill

      discernment-nudge

      After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

      Also in 5 projects that use this

    • +5 more from AbdullahMalik17
  • In this repository270 other files it gives its agents.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free