Separation between consuming and producing skills

[lforst]

Love this project, but one point of feedback. I think it would be beneficial to have the skills that are exported in a different location than .agents/skills.

Reason, you may have a repo that collects skills and exports them for multiple other repos to use, though you probably don't want the skills to be used in the repo in which they're defined. Lmk if that makes sense or not.

In Sentry terminology, the develop repo could have some skills for all SDK repos to use to build SDKs, however you don't want skills for building SDKs to be used for when you're vibing on the develop repo.

[sentry-pierre]

Hi, I'm Pierre!

Merci for the feedback. The separation you're describing is already possible, though the docs don't call it out clearly.

What already works:

• Put skills you want to export in a top-level skills/ directory in the repo.
• dotagents scans skills/ when the repo is used as a source, so consumers can discover and install them.
• Local agents only read .agents/skills/ (or symlinks from there), so the exporting repo does not activate those skills locally.

This repo already uses that pattern: its own dotagents skill lives in skills/dotagents/ and is not declared in agents.toml, so it is discoverable by downstream repos but not consumed here.

A maintainer can take it from here—probably a docs note or init hint is enough.