github-skill-publisherlisted

# GitHub-skill-publisher Use this skill to turn a local agent skill into a polished single-skill GitHub repository and to maintain it over time. This skill is for skill publishing workflows, not general Git tutorials. ## Core rule The user's preferred structure is: ```text one skill = one GitHub repository ``` The repository root is the skill root. Do not create a `skills/<name>/` wrapper unless the user explicitly asks for a collection repository. ## Publish authorization rule This rule applies to GitHub-skill-publisher itself and to every other skill repository it publishes or updates. Local edits and GitHub publication are separate actions. Use two authorization modes: 1. Local-only by default. - If the user says "修改", "更新", "调整", "写进去", "完善", or similar edit-only wording, make local changes only. - After local changes, report what changed and ask before any commit, push, repository creation, sync, publish, or GitHub metadata update. 2. Explicit edit-plus-publish authorization. - If the user says "修改并发布", "改完发布", "更新并同步到 GitHub", "修改后推送", "改完直接发布", or another unambiguous edit-plus-publish instruction, treat that as permission to publish after checks. - In this mode, do not ask for a second confirmation after successful checks. - Still stop and ask before publishing if checks fail, sensitive data is found, cleanup requires deletion/redaction/moving user files, compatibility is partial or unsupported, the remote/branch/visibility is ambiguous, or the