Where to Find the Latest Updates and Roadmap for google/skills

The google/skills repository does not publish a standalone roadmap file, but you can track its progress through the README.md, GitHub Issues, the Projects board, and release history.

The google/skills repository is an open-source collection of skill implementations maintained by Google. To stay informed about upcoming features and development priorities, you need to know where the team communicates its plans. This guide walks you through each authoritative source, including specific file paths and automation techniques you can use to monitor changes programmatically.

Primary Sources for google/skills Updates and Roadmap

README.md — Front-Page Status Indicator

Located at README.md in the repository root, this file contains a brief announcement that the project is "under active development" along with a current inventory of available skills. While it does not contain a formal roadmap, it serves as the first checkpoint for understanding the project's scope and maturity.

Access directly: https://github.com/google/skills/blob/main/README.md

GitHub Issues — Labeled Roadmap and Feature Requests

The Issues tab is where planned enhancements and community input converge. Filter specifically for issues tagged with label:roadmap to isolate items the maintainers have identified as future work.

• Roadmap-labeled issues: https://github.com/google/skills/issues?q=label%3Aroadmap
• General feature requests: https://github.com/google/skills/issues

GitHub Projects Board — Visualized Milestones

Navigate to https://github.com/google/skills/projects to access the team's internal project board. This visualization breaks down work into milestones, current sprints, and upcoming priorities that are not exposed through flat file browsing.

Release History — Shipped Changes

Check https://github.com/google/skills/releases for official releases with changelogs. Unlike continuous commit streams, releases bundle completed work into discrete, documented units with version semantics.

Pulse Page — Real-Time Activity Snapshot

The Insights → Pulse view at https://github.com/google/skills/pulse aggregates recent commits, merged pull requests, and issue velocity over selectable time windows. Use this for a quick health check without drilling into individual files.

CONTRIBUTING.md — How to Influence the Roadmap

The file CONTRIBUTING.md specifies the formal process for proposing new skills and requesting roadmap inclusion. If your use case is not addressed in existing issues, following this template maximizes the probability of maintainer engagement.

Key location: https://github.com/google/skills/blob/main/CONTRIBUTING.md

Automating Roadmap Monitoring

Fetch the Latest Commit Programmatically

When building CI pipelines or automated reports, retrieve the most recent commit SHA from origin/main:

import subprocess

def latest_commit():
    """Returns the latest commit SHA of google/skills main branch."""
    result = subprocess.check_output(
        ["git", "rev-parse", "origin/main"], text=True
    ).strip()
    return result

print("Latest main commit:", latest_commit())

Run this inside a cloned repository after fetching updates with:

git fetch --all

Query Open Roadmap Issues via GitHub API

For automated dashboards or notification systems, extract open roadmap-labeled issues using the REST API:

import requests

GITHUB_API = "https://api.github.com"
REPO = "google/skills"
TOKEN = "YOUR_GITHUB_TOKEN"  # Personal access token with repo scope required

def get_roadmap_issues():
    """Fetches open issues labeled 'roadmap' from google/skills."""
    url = f"{GITHUB_API}/repos/{REPO}/issues"
    params = {"labels": "roadmap", "state": "open"}
    headers = {"Authorization": f"token {TOKEN}"}
    
    resp = requests.get(url, headers=headers, params=params)
    resp.raise_for_status()
    return resp.json()

for issue in get_roadmap_issues():
    print(f"- #{issue['number']}: {issue['title']}")
    print(f"  URL: {issue['html_url']}\n")

Never commit tokens to version control. Use environment variables or secret management systems in production deployments.

Key Files and Their Roles

File Path	Purpose
README.md	Declares active development status; lists current skills
CONTRIBUTING.md	Formal process for roadmap proposals and skill submissions
.github/ISSUE_TEMPLATE/feature_request.md	Structured input for new feature ideas
projects/ (GitHub UI)	Milestone visualization and sprint planning

Summary

• No dedicated roadmap file exists in google/skills; status is distributed across multiple GitHub-native surfaces
• README.md provides the baseline "active development" signal
• GitHub Issues with roadmap label capture planned work
• Projects board visualizes milestones and sprints
• Releases and Pulse document completed and recent activity respectively
• CONTRIBUTING.md defines how external contributors can propose roadmap items
• Programmatic access via git commands and GitHub API enables automation

Frequently Asked Questions

Does google/skills publish a formal roadmap document?

No. According to the source structure in google/skills, the maintainers do not include a ROADMAP.md or equivalent file. Project direction is communicated through GitHub Issues, the Projects board, and release notes instead.

How can I request a feature be added to the roadmap?

Submit a feature request through GitHub Issues using the template in .github/ISSUE_TEMPLATE/feature_request.md, or follow the process in CONTRIBUTING.md. Issues that align with maintainer priorities may receive the roadmap label and appear on the Projects board.

Is there a way to get notified when the roadmap changes?

Yes. Watch the repository for Issues and Releases, or subscribe to specific roadmap-labeled issues. For programmatic monitoring, poll the GitHub API endpoint shown in the code example above, or use GitHub webhooks to push notifications to your infrastructure.

What does "under active development" mean in the README?

This disclaimer in README.md indicates the repository is not feature-frozen and may undergo breaking changes. It signals that the skill catalog and APIs are evolving, making the Issues and Projects board essential resources for anticipating changes.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}