publish-skilllisted

# Publishing a skill to the private registry This is the meta-skill that publishes other skills. It is intentionally **limited in scope**: it assumes the project layout that this blueprint's [skill-package/](../../skill-package) example uses, and refuses to invent fields it doesn't have. ## When to invoke - User says "publish this skill" / "把这个 skill 发布出去" / "register this skill in our registry" / "send this to skills hub" - User has just finished editing a directory that contains `pyproject.toml` and `src/<pkg>/skill_files/SKILL.md` - The user's intent is to make a skill discoverable across the organization, not just to test it locally ## When NOT to invoke - The user is editing the skill content itself (use the regular edit flow; do not auto-publish drafts) - The user is consuming a skill (search / install / use) — that's a different flow, see the consumer scripts - There's no `pyproject.toml` in the current directory — this skill cannot publish raw markdown without a packaging step - The user is on a machine without AWS credentials — refuse to proceed and explain how to set them up ## How this skill works The work is delegated to a single Python script: `scripts/publish.py`. The script is parameterized ��� it reads defaults from `~/.skillpublish/config.toml` and accepts CLI flags to override. Always read [`resources/publish-skill-runbook.md`](resources/publish-skill-runbook.md) **before** running anything. The runbook covers: - The preflight checks t