360 Secure SkillHub
360 安全技能中心

AtomGit

面向 AtomGit 平台的 MCP 操作技能：在已由外部配置好 AtomGit MCP 服务器的运行时中，按需读取各 references 分文件，完成仓库、分支、提交、拉取请求、Issue、标签、里程碑、发布、组织、企业、看板、Actions 工作流、讨论、Webhook、搜索、成员权限与 AIHub 的查询和修改；强调先读后写、变更前确认标识符。

kylezhang
kylezhang
热度 84.20
最近更新 2026-10-12 21:32:54
分类：开发依赖：MCP 服务应用场景：API 集成 / DevOps / 代码审查 / 任务管理 ...

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add atomgit-skills
Metadata
name
atomgit
description
Use this skill when the user explicitly mentions AtomGit or atomgit.com, or needs to inspect or change AtomGit repositories, pull requests, issues, branches, releases, tags, permissions, organizations, enterprises, kanban boards, CI workflows (Actions), discussions, webhooks, or AIHub features through the AtomGit MCP server.
homepage
https://atomgit.com/zkxw2008/AtomGit-Skills
metadata
{"openclaw":{"homepage":"https://atomgit.com/zkxw2008/AtomGit-Skills","requires":{"env":["ATOMGIT_TOKEN"]},"primaryEnv":"ATOMGIT_TOKEN"}}

AtomGit

Use this skill only for AtomGit work. If the user only says "repo", "PR", "issue", "branch", or "tag" without saying AtomGit, do not assume this skill applies; confirm the platform first.

Start Here

  1. Confirm the request is about AtomGit.
  2. Inspect the runtime tool list before planning any repository action.
  3. If AtomGit tools are not exposed yet, stop the workflow and follow references/setup-and-safety.md to connect an AtomGit MCP server manually using the official server docs. Do not install packages or request secrets automatically inside the task.
  4. Match the exposed AtomGit MCP tool names exactly.
  5. Prefer read operations before write operations.
  6. Gather the identifiers you need before mutating anything:
    • owner and repo
    • number for issues and pull requests
    • branch, tag, path, or sha when the workflow needs them
  7. Confirm destructive or org-wide changes before executing them.

AtomGit MCP must be installed and configured outside this skill before the first AtomGit task. Do not wait until after a business request fails if the tool list already shows the server is missing, and do not ask users to paste tokens into chat.

Tool Naming

This skill uses canonical AtomGit MCP method names such as atomgit_get_repository.

Some runtimes add extra namespace wrappers around MCP tools. Always use the exact tool name exposed by the current runtime instead of assuming a prefix format from an example.

Common Identifiers

Identifier Typical meaning Notes
owner Repository owner, username, or organization Needed for most repository-scoped calls
repo Repository name Needed with owner for most repository calls
number Issue or pull request number Replaces older examples that used issue_number or pull_number
path Repository file path Use with file-content and file-update calls
sha Commit or blob SHA File updates usually need the current file SHA first
page, perPage Pagination controls List endpoints often expose both

Read References Only As Needed