# google/skills Community Forum: Where to Get Help With the Repository

> Need help with the google/skills repository? Find answers and connect with developers on the official GitHub Issue Tracker, the central hub for all support and discussions.

- Repository: [Google/skills](https://github.com/google/skills)
- Tags: community-resources
- Published: 2026-08-16

---

**There is no dedicated community forum or chat for google/skills; developers must use the GitHub Issue Tracker for all support, questions, and discussions.**

The google/skills repository provides a curated collection of skills for software engineering projects. Unlike many open-source projects, this Google-maintained repository does not operate traditional community channels such as Slack, Discord, mailing lists, or web forums. Instead, all developer interaction flows through GitHub's built-in issue system.

## Support Options for google/skills Developers

### GitHub Issue Tracker: The Primary Channel

The repository's **official support mechanism** is the GitHub Issue Tracker at `https://github.com/google/skills/issues`. According to the source documentation, this is explicitly designated as the place to seek help.

The [`README.md`](https://github.com/google/skills/blob/main/README.md) file contains a dedicated "Support" section that states:

> "If you need help or encounter issues with these skills, **search for existing issues or open a new one** in the [GitHub Issue Tracker](https://github.com/google/skills/issues)." — [README.md, lines 70-73](https://github.com/google/skills/blob/main/README.md#support)

This approach channels all community activity into a single, searchable, and archivable location.

### What the Issue Tracker Handles

- **Bug reports** – Problems with existing skills or documentation
- **Feature requests** – Suggestions for new capabilities
- **Usage questions** – How to implement or customize specific skills
- **General discussion** – Technical conversations about the codebase

## Alternative Channels: What Was Checked

A thorough review of the repository's documentation confirms **no other community platforms exist**:

| Platform | Status | Evidence in Repository |
|----------|--------|------------------------|
| Dedicated forum | Not present | No forum links in [`README.md`](https://github.com/google/skills/blob/main/README.md) or [`CONTRIBUTING.md`](https://github.com/google/skills/blob/main/CONTRIBUTING.md) |
| Slack workspace | Not present | No Slack invitation or workspace mentioned |
| Discord server | Not present | No Discord links found |
| Mailing list | Not present | No mailing list addresses or subscription info |
| Stack Overflow tag | Unofficial | Not endorsed by maintainers |

The [`CONTRIBUTING.md`](https://github.com/google/skills/blob/main/CONTRIBUTING.md) file reinforces this structure by implicitly routing all contributions and communications through the GitHub workflow—issues for discussion, pull requests for changes.

## How to Engage With the Community

Since no real-time chat or forum exists, here is the recommended approach for google/skills developers seeking community interaction:

1. **Search existing issues first** – Avoid duplicates by checking whether your question or problem has already been addressed.

2. **Open a well-formed issue** – Include reproduction steps, expected behavior, and context. This invites maintainers and other contributors to engage.

3. **Watch the repository** – Enable notifications on issues to follow ongoing discussions and learn from other developers' questions.

4. **Participate in responses** – Reply to open issues where you can contribute answers or additional context, building informal community knowledge.

## Summary

- The **google/skills repository has no community forum, chat, Slack, Discord, or mailing list**.
- **All support flows through the GitHub Issue Tracker**, as documented in [`README.md`](https://github.com/google/skills/blob/main/README.md) lines 70-73.
- Developers seeking community interaction should **file or comment on GitHub issues** rather than looking for alternative platforms.
- The [`CONTRIBUTING.md`](https://github.com/google/skills/blob/main/CONTRIBUTING.md) and [`README.md`](https://github.com/google/skills/blob/main/README.md) files consistently point to GitHub-native workflows for all communication.

## Frequently Asked Questions

### Does google/skills have a Slack or Discord community?

No. The repository documentation contains no references to Slack workspaces, Discord servers, or similar real-time chat platforms. All support is intentionally centralized through the GitHub Issue Tracker to maintain searchable, permanent records of discussions.

### Can I email the google/skills maintainers directly?

No public mailing list or support email address is provided in [`README.md`](https://github.com/google/skills/blob/main/README.md) or [`CONTRIBUTING.md`](https://github.com/google/skills/blob/main/CONTRIBUTING.md). The appropriate channel for contacting maintainers is opening a GitHub issue, which the documentation explicitly directs users to use.

### How do I ask a question about using a specific skill?

Search the [GitHub Issue Tracker](https://github.com/google/skills/issues) for similar questions, then open a new issue if needed. Tag your issue appropriately and include relevant details about the skill, your environment, and what you've attempted.

### Is there any plan to create a forum or chat for google/skills?

The source repository contains no roadmap or discussion about establishing alternative community platforms. The current GitHub-centric model appears to be the intended long-term structure for developer support.