Hi Aleksandr, Thanks, this is a useful point. By user-facing skills I do not mean a generic agent that can already search docs or source code. The idea is to package a narrow workflow with project context and checks.
For example, the docs/release-note skill I mentioned would look at a concrete change, find the affected docs and release-note conventions, and help prepare the update. It should be easy to see its inputs, expected output, and limitations. I will publish that first so we have something real to discuss. I also agree that we should not publish a "make a PR" skill without project-level guardrails. The contributor still owns the patch, tests, and design; the agent is only a tool. A short AI usage policy and an AGENTS.md with the rules you listed sound like a good starting point. I can prepare a small initial proposal around that together with the first skill. Then we can review the rules and decide what belongs in the main repo. Best, Dmitriy
