Agent测试

Name: Agent测试
Author: diegosouzapw

其他社区

作者仓库星标 39
作者更新于实时读取
作者仓库 awesome-omni-skill

流狐档案事实层信息：领域、Agent、信任分、运行环境、权限与网络

领域: 通用
兼容 Agent: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
信任分: 88 / 100 · 社区维护
作者 / 版本 / 许可: @diegosouzapw · 未声明 license
Token 消耗评级: 低消耗
接入复杂程度: 即装即用
是否需要外部 API Key: 不需要
兼容的系统: macOS · Linux · Windows
底层运行要求: Node.js
文件与系统权限: 只读
允许写入 / 修改
读取环境变量
网络行为: 允许外网请求
安装命令数: 26 条

档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。

需要注意： 未限定 allowed-tools，默认拥有全部工具权限。

输出预览 gh-skill.preview

---
name: gh-skill
description: Manage GitHub Projects (V2), Issues, and Boards. View project boards, create/move issues, commen…
category: 通用
runtime: Node.js
---

# gh-skill 输出预览

## PART A: 任务判断
- 适用问题：通用任务拆解、检查和交付。
- 输入要求：目标材料、限制条件、期望输出和验收方式。
- 证据边界：围绕“Usage / 0. 🔍 Discovery / 1. 📋 Board Items”读取原文规则，不把推断写成作者承诺。

## PART B: 执行结果
- **01** 任务判断：确认你的需求是否属于通用任务拆解、检查和交付，并标出输入、限制和预期结果。
- **02** 执行计划：优先按“Usage / 0. 🔍 Discovery / 1. 📋 Board Items”拆成步骤，说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果：给出可复制的命令、文件改动、检查清单或内容草稿，并说明如何继续迭代。
- **04** 风险边界：结合 读取文件、写入/修改文件、读取环境变量、会按任务需要访问外部网络、通常不需要额外 API Key 给出执行前确认项。

## Running Rules
- 读取文件、写入/修改文件、读取环境变量；会按任务需要访问外部网络；通常不需要额外 API Key。
- 先小样例验证，再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。

SKILL.md SKILL.md

---
name: gh-skill
description: Manage GitHub Projects (V2), Issues, and Boards. View project boards, create/move issues, commen…
category: 通用
source: diegosouzapw/awesome-omni-skill
---

# gh-skill

## 什么时候使用
- 把通用方向的常用动作沉淀成 Agent 可调用的技能 适合处理通用任务拆解、检查、交付和复盘，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤；通常不需要额外…
- 面向通用任务拆解、检查和交付，优先处理能明确输入、步骤和验收标准的工作。

## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。

## 执行规则
- 围绕「Usage / 0. 🔍 Discovery / 1. 📋 Board Items」组织步骤，不把推断写成作者事实。
- 读取文件、写入/修改文件、读取环境变量；会按任务需要访问外部网络；通常不需要额外 API Key。
- 先跑小样例，确认结果可检查后再扩大任务范围。

## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown，不编造命令、平台或依赖。

证据边界与执行链路

作者原文负责流程事实；仓库文件负责来源和命令；流狐只补充适用场景、限制和质量判断。

skill "gh-skill" {
  输入层     -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
  上下文层   -> Usage / 0. 🔍 Discovery / 1. 📋 Board Items
  规则层     -> SKILL.md 触发条件 / 执行顺序 / 输出格式
  运行层     -> Node.js | 读取文件、写入/修改文件、读取环境变量 | 会按任务需要访问外部网络
  安全层     -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
  输出层     -> 可复制结果 + 检查清单 + 下一步迭代
}

解读按原文结构重写，命令、链接、术语均保留；右侧可核对作者原始 SKILL.md

先判断是否适合

核心用途：把通用方向的常用动作沉淀成 Agent 可调用的技能适合处理通用任务拆解、检查、交付和复盘，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。把任务拆成可执行、可检查、可继续迭代的步骤；通常不需要额外 API Key，适…
适用任务：更适合通用任务拆解、检查、交付和复盘，尤其是输入、步骤、验收口径可以反复复用的场景。
不宜硬套：如果任务只有一次性问答、来源材料很少，或需要作者没有说明的命令和外部服务，应先降级为普通对话。

作者设计意图

触发依据：使用时机、上下文收集、输出格式和失败处理共同决定它是否适合当前任务。
来源边界：作者原文负责事实，仓库文件负责命令和文件证据；Fluxly 只补充用途、限制和使用判断。

作者的方法与取舍

执行主线：任务围绕「Usage / 0. 🔍 Discovery / 1. 📋 Board Items」组织，把触发条件、必要上下文、执行规则和交付标准连成一条可复核的链路。
设计重点：重点不在重复教程，而在解释作者为什么规定这些步骤、哪些条件不可省略，以及结果偏离时应回到哪一层检查。
使用判断：先确认任务与原文边界一致，再决定是否启用；来源没有说明的命令、平台和依赖保持未知，不由 Fluxly 补写。

边界和复核

依赖条件：通常不需要额外 API Key，适合先用小任务验证触发是否稳定。
权限提醒：会涉及 read / write / env-read 权限，执行前要说明可读写范围、命令边界和回退方式。
质量标准：结果应包含明确产物、必要证据和下一步动作；如果只是泛泛解释，需要补充输入和验收条件后重跑。

GitHub Project Skill

This skill provides a comprehensive CLI wrapper for the GitHub GraphQL API, enabling efficient management of GitHub Projects V2 and Issues directly from the terminal.

Usage

The main entry point is dist/cli.js (relative to the project root). You can verify it works with:

node dist/cli.js --help

Global Options:

-j, --json: Output results in JSON format. ALWAYS use this flag when parsing output programmatically.

Note: In --json mode, the CLI prints only JSON to stdout.

0. 🔍 Discovery

Goal: Explore owner resources and project structure.

List Projects

Command: node dist/cli.js project-list <owner>

Usage:

node dist/cli.js project-list "my-org" --json

List Repositories

Command: node dist/cli.js repo-list <owner>

Usage:

node dist/cli.js repo-list "my-org" --json

Get Project Board Details

Command: node dist/cli.js board <owner> <project>
Arguments: <project> can be the Project Number or the Project Title (case-insensitive).
Options: --status-field <name> (Default: "Status")
Usage:
```
node dist/cli.js board "my-org" "My Project Name" --json
```
Returns project ID, global node ID, and column definitions (including Option IDs needed for moving items).

1. 📋 Board Items

Goal: List all items (Issues/PRs/Drafts) on the board with their current status.

Command: node dist/cli.js items <owner> <project>
Usage:
```
node dist/cli.js items "my-org" 1 --json
```
Returns list of items with their Item IDs (for moving/archiving) and Content Node IDs.

List Issues Linked to a Project (Project-Centric)

Goal: One consistent way for AI agents: start from Project, get issues + both IDs (Issue node ID and Project item ID).

Command: node dist/cli.js project-issues <owner> <project>
Options:
- --status-field <name> (Default: "Status")
- --state <open|closed|all> (Default: open)
- --limit <n> (Default: 50)
- --repo <owner/repo> (Optional: narrow search to a single repo)

Usage:

node dist/cli.js project-issues "my-org" "Trionix Lab" --state open --limit 50 --json
# optionally scope to one repo for speed/limits
node dist/cli.js project-issues "my-org" 1 --repo "my-org/my-repo" --json

Implementation note: uses GitHub GraphQL search + Issue.projectItems to avoid cases where ProjectV2.items listing is incomplete for some integrations.

Show Project Item by Item ID

Goal: Inspect a specific project item when listing is incomplete.

Command: node dist/cli.js item-show <itemId>
Options: --status-field <name> (Default: "Status")
Usage:
```
node dist/cli.js item-show "PVTI_..." --json
```
Useful workaround if items does not show Issues/PRs due to access restrictions.

2. 🆕 Issue & Draft Management

List Issues

Goal: List issues in a repository (with pagination).

Command: node dist/cli.js issue-list <owner/repo>
Options: --state <open|closed|all> (Default: open), --limit <n> (Default: 50)

Usage:

node dist/cli.js issue-list "my-org/my-repo" --state open --limit 50 --json

Create Issue

Command: node dist/cli.js issue-create <owner/repo> "<title>"
Options: --body "<body>"

Usage:

node dist/cli.js issue-create "my-org/my-repo" "Fix bug" --body "Details" --json

Create Draft

Command: node dist/cli.js draft-create <owner> <project> "<title>"
Options: --body "<body>"

Usage:

node dist/cli.js draft-create "my-org" "Product Roadmap" "Task title" --body "Details" --json

Show Issue

Command: node dist/cli.js issue-show <owner/repo> <issue_number>

Usage:

node dist/cli.js issue-show "my-org/my-repo" 123 --json

Get Issue by Node ID (Agent-Friendly)

Goal: Fetch issue content when you already have issue.id (node ID).

Command: node dist/cli.js issue-get <issueNodeId>

Usage:

node dist/cli.js issue-get "I_kwDO..." --json

Update Issue

Command: node dist/cli.js issue-update <issueNodeId>
Options: --title <text>, --body <text>

Usage:

node dist/cli.js issue-update "I_kwDO..." --title "New Title" --json

Close Issue

Command: node dist/cli.js issue-close <issueNodeId>

Usage:

node dist/cli.js issue-close "I_kwDO..." --json

Delete Issue (Behavior)

Note: GitHub APIs do not support hard-deleting Issues. This command closes the issue.

Command: node dist/cli.js issue-delete <issueNodeId>

Usage:

node dist/cli.js issue-delete "I_kwDO..." --json

3. 💬 Collaboration

Goal: Add comments to issues.

Command: node dist/cli.js issue-comment <issueNodeId> "Comment text"

Usage:

node dist/cli.js issue-comment "I_kwDO..." "Done" --json

List Comments

Goal: Get existing comments for an issue (for agents that need context).

Command: node dist/cli.js issue-comments <issueNodeId>
Options: --limit <n> (Default: 50)

Usage:

node dist/cli.js issue-comments "I_kwDO..." --limit 50 --json

4. 🚚 Kanban Operations

Add Issue to Project

Command: node dist/cli.js issue-add-to-project <owner> <project> <issueNodeId>

Usage:

node dist/cli.js issue-add-to-project "my-org" "Project Name" "I_kwDO..." --json

Move Item

Command: node dist/cli.js issue-move <itemId> <projectId> <statusFieldId> <optionId>

Usage:

# IDs are obtained from 'board' and 'items' commands
node dist/cli.js issue-move "PVTI_..." "PVT_..." "PVTSSF_..." "f75ad846" --json

Move Item (Agent-Friendly)

Goal: Move an item without dealing with option IDs.

Command: node dist/cli.js item-move <owner> <project> <itemId> --status "<Status Name>"
Options: --status-field <name> (Default: "Status")

Usage:

node dist/cli.js item-move "my-org" "Product Roadmap" "PVTI_..." --status "In progress" --json

Archive Item

Command: node dist/cli.js item-archive <owner> <project> <itemId>
Options: --unarchive

Usage:

node dist/cli.js item-archive "my-org" 1 "PVTI_..." --json

Delete Item from Project

Command: node dist/cli.js item-delete <owner> <project> <itemId>

Usage:

node dist/cli.js item-delete "my-org" "Project Alpha" "PVTI_..." --json

Best Practices

Use JSON: Always append --json for robust parsing.
Get IDs First: Most mutation commands require Node IDs (strings starting with like PVT_, I_, PVTI_). Use project-list, board and items commands to retrieve these IDs.
Owner Logic: Owner can be either an Organization or a User. The tool automatically tries both.

Troubleshooting

"Project not found": Check if owner and project_number are correct.
"Resource not accessible by integration": Check your .env credentials and GitHub App permissions.

Notes on Project Items Visibility

A Project V2 may contain items that the current token cannot fully view. GitHub can return items as REDACTED when the integration lacks permissions to view the underlying Issue/PR.
If issue-add-to-project succeeds but items does not show the Issue/PR item, use item-show <itemId> (the itemId returned by issue-add-to-project) to inspect it directly.

Recommended Single Workflow (for AI agents)

List work from the Project (project-centric): project-issues <owner> <project> --json. Note: <project> can be a name or a number.
Read issue content by node ID: issue-get <issueNodeId> --json.
Update / comment:
- issue-update <issueNodeId> --title ... --body ... --json
- issue-comments <issueNodeId> --json (get context)
- issue-comment <issueNodeId> "..." --json (add)
“Delete” in practice:
- GitHub APIs do not support hard-deleting Issues.
- Use issue-delete <issueNodeId> (closes the issue) and/or item-delete <owner> <project> <projectItemId> (removes it from the Project).
Move on the board using readable status:
- item-move <owner> <project> <projectItemId> --status "To Do" --json
Optional lifecycle:
- item-archive <owner> <project> <projectItemId> --json

安装命令

一键复制安装选择包管理器,点击右侧复制,粘贴到终端回车即可

npx skills add diegosouzapw/awesome-omni-skill/skills/tools/gh-skill -y

查看通用安装教程

查看 Skill 原文

兼容工具

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

安全审计

88 / 100

社区

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

元信息

来源: github
diegosouzapw/awesome-omni-skill
English

@diegosouzapw 的其他技能

分类与标签

分类其他

先判断是否适合

作者设计意图

作者的方法与取舍

边界和复核

GitHub Project Skill

Usage

0. 🔍 Discovery

List Projects

List Repositories

Get Project Board Details

1. 📋 Board Items

List Issues Linked to a Project (Project-Centric)

Show Project Item by Item ID

2. 🆕 Issue & Draft Management

List Issues

Create Issue

Create Draft

Show Issue

Get Issue by Node ID (Agent-Friendly)

Update Issue

Close Issue

Delete Issue (Behavior)

3. 💬 Collaboration

List Comments

4. 🚚 Kanban Operations

Add Issue to Project

Move Item

Move Item (Agent-Friendly)

Archive Item

Delete Item from Project

Best Practices

Troubleshooting

Notes on Project Items Visibility

Recommended Single Workflow (for AI agents)

讨论