GitHub for Meta Muse
Community draft proposes: View your profile, list repos, list open issues, and create issues.
Guide description: Work with the user's GitHub account: verify identity, list repositories, list open issues, and create issues. Use when the user mentions GitHub, a repo, or wants an issue filed.
Community draft. OpenTools has not verified a Muse installation or provider API result. Issue creation is an untested write. Use a scoped test repository after checking profile and repository reads.
View original source ↗How to set it up
Paste a promptDraft — these instructions come from the linked source and have not been independently live-tested by OpenTools.
Source maturity: 🧪 Draft: written from GitHub's public REST API docs; not yet live-tested end-to-end.
Before you start
- personal access token (classic, scopes `repo` + `read:user`, per-user)
Steps
- Review the pinned connectors/github/SKILL.md and its Files list (SKILL.md, bin/github.py).
- Prepare personal access token (classic, scopes `repo` + `read:user`, per-user); provide credentials only through Muse’s secure flow if available.
- Ask Muse to fetch the pinned skill and its exact listed files. Treat this as an upstream proposed installation, not a verified one-click setup.
- Run the source status check `bin/github.py auth` (must print your login); inspect the actual response before using any action.
Prompt to paste into Muse
Inspect this community skill: https://raw.githubusercontent.com/bluman1/muse-connectors/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/github/SKILL.md Read its Files manifest. If this Muse account supports custom skill installation and secure credentials, install exactly those files; otherwise report that the setup is unavailable. Collect credentials through Muse's secure credential flow; never ask me for raw keys in chat. Run the skill's status check and report the actual result.
Account access: personal access token (classic PAT) via the secure credential flow (`credentials.request_api_access`); create one at github.com → Settings → Developer settings → Personal access tokens → Tokens (classic) with scopes `repo` and `read:user`
Allowed hosts: api.github.com
Source status check: `bin/github.py auth` (must print your login)
A successful source status check may verify only configuration or credentials; it is not proof of a working end-to-end integration.
Services it connects with
These are the services the connector uses.