9 skills published by googleapis across 6 repositories. Together they weigh 11 537 tokens — that is what loading all of them at once would cost you in context.
9 skills 11 537 tokens total vendor account
>- Review a GitHub pull request in the googleapis/mcp-toolbox repo against the logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks you to review, look over, "take a look at", or check whether something is ready to merge in mcp-toolbox, e.g. "review #3703", "can you look at this PR", "is this good to merge", or when they paste an mcp-toolbox PR link. approves, requests changes, comments, labels, or merges on its own.
>- labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a batch) in mcp-toolbox, e.g. "triage #3648", "what labels should this get", "is this a dup", triage a batch of issue numbers, or when they paste an mcp-toolbox never edits labels, comments, closes, or assigns on its own.
Specialized guidance for migrating Node.js packages from the legacy Mocha, Sinon, and Istanbul/c8 ecosystem to Jest. It focuses on surgical test transformation, type safety, and resolving ESM/CommonJS interoperability issues.
Guidelines and playbooks for managing the API lifecycle (BetaApi, GA, ObsoleteApi, Deprecated, and Removal) in the Google Cloud Java SDK. Use this skill when modifying, deprecating, or introducing new public API surfaces.
Use this skill when a dependabot dependency update PR fails.
Verifies local Java SDK changes.
Use this skill when asked to write or draft a commit message. It ensures commit messages follow the conventions in CONTRIBUTING.md.
Helps create a GitHub issue that strictly follows the conventions in CONTRIBUTING.md. Use this skill when asked to create, draft, or open a GitHub issue or bug report.
Helps review your own pull request or local changes before opening a PR. Analyzes diffs against project conventions and checks out branches locally to ensure you can apply changes. Requires the `gh` and `git` CLI tools.