← Back to Skills Marketplace
grey0758

GitHub Personal Repo Publisher

by grey0758 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
101
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install github-personal-repo-publisher
Description
Create a repository under your own GitHub account, wire a local project repo to it, and push committed history safely. 为你自己的 GitHub 账户创建仓库,把本地项目仓库接过去,并安全推送已提...
README (SKILL.md)

GitHub Personal Repo Publisher

Use this skill when a local Git project should be published to a new repository under your own GitHub account and the account access is managed through SSH plus a 1Password-stored PAT. 当本地 Git 项目需要发布到你自己 GitHub 账户下的新仓库,且账户访问通过 SSH 和 1Password 中保存的 PAT 管理时,使用这个 skill。

Read First | 先读这些

  • {baseDir}/README.md
  • {baseDir}/WORKFLOW.md
  • {baseDir}/FAQ.md
  • {baseDir}/CHANGELOG.md

Primary Rule | 核心原则

Treat Git history as the publish boundary: only committed local history should be described as pushed. 把 Git 提交历史当作发布边界:只有已提交的本地历史,才能算已经推送。

Workflow | 执行流程

  1. inspect the local repository state 检查本地仓库状态
  2. verify SSH auth to the personal GitHub account 验证到个人 GitHub 账户的 SSH 认证
  3. check whether the target repository already exists 检查目标仓库是否已存在
  4. create the GitHub repository through the API if missing 如果缺失,则通过 API 创建 GitHub 仓库
  5. add or update the local origin 添加或更新本地 origin
  6. push the current branch and set upstream 推送当前分支并建立 upstream
  7. verify remote wiring and pushed commit 校验远端绑定和已推送提交
  8. state clearly what remains local-only 明确说明哪些内容仍只存在于本地

Strong Heuristics | 强判断规则

  • if origin already points to the correct repo, do not recreate the repository
  • if SSH auth fails, do not continue to remote rewiring or push
  • if the GitHub repo does not exist and gh is unavailable, use the REST API with a 1Password-managed PAT
  • default new personal project repositories to private unless the user clearly wants public exposure
  • if the worktree is dirty, say explicitly that uncommitted files were not pushed
  • if origin exists but points elsewhere, update it intentionally rather than assuming it is disposable

中文解释:

  • 如果 origin 已经指向正确仓库,就不要重复建仓库。
  • SSH 认证失败时,不要继续改 remote 或 push。
  • GitHub 仓库不存在且 gh 不可用时,用 1Password 管理的 PAT 调 REST API。
  • 新的个人项目仓库默认建成 private,除非用户明确要求公开。
  • 工作区有脏改动时,要明确说明未提交文件并没有被推送。
  • origin 已存在但指向别处时,要有意识地更新,不要假设它可以随便覆盖。

Safe Commands | 安全命令

git -C /path/to/project status --short
git -C /path/to/project remote -v
git -C /path/to/project log --oneline -3
ssh -T git@github-grey0758
git ls-remote git@github-grey0758:grey0758/your-repo.git HEAD
TOKEN="$(op read 'op://OpenClaw/GitHub Fine-Grained PAT - Repo Admin - grey0758/credential')"
curl -fsSL -X POST -H 'Accept: application/vnd.github+json' -H "Authorization: Bearer $TOKEN" https://api.github.com/user/repos -d '{"name":"your-repo","private":true}'
git -C /path/to/project remote add origin git@github-grey0758:grey0758/your-repo.git
git -C /path/to/project push -u origin main

Response Format | 输出格式

Always return: 始终返回:

  1. current local repo status
  2. GitHub repo existence or creation status
  3. remote wiring status
  4. push status
  5. local-only work that still remains

Constraints | 约束

  • do not reveal PAT values or copy secret material into files
  • do not say a project is fully published when uncommitted changes still exist
  • do not assume gh is installed
  • keep the owner, SSH alias, and target repo name explicit
Usage Guidance
Before installing or using this skill: (1) Confirm you have git, ssh, curl, network access, and the 1Password CLI available on the agent environment — the manifest does not declare these but SKILL.md requires them. (2) Replace or remove the hardcoded defaults (owner 'grey0758', SSH host alias 'github-grey0758', and the 1Password item path) with values that match your account; do not use someone else's defaults. (3) Verify the 1Password item and PAT scope: the PAT should have only the minimal scopes needed (repo creation/administration as required) and you should never allow the skill to print or store the raw token. (4) Test the workflow on a disposable repo or with a dry run before running against important repositories. (5) If you want stronger guarantees, ask the author to update the package metadata to declare required binaries and to make credential/SSH-alias configurable rather than hardcoded. If you cannot verify these changes, treat the skill with caution.
Capability Analysis
Type: OpenClaw Skill Name: github-personal-repo-publisher Version: 1.0.0 The skill is a specialized automation tool designed to create GitHub repositories and push local project history using the 1Password CLI ('op') for credential management. While it contains hardcoded identifiers specific to a single user's environment (e.g., the 'grey0758' SSH alias and specific 1Password vault paths in SKILL.md and README.md), the logic is transparent, aligns with the stated purpose, and includes safety checks such as defaulting to private repositories and verifying SSH connectivity before execution.
Capability Assessment
Purpose & Capability
The skill's stated purpose (create a repo and push via SSH + a 1Password-stored PAT) is coherent with the runtime instructions, but the registry metadata declares no required binaries or credentials while SKILL.md explicitly assumes git, ssh, curl, network access, and the 1Password CLI. Also README/SKILL.md include concrete defaults (owner 'grey0758', SSH alias 'github-grey0758', a specific 1Password item path) which are specific to one account and inappropriate as global defaults.
Instruction Scope
SKILL.md instructs the agent to read local repo files, verify SSH (ssh -T), and read a PAT from 1Password (op read) then call the GitHub API via curl. Those actions are expected for this purpose, but the instructions reference a specific 1Password path and SSH host alias (which could fail or be misapplied) and they instruct reading a secret from 1Password — ensure the skill will only read a PAT you intend to use and will not copy or leak it (the SKILL.md does state 'do not reveal PAT values').
Install Mechanism
Instruction-only skill with no install spec or code files — low file-write/install risk. All runtime behavior comes from the SKILL.md commands the agent will run.
Credentials
The skill needs a GitHub PAT to call the REST API when 'gh' is unavailable, which is proportionate. However the manifest lists no required credentials/primaryEnv while SKILL.md uses an explicit 1Password item path ('op://OpenClaw/GitHub Fine-Grained PAT - Repo Admin - grey0758/credential'). The hardcoded item and owner name point to a specific account and should be removed or made configurable. Also confirm the PAT scope is minimal for the task (repo creation) and not broader than necessary.
Persistence & Privilege
The skill does not request 'always: true', does not modify other skills, and 'agents/openai.yaml' sets allow_implicit_invocation:false. It has no persistent installation actions in its manifest. Normal autonomous invocation concerns are not compounded here.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install github-personal-repo-publisher
  3. After installation, invoke the skill by name or use /github-personal-repo-publisher
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of github-personal-repo-publisher. - Publishes a local Git project to a new personal GitHub repository using SSH and a 1Password-stored PAT. - Ensures only committed history is pushed; uncommitted changes are clearly reported as local-only. - Automatically creates the repo via API if needed; defaults to private unless the user indicates otherwise. - Checks and updates the remote origin as needed without overwriting unintentionally. - Provides clear output on local status, remote setup, push success, and remaining local-only work.
Metadata
Slug github-personal-repo-publisher
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is GitHub Personal Repo Publisher?

Create a repository under your own GitHub account, wire a local project repo to it, and push committed history safely. 为你自己的 GitHub 账户创建仓库,把本地项目仓库接过去,并安全推送已提... It is an AI Agent Skill for Claude Code / OpenClaw, with 101 downloads so far.

How do I install GitHub Personal Repo Publisher?

Run "/install github-personal-repo-publisher" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is GitHub Personal Repo Publisher free?

Yes, GitHub Personal Repo Publisher is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does GitHub Personal Repo Publisher support?

GitHub Personal Repo Publisher is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created GitHub Personal Repo Publisher?

It is built and maintained by grey0758 (@grey0758); the current version is v1.0.0.

💬 Comments