Next AI Draw.io
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
The all-in-one AI agent. Build mobile apps, frontend, backend, manages files, deep research, schedule tasks and events. Self-improving, self-healing, fully autonomous. TUI, CLI and Daemon. Connect to your favorite channels. Zero Telemetry.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/opencrabs-opencrabs)在同一工作中把 AI 连到服务的 MCP
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.
同类工作,排序与 Skill 列表相同
| 本项 opencrabs | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| 作者 | opencrabs | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skill 数 | – | 1 | 1 | 1 | 1 |
| GitHub 星标 | 1,031 | 111,852 | 67,796 | 32,458 | 29,958 |
| 最近代码更新 | 2026年11月17日 | 2026年11月17日 | 2026年11月13日 | 2026年6月24日 | 2026年10月30日 |
| 许可证 | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
opencrabs 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
CodexGitHub CopilotOpenCode
依据开发者 README 和 repo 中的文件夹
GitHub account opencrabs (organization) is only 8 months old: take extra care
★ 1,031 stars · code last changed 2026年11月17日
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit b4e1a66 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Uploading to claude.ai would fail: the description is over 200 characters (261). Use "Let the AI install it" instead
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /github,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/opencrabs/opencrabs.git /tmp/popnx-skill-opencrabs-opencrabs-b4e1a66 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-opencrabs-opencrabs-b4e1a66/src/docs/reference/templates/skills/github' ~/.claude/skills/githubChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 github 文件夹放到 ~/.agents/skills/github
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/opencrabs/opencrabs.git /tmp/popnx-skill-opencrabs-opencrabs-b4e1a66 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-opencrabs-opencrabs-b4e1a66/src/docs/reference/templates/skills/github' ~/.agents/skills/githubChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/opencrabs/opencrabs.git /tmp/popnx-skill-opencrabs-opencrabs-b4e1a66 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-opencrabs-opencrabs-b4e1a66/src/docs/reference/templates/skills/github' ~/.agents/skills/github复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 github
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/opencrabs/opencrabs.git /tmp/popnx-skill-opencrabs-opencrabs-b4e1a66 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-opencrabs-opencrabs-b4e1a66/src/docs/reference/templates/skills/github' ~/.cursor/skills/github适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月18日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
5,826 个字符 · 在 GitHub 打开完整文件
---
name: github
description: Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
---
# GitHub Skill
Full GitHub operations via the `gh` CLI. Always check auth first, use templates for consistency, and respect rate limits.
## Step 0: Auth Detection (ALWAYS FIRST)
Before ANY GitHub operation, detect the auth method:
```bash
gh auth status 2>&1
```
**If authenticated:** Proceed. Note the logged-in username for the session.
**If not authenticated:** Check for `GITHUB_TOKEN` env var:
```bash
echo "${GITHUB_TOKEN:+token_set}"
```
**If no token either:** Tell the user:
> GitHub CLI is not authenticated. Run `gh auth login` to authenticate, or set `GITHUB_TOKEN` environment variable with a personal access token.
Do NOT proceed without auth. Do NOT fall back to `curl` or `http_request`.
## Step 1: Rate Limit Check (before bulk operations)
Before operations that issue 5+ API calls (batch triage, bulk label, multi-issue create), check rate limits:
```bash
gh api rate_limit --jq '.resources.core.remaining, .resources.core.limit, .resources.search.remaining, .resources.search.limit'
```
If core remaining < 100 or search remaining < 10, warn the user and ask whether to proceed.
## Issue Operations
### Create Issue
```bash
gh issue create --repo OWNER/REPO --title "TITLE" --body "BODY" --label "LABEL" --assignee "USER"
```
Templates (use unless user provides their own):
**Bug report:**
```markdown
## Description
[What happened]
## Steps to Reproduce
1. [Step 1]
2. [Step 2]
## Expected Behavior
[What should happen]
## Actual Behavior
[What actually happened]
## Environment
- OS: [e.g., macOS 14.3]
- Version: [e.g., v0.3.70]
```
**Feature request:**
```markdown
## Problem
[What problem does this solve?]
## Proposed Solution
[How should it work?]
## Alternatives Considered
[What else was considered?]
## Additional Context
[Screenshots, logs, references]
```
### List Issues
```bash
gh issue list --repo OWNER/REPO --state open --limit 20
gh issue list --repo OWNER/REPO --label "bug" --state open
gh issue list --repo OWNER/REPO --assignee "@me"
```
### View Issue
```bash
gh issue view NUMBER --repo OWNER/REPO
gh issue view NUMBER --repo OWNER/REPO --comments
```
### Comment on Issue
```bash
gh issue comment NUMBER --repo OWNER/REPO --body "COMMENT"
```
### Close Issue
```bash
gh issue close NUMBER --repo OWNER/REPO --reason completed
gh issue close NUMBER --repo OWNER/REPO --comment "Closing because REASON"
```
### Label Issue
```bash
gh issue edit NUMBER --repo OWNER/REPO --add-label "bug,priority:high"
gh issue edit NUMBER --repo OWNER/REPO --remove-label "wontfix"
```
### Assign Issue
```bash
gh issue edit NUMBER --repo OWNER/REPO --add-assignee "username"
gh issue edit NUMBER --repo OWNER/REPO --remove-assignee "username"
```
## Pull Request Operations
### Create PR
```bash
gh pr create --repo OWNER/REPO --title "TITLE" --body "BODY" --base main --head feature-branch
```
PR template:
```markdown
## What
[One-line summary]
## Why
[Why this change is needed]
## How
[What changed and how it works]
## Testing
- [ ] `cargo fmt --all -- --check`
- [ ] `cargo clippy --all-features -- -D warnings`
- [ ] `cargo test --all-features`
## Related Issues
Closes #NUMBER
```
### List PRs
```bash
gh pr list --repo OWNER/REPO --state open
gh pr list --repo OWNER/REPO --author "@me" --state open
```
### View PR
```bash
gh pr view NUMBER --repo OWNER/REPO
gh pr view NUMBER --repo OWNER/REPO --comments
gh pr diff NUMBER --repo OWNER/REPO
```
### Review PR
```bash
gh pr review NUMBER --repo OWNER/REPO --approve
gh pr review NUMBER --repo OWNER/REPO --request-changes --body "Please fix X"
gh pr review NUMBER --repo OWNER/REPO --comment --body "Looks good, one nit"
```
### Merge PR
```bash
gh pr merge NUMBER --repo OWNER/REPO --squash
gh pr merge NUMBER --repo OWNER/REPO --merge
gh pr merge NUMBER --repo OWNER/REPO --rebase
```
### Branch Operations
```bash
gh pr checkout NUMBER --repo OWNER/REPO
git push origin --delete feature-branch # after merge
```
## Repository Operations
### View Repo
```bash
gh repo view OWNER/REPO
gh repo view OWNER/REPO --json name,description,defaultBranchRef,stargazerCount
```
### Clone
```bash
gh repo clone OWNER/REPO
gh repo clone OWNER/REPO /path/to/dir
```
### Fork
```bash
gh repo fork OWNER/REPO
gh repo fork OWNER/REPO --clone=false
```
### Releases
```bash
gh release list --repo OWNER/REPO
gh release view TAG --repo OWNER/REPO
gh release create TAG --repo OWNER/REPO --title "TITLE" --notes "NOTES"
```
## Workflow / Actions
```bash
gh workflow list --repo OWNER/REPO
gh run list --repo OWNER/REPO --limit 5
gh run view RUN_ID --repo OWNER/REPO
gh run watch RUN_ID --repo OWNER/REPO
```
## Code Search
```bash
gh search code "QUERY" --repo OWNER/REPO
gh search issues "QUERY" --repo OWNER/REPO
gh search prs "QUERY" --repo OWNER/REPO
```
## Rules
1. **ALWAYS use `gh` CLI, NEVER `http_request` to api.github.com** — http_request lacks proper headers and gets 403
2. **ALWAYS check auth before first operation** — Step 0 above
3. **ALWAYS use `--repo OWNER/REPO`** — don't rely on working directory detection
4. **NEVER expose tokens** — don't echo GITHUB_TOKEN, don't log it, don't include in bodies
5. **Batch operations check rate limits first** — Step 1 above
6. **Use `--jq` for filtering** — `gh api ... --jq '.field'` to extract specific values
7. **Templates are suggestions** — adapt to the user's actual content, don't force rigid structure
8. **Cross-reference usernames** — when the issue/comment mentions a user, check if they're in USER.md
提问、分享技巧或报告无法使用。按“有帮助”数量排序。