New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Add Source E2E Integ Test Smt

by GoogleCloudPlatform in GoogleCloudPlatform/spanner-migration-tool

Skill for independently generating Integration Tests and performing End-to-End QA validation for newly added Spanner Migration Tool database sources.

Apache-2.0Auto-check passedTesting & QA

Install Add Source E2E Integ Test Smt

skills CLI
$ npx skills add GoogleCloudPlatform/spanner-migration-tool --skill add-source-e2e-integ-test-smt -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install GoogleCloudPlatform/spanner-migration-tool add-source-e2e-integ-test-smt --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/spanner-migration-tool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/add-source-e2e-integ-test-smt .claude/skills/add-source-e2e-integ-test-smt && rm -rf skills-src

Use ~/.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/

Facts

Skill name
add-source-e2e-integ-test-smt
GitHub stars
155
Token cost
~1.3k tokens
SKILL.md length
671 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

Skill for independently generating Integration Tests and performing End-to-End QA validation for newly added Spanner Migration Tool database sources.

  • Works in 4 steps: Prerequisites → Database Integration Testing → Exhaustive E2E Validation → …
  • Tasks that involve End-to-end testing
  • SKILL.md covers 1. Prerequisites, Phase 1: Database Integration…, Phase 2: Exhaustive E2E… and Phase 3: Final Reporting
  • Calls go, npm and curl

What it does

Add Source E2E Integ Test Smt is an agent skill from GoogleCloudPlatform/spanner-migration-tool. Skill for independently generating Integration Tests and performing End-to-End QA validation for newly added Spanner Migration Tool database sources.

Its SKILL.md is about 1.3k 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 Integration testing. It works with Google Cloud. The repository describes itself as: Spanner migration tool helps you migrate from your existing database/dump files to Spanner. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve End-to-end testing
  • Tasks that involve Integration testing

Example prompts

  • “/add-source-e2e-integ-test-smt”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Prerequisites
  2. Database Integration Testing
  3. Exhaustive E2E Validation
  4. Final Reporting

What it can do on your machine

Read from SKILL.md and the folder at commit 345e09c. 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:

    • go
    • npm
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and curl, 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

Add Source E2E Integ Test Smt loads about 1.3k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 671 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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

The full file from GoogleCloudPlatform/spanner-migration-tool at commit 345e09c, republished under its Apache-2.0 licence (© GoogleCloudPlatform). 671 words, ~1,298 tokens.

Download SKILL.mdSave it as .claude/skills/add-source-e2e-integ-test-smt/SKILL.md (or your agent's skills folder).
name
add-source-e2e-integ-test-smt
description
Skill for independently generating Integration Tests and performing End-to-End QA validation for newly added Spanner Migration Tool database sources.

Skill: SMT New Source Integration and E2E Testing

Description: This skill provides detailed instructions for an independent agent to construct integration tests and execute end-to-end full-stack manual testing for newly integrated database sources in the Spanner Migration Tool (SMT). Operating independently blocks confirmation bias from the original implementation agent.

1. Prerequisites

1.1 Required Input Files

CRITICAL HALT RULE: Before writing any tests, check if the user provided ALL of the following: a data-type mapping matrix file, a feature support matrix file, and a testing environment setup path (e.g., testing_execution.env). If the user did not provide these files and test credentials, you must STOP execution immediately and politely ask the user to provide them before proceeding. These files act as your Absolute Ground Truth for assertions.

1.2 Execution Configuration

If the user provided a testing_execution.env file in the workspace, it typically contains the following schema:

env
REMOTE_WORKSPACE_PATH=
REMOTE_EXEC_TEMPLATE=
REMOTE_SYNC_TEMPLATE=

You MUST load these variables and route any physical server commands (compilation, backend boot-up, UI server) through the REMOTE_EXEC_TEMPLATE.

Phase 1: Database Integration Testing

Step 1: Implement Permanent Backend Tests (ITs)
  1. Implement Integration Tests (IT): You must write and completely implement a comprehensive suite of integration tests inside a new testing/<database>/integration_test.go file. Your tests must execute and assert the core backend database extraction CLI workflows, achieving strict testing parity with the existing MySQL ITs. Use exactly the structural mappings found in the user's provided matrix files to build your test validations.
Step 2: Global Regression Testing
  1. Backend Integration Regressions: Trigger a workspace-wide go test ./testing/... to guarantee the engine did not inadvertently break pre-existing platforms.
  2. UI E2E Regressions: Navigate to ui/ and trigger Cypress regression suites (npm run cypress:run) to ensure new HTML/TS implementations did not poison other database UI flows.

Phase 2: Exhaustive E2E Validation

Because automated Backend ITs only test the CLI, they never test the true physical bridge to the Angular UI. You must act as a QA engineer and manually execute the scenarios across the full live stack using these 4 steps:

Step 3: Server and Environment Boot-up
  1. Backend: Compile and boot the smt-cli web backend server (go run main.go web in the background).
  2. Frontend: Build and boot the Angular frontend (npm run build).
  3. Execution Routing: To determine where and how to run the backend and database, you must read the testing_execution.env file. You must route all your validation commands, compiler executions, and server setups through the REMOTE_EXEC_TEMPLATE strings provided there. Do not attempt to randomly run local commands if a remote template is strictly provided.
Show full SKILL.md (251 more words)Show less
Step 4: Full-Spectrum Database Population

Using the credentials from your test setup, connect directly to the target database shell. Populate the physical DB with every single data type and edge-case table available from the Data-Type mapping matrix (e.g., arrays, proprietary constraints).

Step 5: End-to-End Extraction Execution

Assess your current Agent Tooling capabilities and execute the test:

  • If you possess UI Rendering Capabilities (e.g., Headless browser tools, visual/DOM orchestration hooks): Execute the true end-to-end testing visually by navigating to localhost:8080, rendering the Angular SPA UI directly via your browser tools, and clicking through the direct-connection flow.
  • If you DO NOT possess UI Rendering Capabilities (e.g., standard text/code LLMs): Programmatically simulate the exact Angular direct-connection UI flow by crafting a strictly typed curl -X POST request against the localhost:8080/connect endpoint, followed by fetching localhost:8080/convert/infoschema.
Step 6: Verify Edge-Case Masking

Assert that the backend Go-Drivers did not panic during the extraction. Specifically assert that complex precision masking (like parsing TIMESTAMP(6) or spatial data wrappers) translated correctly on the real wire and returned a strict 200 OK on all handlers.

Phase 3: Final Reporting

Step 7: Compile and Report
  1. Compile: Run go build ./....
  2. Report: Create a final markdown artifact ([database]_testing_report.md) detailing the validation. Include:
    • Explicit printed test validations documenting the status of your Global ITs and Global Cypress suites.
    • The outcome of your True-Integrated Manual DB Evaluation, explicitly highlighting your tooling capabilities and whether you tested the integration natively via UI browser rendering tools, or used the backend curl programmatic API simulation approach.

© GoogleCloudPlatform, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/add-source-e2e-integ-test-smt of GoogleCloudPlatform/spanner-migration-tool.

Open the folder on GitHubat commit 345e09c

Compare with similar skills

Add Source E2E Integ Test Smt 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.

Add Source E2E Integ Test Smt compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add Source E2E Integ Test Smt this skillGoogleCloudPlatform/spanner-migration-tool155—~1.3kAutomated safety check: PassApache-2.0
OpenHarness End-to-End EvalsHKUDS/OpenHarness16k1 repos~2.1kAutomated safety check: NotesMIT
E2E Testinglangflow-ai/langflow156k—~3.3kAutomated safety check: PassMIT
MongoDB Source Connector E2E Harnessairbytehq/airbyte22k—~1.9kAutomated safety check: PassCustom licence
Java SDK E2E Test with Replay Snapshotgithub/copilot-sdk11k—~1.8kAutomated safety check: PassMIT
Go Redis Client Test Runnerredis/go-redis22k—~786Automated safety check: PassBSD-2-Clause

Similar skills

  • OpenHarness End-to-End Evals

    HKUDS/OpenHarness

    Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.

    16k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check: notes

  • E2E Testing

    langflow-ai/langflow

    Write and review Playwright E2E tests for Langflow. An agent skill from langflow-ai/langflow.

    156k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed

  • MongoDB Source Connector E2E Harness

    airbytehq/airbyte

    Official

    Starts a throwaway MongoDB 7.0 replica set and runs the Airbyte spec, check, discover and read commands against source-mongodb-v2 images for local end-to-end testing.

    22k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed

  • Java SDK E2E Test with Replay Snapshot

    github/copilot-sdk

    Official

    Creates a Java SDK end-to-end test for the Copilot SDK that runs against a recorded YAML snapshot through a replay proxy, so CI needs no real authentication.

    11k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed

  • Go Redis Client Test Runner

    redis/go-redis

    Official

    Explains how to run go-redis tests: the Docker Compose stack, make targets, focusing a single Ginkgo spec, the e2e suite and the version environment variables.

    22k GitHub stars~786 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Airbyte Postgres Source E2E Tests

    airbytehq/airbyte

    Official

    Starts a local PostgreSQL 16 container, loads SQL fixtures and runs the Airbyte spec, check, discover and read commands against a chosen source-postgres image.

    22k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed

More from GoogleCloudPlatform/spanner-migration-tool

  • Add Source Support Smt

    GoogleCloudPlatform/spanner-migration-tool

    This skill provides comprehensive architectural instructions for agents to safely implement entirely new database source engines into the Spanner Migration Tool (SMT).

    155 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed

  • Source Baseline Matrix Research Skill

    GoogleCloudPlatform/spanner-migration-tool

    Skill for helping achieve datatype and feature mapping matrix for any source against spanner.

    155 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Add Source E2E Integ Test Smt

What does Add Source E2E Integ Test Smt do?

Skill for independently generating Integration Tests and performing End-to-End QA validation for newly added Spanner Migration Tool database sources. Add Source E2E Integ Test Smt is an agent skill from GoogleCloudPlatform/spanner-migration-tool. Skill for independently generating Integration Tests and performing End-to-End QA validation for newly added Spanner Migration Tool database sources.

When should I use Add Source E2E Integ Test Smt?

Add Source E2E Integ Test Smt fits situations like: tasks that involve End-to-end testing; tasks that involve Integration testing.

How do I install Add Source E2E Integ Test Smt in Claude Code?

Run `npx skills add GoogleCloudPlatform/spanner-migration-tool --skill add-source-e2e-integ-test-smt -a claude-code`. Or copy the skill folder (.agents/skills/add-source-e2e-integ-test-smt in GoogleCloudPlatform/spanner-migration-tool) into .claude/skills/add-source-e2e-integ-test-smt in your project. Claude Code loads it when a task matches its description.

How do I install Add Source E2E Integ Test Smt in Codex?

Run `npx skills add GoogleCloudPlatform/spanner-migration-tool --skill add-source-e2e-integ-test-smt -a codex`. Or copy the skill folder (.agents/skills/add-source-e2e-integ-test-smt in GoogleCloudPlatform/spanner-migration-tool) into .agents/skills/add-source-e2e-integ-test-smt in your project. Codex loads it when a task matches its description.

Can I use Add Source E2E Integ Test Smt 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/spanner-migration-tool --skill add-source-e2e-integ-test-smt -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-source-e2e-integ-test-smt, .gemini/skills/add-source-e2e-integ-test-smt, .github/skills/add-source-e2e-integ-test-smt and .opencode/skills/add-source-e2e-integ-test-smt in your project.

What does Add Source E2E Integ Test Smt need to run?

Going by SKILL.md and its folder, Add Source E2E Integ Test Smt needs the command-line tools its instructions call (go, npm and curl).

Does Add Source E2E Integ Test Smt access the network?

SKILL.md contains no URLs. Its commands use npm and curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Add Source E2E Integ Test Smt 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 Add Source E2E Integ Test Smt use?

Add Source E2E Integ Test Smt is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Add Source E2E Integ Test Smt use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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 Add Source E2E Integ Test Smt?

Skills that share tags, products or a category with Add Source E2E Integ Test Smt: OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), E2E Testing (langflow-ai/langflow, 156k stars), MongoDB Source Connector E2E Harness (airbytehq/airbyte, 22k stars) and Java SDK E2E Test with Replay Snapshot (github/copilot-sdk, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Source E2E Integ Test Smt?

GoogleCloudPlatform (a GitHub organization) maintains it in GoogleCloudPlatform/spanner-migration-tool, which has 155 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 6, 2026.

Source: GoogleCloudPlatform/spanner-migration-tool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.