New Feature Design
agentic-community/mcp-gateway-registry
Design and document new features with GitHub issue, low-level design (LLD), expert review, and testing plan.
Workflow for fetching, triaging, analyzing, and reporting on nightly acceptance test results across Beta and GA Google Cloud Terraform providers.
Install Test Monitor Workflow
$ npx skills add GoogleCloudPlatform/magic-modules --skill test-monitor-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules test-monitor-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/workflows/test_monitor .claude/skills/test-monitor-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "test-monitor-workflow" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/workflows/test_monitor into .claude/skills/test-monitor-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-monitor-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/workflows/test_monitorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add GoogleCloudPlatform/magic-modules --skill test-monitor-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules test-monitor-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/workflows/test_monitor .agents/skills/test-monitor-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-monitor-workflow" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/workflows/test_monitor into .agents/skills/test-monitor-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-monitor-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GoogleCloudPlatform/magic-modules --skill test-monitor-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules test-monitor-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/workflows/test_monitor .cursor/skills/test-monitor-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "test-monitor-workflow" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/workflows/test_monitor into .cursor/skills/test-monitor-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-monitor-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/GoogleCloudPlatform/magic-modules.git --path .agents/skills/workflows/test_monitor--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add GoogleCloudPlatform/magic-modules --skill test-monitor-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules test-monitor-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/workflows/test_monitor .gemini/skills/test-monitor-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "test-monitor-workflow" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/workflows/test_monitor into .gemini/skills/test-monitor-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-monitor-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install GoogleCloudPlatform/magic-modules test-monitor-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add GoogleCloudPlatform/magic-modules --skill test-monitor-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/workflows/test_monitor .github/skills/test-monitor-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "test-monitor-workflow" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/workflows/test_monitor into .github/skills/test-monitor-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-monitor-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GoogleCloudPlatform/magic-modules --skill test-monitor-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules test-monitor-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/workflows/test_monitor .opencode/skills/test-monitor-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "test-monitor-workflow" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/workflows/test_monitor into .opencode/skills/test-monitor-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-monitor-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
test-monitor-workflow- GitHub stars
- 974
- Token cost
- ~1k tokens
- SKILL.md length
- 477 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Workflow for fetching, triaging, analyzing, and reporting on nightly acceptance test results across Beta and GA Google Cloud Terraform providers.
- Works in 5 steps: Fetch Test Results → Triage & Aggregate Failure Trends → Cross-Reference GitHub Issues → …
- Tasks that involve End-to-end testing
- SKILL.md covers Overview, Available Skills Used in This…, Execution Steps and Boundaries & Guardrails
- Calls gcloud, python3 and gh
What it does
Test Monitor Workflow is an agent skill from GoogleCloudPlatform/magic-modules. Workflow for fetching, triaging, analyzing, and reporting on nightly acceptance test results across Beta and GA Google Cloud Terraform providers.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering End-to-end testing and Infrastructure as code. It works with Google Cloud, Terraform and GitHub. The repository describes itself as: Add Google Cloud Platform support to Terraform.
When your agent uses it
- Tasks that involve End-to-end testing
- Tasks that involve Infrastructure as code
Example prompts
- “/test-monitor-workflow”
Requirements
- Python 3
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Fetch Test Results
- Triage & Aggregate Failure Trends
- Cross-Reference GitHub Issues
- Categorize Root Causes & Analyze Errors
- Generate Monitoring Report
What it can do on your machine
Read from SKILL.md and the folder at commit 617a89c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gcloudpython3gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gcloud and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Test Monitor Workflow loads about 1k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 477 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 477 words (~1,011 tokens).
“This document guides the agent through the task of monitoring nightly acceptance test runs.”
- name
- test-monitor-workflow
Files
Just SKILL.md in .agents/skills/workflows/test_monitor of GoogleCloudPlatform/magic-modules.
Open the folder on GitHubat commit 617a89c
Compare with similar skills
Test Monitor Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Test Monitor Workflow this skillGoogleCloudPlatform/magic-modules | 974 | — | ~1k | Automated safety check: Pass | Custom licence | |
| New Feature Designagentic-community/mcp-gateway-registry | 968 | — | ~18k | Automated safety check: Notes | Apache-2.0 | |
| Smt E2E Dataflow DebuggingGoogleCloudPlatform/DataflowTemplates | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Avm Tf TestingAzure/terraform-azurerm-avm-ptn-alz | 135 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Schema Coverageelastic/terraform-provider-elasticstack | 210 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Provider Verificationmondoohq/mql | 412 | — | ~3.7k | Automated safety check: Pass | Custom licence |
Similar skills
Smt E2E Dataflow Debugging
GoogleCloudPlatform/DataflowTemplates
Debugs logical errors and data discrepancies in Dataflow templates by launching jobs via Terraform and comparing source (e.g.
- Official
Avm Tf Testing
Azure/terraform-azurerm-avm-ptn-alz
A skill your agent uses for AVM Terraform validation, provider-mocked unit tests, real-Azure integration tests, E2E example tests, PowerShell hooks, OIDC, policy checks, and Avm.Authoring CI behavior.
- Official
Schema Coverage
elastic/terraform-provider-elasticstack
Analyzes a Terraform resource schema and compares it to attributes used in the acceptance test suite (configs + assertions).
Provider Verification
mondoohq/mql
Verify mql provider resource/field changes against real cloud infrastructure.
Devops Pipeline
luongnv89/skills
Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance.
More from GoogleCloudPlatform/magic-modules
All 30 skills in this repoRun Pre Gen Checks
GoogleCloudPlatform/magic-modules
Run fast static checks that don't require generating downstreams, including git submodule verification, gofmt formatting, YAML linting, template validation (version-guard and unused-tmpl), mmv1 core…
Validate Provider Changes
GoogleCloudPlatform/magic-modules
Validate that changes to the generated providers don't introduce breaking changes or fields with missing tests or missing documentation.
Add List Resource Workflow
GoogleCloudPlatform/magic-modules
Opt resource into MMv1 list-resource generation by setting generatelistresource: true and validate it locally with generated tests.
Fetch Nightly Results
GoogleCloudPlatform/magic-modules
Skill to fetch latest nightly test results and metadata for Beta or GA providers from GCS test-metadata.
Automate Test Triage
GoogleCloudPlatform/magic-modules
Skill to automatically triage failing tests by reading test-metadata status files, matching GitHub issues, and generating a multi-section failure report.
Dev Overrides
GoogleCloudPlatform/magic-modules
Configures Terraform CLI with developer overrides to test locally built provider binaries without full Go acceptance tests, enabling rapid plan/apply cycles.
Related
Works with
Categories
Questions about Test Monitor Workflow
What does Test Monitor Workflow do?
Workflow for fetching, triaging, analyzing, and reporting on nightly acceptance test results across Beta and GA Google Cloud Terraform providers. Test Monitor Workflow is an agent skill from GoogleCloudPlatform/magic-modules. Workflow for fetching, triaging, analyzing, and reporting on nightly acceptance test results across Beta and GA Google Cloud Terraform providers.
When should I use Test Monitor Workflow?
Test Monitor Workflow fits situations like: tasks that involve End-to-end testing; tasks that involve Infrastructure as code.
How do I install Test Monitor Workflow in Claude Code?
Run `npx skills add GoogleCloudPlatform/magic-modules --skill test-monitor-workflow -a claude-code`. Or copy the skill folder (.agents/skills/workflows/test_monitor in GoogleCloudPlatform/magic-modules) into .claude/skills/test-monitor-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Test Monitor Workflow in Codex?
Run `npx skills add GoogleCloudPlatform/magic-modules --skill test-monitor-workflow -a codex`. Or copy the skill folder (.agents/skills/workflows/test_monitor in GoogleCloudPlatform/magic-modules) into .agents/skills/test-monitor-workflow in your project. Codex loads it when a task matches its description.
Can I use Test Monitor Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GoogleCloudPlatform/magic-modules --skill test-monitor-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-monitor-workflow, .gemini/skills/test-monitor-workflow, .github/skills/test-monitor-workflow and .opencode/skills/test-monitor-workflow in your project.
What does Test Monitor Workflow need to run?
Going by SKILL.md and its folder, Test Monitor Workflow needs the command-line tools its instructions call (gcloud, python3 and gh). Our summary lists: Python 3.
Does Test Monitor Workflow access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Test Monitor Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Test Monitor Workflow use?
Test Monitor Workflow has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Test Monitor Workflow use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Test Monitor Workflow?
Skills that share tags, products or a category with Test Monitor Workflow: New Feature Design (agentic-community/mcp-gateway-registry, 968 stars), Smt E2E Dataflow Debugging (GoogleCloudPlatform/DataflowTemplates, 1.3k stars), Avm Tf Testing (Azure/terraform-azurerm-avm-ptn-alz, 135 stars) and Schema Coverage (elastic/terraform-provider-elasticstack, 210 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Monitor Workflow?
GoogleCloudPlatform (a GitHub organization) maintains it in GoogleCloudPlatform/magic-modules, which has 974 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 9, 2026.
Source: GoogleCloudPlatform/magic-modules on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.