bambu-studio-ai
Bambu Lab 3D printer control and automation. Activate when user mentions: printer status, 3D printing, slice, analyze model, generate 3D, AMS filament, print monitor, Bambu Lab, or any 3D printing task. Full pi...
Manage a single GitHub repository via chat for non-technical requesters—after they share the repo URL and a temporary personal token, pull status, summarize who did what and when, and create/follow up on issues directly through the GitHub API.
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
SkillHub CLI
skillhub install iamkalio/github-chat-ops打开来源仓库,查看说明和兼容环境后,按来源提供的命令或步骤安装。
将来源链接提供给你的 Agent,让它先读取说明、核对依赖,并向你说明将执行的安装步骤。
Use this skill whenever a non-technical person (often over WhatsApp) needs lightweight GitHub help without cloning or forking a repo. Typical asks:
owner/name.repo scope (private repos) or public_repo (public). Remind them to generate a short-lived token and send it in the chat; you’ll discard it afterward.Always restate the inputs back to them before acting. If anything is missing, pause and ask.
export GITHUB_TOKEN="<token-from-chat>"
unset GITHUB_TOKEN.Authorization: Bearer $GITHUB_TOKEN and Accept: application/vnd.github+json.GET /repos/{owner}/{repo} – confirms access and surfaces default branch.GET /repos/{owner}/{repo}/commits?since=<ISO8601>&until=<ISO8601>
author=<username> or group results locally.GET /repos/{owner}/{repo}/issues?state=all&since=<ISO8601>.
pull_request key.Record the raw JSON responses (e.g., save to /tmp/commits.json) if you need to run jq filters before summarizing.
When you need file-level context (to quote code in an issue or explain why a commit matters), walk the tree via the RES...
这些信息来自收录时的来源分析,可能滞后;使用前请核对最新来源文件。
## Overview
Use this skill whenever a non-technical person (often over WhatsApp) needs lightweight GitHub help without cloning or forking a repo. Typical asks:
- "Tell me what changed recently and who did it."
- "Create an issue describing X."
- "Follow up on existing issues or PRs."
The workflow relies entirely on the GitHub REST API using a personal access token (PAT) the requester provides during the chat.
## 1. Gather prerequisites every session
1. **Repo identifier** – ask for full URL or `owner/name`.
2. **PAT** – confirm it has `repo` scope (private repos) or `public_repo` (public). Remind them to generate a short-lived token and send it in the chat; you’ll discard it afterward.
3. **Task brief** – what they need (issue, summary, follow-up) plus timeframe (e.g., "last 7 days").
_Always restate the inputs back to them before acting. If anything is missing, pause and ask._
## 2. Handle tokens safely
- Paste the token into a temporary shell variable in the current session only:
```bash
export GITHUB_TOKEN="<token-from-chat>"
```
- Never save tokens to disk or log files. When finished, run `unset GITHUB_TOKEN`.
- Every API call must set `Authorization: Bearer $GITHUB_TOKEN` and `Accept: application/vnd.github+json`.
## 3. Fetch repo context before acting
1. **Health check**: `GET /repos/{owner}/{repo}` – confirms access and surfaces default branch.
2. **Recent commits** (for summaries / who-did-what):
- `GET /repos/{owner}/{repo}/commits?since=<ISO8601>&until=<ISO8601>`
- For per-author breakdown, add `author=<username>` or group results locally.
3. **Issues & PRs**: `GET /repos/{owner}/{repo}/issues?state=all&since=<ISO8601>`.
- Distinguish PRs via `pull_request` key.
Record the raw JSON responses (e.g., save to `/tmp/commits.json`) if you need to run jq filters before summarizing.
## 4. Deep repo inspection without cloning
When you need file-level context (to quote code in an issue or explain why a commit matters), walk the tree via the RES...Bambu Lab 3D printer control and automation. Activate when user mentions: printer status, 3D printing, slice, analyze model, generate 3D, AMS filament, print monitor, Bambu Lab, or any 3D printing task. Full pi...
Generative Engine Optimization (GEO) for AI search visibility. Optimize content to appear in ChatGPT, Perplexity, Claude, and Google AI Overviews. Use when optimizing websites, pages, or content for LLM discove...
Agents can sign plugins, rotate credentials without losing identity, and publicly attest to behavior.
Send and receive P2P messages using disposable numbers and PINs. No servers, no accounts. Use for human notifications, approval flows, and agent-to-agent communication.