# Github Discussions GRAPHQL

> Incubating Butler wrapper spec for upstream 'GitHub Discussions GraphQL API'.

- Skill: `ocean326/github-discussions-graphql` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add ocean326/github-discussions-graphql`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ocean326/github-discussions-graphql/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: ocean326 (https://skillmd.com/u/ocean326)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ocean326/github-discussions-graphql

---

# GitHub Discussions GraphQL API

## Status

- `incubating`
- 这不是生产可执行 skill，而是 Butler 对外部上游的包装草案。
- 默认不得加入 `chat_default` / `codex_default` / `automation_safe`。

## Proposed Butler Shape

- GitHub Discussions retrieval, maintainer FAQ extraction, release-feedback watch

## Upstream

- repo_or_entry: https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions
- docs: https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions
- upstream_type: official_api
- maturity: high

## Why This Matters

- Strong fit for open-source product support and maintainer communication channels.
- Complements issues and changelog monitoring already common in coding workflows.

## Risks

- Requires GitHub token and GraphQL query discipline.
- Per-repo permissions limit broad public crawling.

## Suggested Future Exposure

- codex_default

## Implementation Checklist

- 明确 Butler 输入输出 contract，不直接复刻上游 API。
- 确认认证、限流、缓存和错误恢复策略。
- 补执行脚本或 tool bridge，而不是只停留在说明文档。
- 补测试与 `skill-pool-verify` / `skill-pool-maintain` 校验。
- 审阅后再决定是否加入 collection registry。