Io Connectors
Kilo-Org/kilo-marketplace
Guides development and usage of I/O connectors in Apache Beam.
Agent skill
Add Source Spanner To Sourcedb
by GoogleCloudPlatform in GoogleCloudPlatform/DataflowTemplates
Guide for implementing a database source connector in the v2/spanner-to-sourcedb reverse migration Dataflow template.
Install Add Source Spanner To Sourcedb
$ npx skills add GoogleCloudPlatform/DataflowTemplates --skill add-source-spanner-to-sourcedb -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GoogleCloudPlatform/DataflowTemplates add-source-spanner-to-sourcedb --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/DataflowTemplates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb .claude/skills/add-source-spanner-to-sourcedb && 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 "add-source-spanner-to-sourcedb" agent skill from https://github.com/GoogleCloudPlatform/DataflowTemplates/tree/main/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb into .claude/skills/add-source-spanner-to-sourcedb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-source-spanner-to-sourcedb", 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/DataflowTemplates/tree/main/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedbType 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/DataflowTemplates --skill add-source-spanner-to-sourcedb -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GoogleCloudPlatform/DataflowTemplates add-source-spanner-to-sourcedb --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/DataflowTemplates.git skills-src && mkdir -p .agents/skills && cp -r skills-src/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb .agents/skills/add-source-spanner-to-sourcedb && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-source-spanner-to-sourcedb" agent skill from https://github.com/GoogleCloudPlatform/DataflowTemplates/tree/main/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb into .agents/skills/add-source-spanner-to-sourcedb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-source-spanner-to-sourcedb", 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/DataflowTemplates --skill add-source-spanner-to-sourcedb -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GoogleCloudPlatform/DataflowTemplates add-source-spanner-to-sourcedb --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/DataflowTemplates.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb .cursor/skills/add-source-spanner-to-sourcedb && 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 "add-source-spanner-to-sourcedb" agent skill from https://github.com/GoogleCloudPlatform/DataflowTemplates/tree/main/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb into .cursor/skills/add-source-spanner-to-sourcedb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-source-spanner-to-sourcedb", 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/DataflowTemplates.git --path v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb--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/DataflowTemplates --skill add-source-spanner-to-sourcedb -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GoogleCloudPlatform/DataflowTemplates add-source-spanner-to-sourcedb --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/DataflowTemplates.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb .gemini/skills/add-source-spanner-to-sourcedb && 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 "add-source-spanner-to-sourcedb" agent skill from https://github.com/GoogleCloudPlatform/DataflowTemplates/tree/main/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb into .gemini/skills/add-source-spanner-to-sourcedb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-source-spanner-to-sourcedb", 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/DataflowTemplates add-source-spanner-to-sourcedbInstalls 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/DataflowTemplates --skill add-source-spanner-to-sourcedb -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/DataflowTemplates.git skills-src && mkdir -p .github/skills && cp -r skills-src/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb .github/skills/add-source-spanner-to-sourcedb && 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 "add-source-spanner-to-sourcedb" agent skill from https://github.com/GoogleCloudPlatform/DataflowTemplates/tree/main/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb into .github/skills/add-source-spanner-to-sourcedb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-source-spanner-to-sourcedb", 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/DataflowTemplates --skill add-source-spanner-to-sourcedb -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/DataflowTemplates add-source-spanner-to-sourcedb --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/DataflowTemplates.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb .opencode/skills/add-source-spanner-to-sourcedb && 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 "add-source-spanner-to-sourcedb" agent skill from https://github.com/GoogleCloudPlatform/DataflowTemplates/tree/main/v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb into .opencode/skills/add-source-spanner-to-sourcedb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-source-spanner-to-sourcedb", 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
add-source-spanner-to-sourcedb- GitHub stars
- 1.3k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 738 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guide for implementing a database source connector in the v2/spanner-to-sourcedb reverse migration Dataflow template.
- Works in 6 steps: Mandatory Prerequisite Gate → Implement SpToSrcSourceConnector → Implement DMLGenerator and Source… → …
- Tasks that involve Unit testing
- SKILL.md covers Overview, Prerequisites, Architectural Boundaries &… and Datatype Mapping Matrix…, plus 1 more section
- Calls mvn
What it does
Add Source Spanner To Sourcedb is an agent skill from GoogleCloudPlatform/DataflowTemplates. Guide for implementing a database source connector in the v2/spanner-to-sourcedb reverse migration Dataflow template. Details scope boundaries, prerequisites, connector implementations, registry registrations, unit testing, and smoke testing guidelines.
Its SKILL.md is about 1.8k 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 Unit testing. It works with Google Cloud, Google BigQuery and Java. The repository describes itself as: Cloud Dataflow Google-provided templates for solving in-Cloud data tasks. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Unit testing
Example prompts
- “/add-source-spanner-to-sourcedb”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Mandatory Prerequisite Gate
- Implement SpToSrcSourceConnector
- Implement DMLGenerator and Source Processing Classes
- Register Source in Constants & Processor Factory
- Unit Testing & Verification
- Mandatory Live Smoke Testing & Verification
What it can do on your machine
Read from SKILL.md and the folder at commit c95daba. 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:
mvn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Spanner To Sourcedb loads about 1.8k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 738 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
The full file from GoogleCloudPlatform/DataflowTemplates at commit c95daba, republished under its Apache-2.0 licence (© GoogleCloudPlatform). 738 words, ~1,818 tokens.
Download SKILL.mdSave it as
.claude/skills/add-source-spanner-to-sourcedb/SKILL.md (or your agent's skills folder).- name
- add-source-spanner-to-sourcedb
- description
- Guide for implementing a database source connector in the v2/spanner-to-sourcedb reverse migration Dataflow template. Details scope boundaries, prerequisites, connector implementations, registry registrations, unit testing, and smoke testing guidelines.
Skill: Implement Source in Spanner to SourceDb Template
Overview
This skill provides a step-by-step procedure for adding support for a new database source connector to the v2/spanner-to-sourcedb reverse migration template. It details prerequisites, scope boundaries, type mapping requirements, connector implementation, registry registration, unit testing, and smoke testing procedures.
Prerequisites
[!CRITICAL] MANDATORY PREREQUISITE GATE: Before running code searches, inspecting files, or executing unit tests, you MUST verify if the user provided the inputs below. If any required input is missing, STOP IMMEDIATELY and ask the user for clarification before proceeding further.
- Datatype Mapping File: Ask the user to provide or point to the Datatype Mapping Matrix for the new target database, defining the mappings between Spanner GoogleSQL and PostgreSQL dialects and the destination database datatypes.
- Test Setup Details: Ask the user for the test environment details required for live smoke testing, including:
- Target Database Instance details (host/instance name, port, database name, and credentials/connection method).
- Source Spanner Instance & Database details (with Change Stream configured).
- Shard configuration file path or details (if multi-shard / sharded migration).
Architectural Boundaries & Code Scope
All implementation for a new source connector MUST be strictly confined to:
- Source Connector Package:
v2/spanner-to-sourcedb/src/main/java/com/google/cloud/teleport/v2/templates/source/<source_type>/- Implementation of
ISpToSrcSourceConnector(<Source>SpToSrcSourceConnector.java) - Implementation of
IDMLGenerator(<Source>DMLGenerator.java) - Source-specific schema, connection, and DAO classes in package
<source_type>(e.g.,<Source>Dao.java,<Source>ConnectionHelper.java,<Source>TypeHandler.java).
- Implementation of
- Connector Registry / Factory:
SourceProcessorFactory.java(v2/spanner-to-sourcedb/src/main/java/com/google/cloud/teleport/v2/templates/dbutils/processor/SourceProcessorFactory.java)- Dynamic connector registration via
sourceMap.put(Constants.SOURCE_<SOURCE>, new <Source>SpToSrcSourceConnector()).
- Dynamic connector registration via
- Constants:
Constants.java(v2/spanner-to-sourcedb/src/main/java/com/google/cloud/teleport/v2/templates/constants/Constants.java)- Definition of source identifier constant (e.g.,
public static final String SOURCE_<SOURCE> = "<source_type>";).
- Definition of source identifier constant (e.g.,
- Shared Core Registries & Configs:
v2/spanner-common- Registries and configuration files in
spanner-common(updated similar to existing sources).
- Registries and configuration files in
Datatype Mapping Matrix Requirements
Consult the Datatype Mapping Matrix provided in the prerequisites to verify correct datatype conversion between Spanner GoogleSQL/PostgreSQL dialects and the target database. Ensure proper alignment for character, numeric, temporal, binary, boolean, JSON, and any other datatypes as specified in the mapping file.
Step-by-Step Implementation Workflow
Step 0: Mandatory Prerequisite Gate
- Verify Inputs: Inspect the request for the required inputs. If the Datatype Mapping Matrix and Test Setup Details are not provided in the user request, DO NOT run any inspection or execution tools. Stop and ask the user for the missing details first.
Step 1: Implement <Source>SpToSrcSourceConnector
Implement ISpToSrcSourceConnector in com.google.cloud.teleport.v2.templates.source.<source_type>:
- Implement
getDmlGenerator(),getConnectionHelper(),getDao(Shard shard),initConnectionHelper(...),parseShardConfig(...),validate(...),getInformationSchema(...),supportsSharding(),shouldUpdateReadValuesToSpannerRecord(), andclassifyException(...). - Configure connection parameters and dialect-specific setup to work for GoogleSQL and PostgreSQL Spanner dialects similar to other supported sources.
Step 2: Implement <Source>DMLGenerator and Source Processing Classes
- Implement
IDMLGenerator(<Source>DMLGenerator.java) incom.google.cloud.teleport.v2.templates.source.<source_type>to generate dialect-specific DML statements (INSERT,UPDATE,DELETE) for the target database. - Implement remaining source-specific change event context, schema scanning, type mapping, and DAO classes in package
com.google.cloud.teleport.v2.templates.source.<source_type>similar to other existing source connectors.
Show full SKILL.md (298 more words)Show less
Step 3: Register Source in Constants & Processor Factory
- Add the source constant in
Constants.java:java public static final String SOURCE_<SOURCE> = "<source_type>"; - Register connector in
SourceProcessorFactory.java:java sourceMap.put(Constants.SOURCE_<SOURCE>, new <Source>SpToSrcSourceConnector()); - Update corresponding registries and converter files in
v2/spanner-commonsimilar to existing sources.
Step 4: Unit Testing & Verification
Execute Maven unit tests for the template:
mvn test -pl v2/spanner-to-sourcedb \
-Dtest=<Source>SpToSrcSourceConnectorTest,SourceProcessorFactoryTestAll unit tests must pass with BUILD SUCCESS.
Step 5: Mandatory Live Smoke Testing & Verification
[!CRITICAL] MANDATORY EXECUTION REQUIREMENT: Immediately after unit tests pass, you MUST AUTOMATICALLY PROCEED to execute live end-to-end smoke testing using the test environment details provided in the prerequisites. Do NOT stop, pause, or declare completion after unit testing without running the live smoke tests.
[!IMPORTANT] WORKER MACHINE TYPE DIRECTIVE: When submitting the Dataflow job for live smoke testing, you MUST explicitly specify a worker machine type of the correct size with at least 4 vCPUs (e.g.,
--worker-machine-type=n2-standard-4). Omitting this parameter will cause Dataflow job launch validation to fail with a machine specification policy violation.
- Environment Setup:
- Connect to the source Spanner database instance (with change stream enabled) and target database instance configured in the test setup.
- Perform CRUD Operations:
- INSERT: Execute
INSERTstatements covering supported datatypes in the source Spanner database. - UPDATE: Update existing rows in the source Spanner database.
- DELETE: Delete test rows from the source Spanner database.
- INSERT: Execute
- Verify Replication Flow:
- Verify that Spanner Change Stream events flow through Dataflow to the target database.
- Query the target database tables to confirm that
INSERT,UPDATE, andDELETEoperations are accurately reflected in the destination database.
- Retry Loop on Failure:
- If any CRUD operation fails to replicate or produces data discrepancies in the target database, inspect error logs, modify the connector, DML generator, or DAO code, rebuild, and re-test until all operations pass cleanly.
© 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 v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb of GoogleCloudPlatform/DataflowTemplates.
Open the folder on GitHubat commit c95daba
Compare with similar skills
Add Source Spanner To Sourcedb 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 |
|---|---|---|---|---|---|---|
| Add Source Spanner To Sourcedb this skillGoogleCloudPlatform/DataflowTemplates | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Io ConnectorsKilo-Org/kilo-marketplace | 189 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Add Library Testosama-raddad/FireCrasher | 147 | — | ~612 | Automated safety check: Pass | Apache-2.0 | |
| Edt MCP Build TestDitriXNew/EDT-MCP | 295 | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 | |
| Debug Surefireeclipse-rdf4j/rdf4j | 420 | — | ~2.4k | Automated safety check: Pass | BSD-3-Clause | |
| Validationjosstei/maestro-orchestrate | 465 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Add Library Test
osama-raddad/FireCrasher
Add or update a Robolectric JVM unit test for the FireCrasher library.
Edt MCP Build Test
DitriXNew/EDT-MCP
How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo.
Debug Surefire
eclipse-rdf4j/rdf4j
Debug Maven Surefire unit tests by running them in JDWP "wait for debugger" mode (-Dmaven.surefire.debug) and attaching to the forked test JVM using jdb (preferred for CLI/agent debugging)…
Validation
josstei/maestro-orchestrate
Cross-cutting validation methodology for verifying phase outputs and project integrity
Minecraft Testing
Jahrome907/minecraft-agent-skills
Design and implement automated tests for current Minecraft 26.x or legacy 1.21.x mods and plugins using JUnit, MockBukkit, NeoForge Game Tests, or Fabric Game Tests.
More from GoogleCloudPlatform/DataflowTemplates
All 12 skills in this repoSmt E2E Dataflow Debugging
GoogleCloudPlatform/DataflowTemplates
Debugs logical errors and data discrepancies in Dataflow templates by launching jobs via Terraform and comparing source (e.g.
Smt Functional Testing
GoogleCloudPlatform/DataflowTemplates
Functionally tests local Dataflow pipeline changes against the main branch using ephemeral GCP resources and gated approvals.
Add Integ Tests Datastream To Spanner
GoogleCloudPlatform/DataflowTemplates
Specific runner skill that delegates to the Template-Agnostic Meta-Test Orchestrator for the datastream-to-spanner (CDC) template.
Add Integ Tests Gcs Spanner Dv
GoogleCloudPlatform/DataflowTemplates
Specific runner skill that creates integration tests for the gcs-spanner-dv (Data Validation) template.
Add Integ Tests Sourcedb To Spanner
GoogleCloudPlatform/DataflowTemplates
Specific runner skill that delegates to the Template-Agnostic Meta-Test Orchestrator for the sourcedb-to-spanner (Bulk) template.
Add Integ Tests Spanner To Sourcedb
GoogleCloudPlatform/DataflowTemplates
Specific runner skill that delegates to the Template-Agnostic Meta-Test Orchestrator for the spanner-to-sourcedb (Reverse Migration) template.
Related
Works with
Categories
Questions about Add Source Spanner To Sourcedb
What does Add Source Spanner To Sourcedb do?
Guide for implementing a database source connector in the v2/spanner-to-sourcedb reverse migration Dataflow template. Add Source Spanner To Sourcedb is an agent skill from GoogleCloudPlatform/DataflowTemplates. Guide for implementing a database source connector in the v2/spanner-to-sourcedb reverse migration Dataflow template.
When should I use Add Source Spanner To Sourcedb?
Add Source Spanner To Sourcedb fits situations like: tasks that involve Unit testing.
How do I install Add Source Spanner To Sourcedb in Claude Code?
Run `npx skills add GoogleCloudPlatform/DataflowTemplates --skill add-source-spanner-to-sourcedb -a claude-code`. Or copy the skill folder (v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb in GoogleCloudPlatform/DataflowTemplates) into .claude/skills/add-source-spanner-to-sourcedb in your project. Claude Code loads it when a task matches its description.
How do I install Add Source Spanner To Sourcedb in Codex?
Run `npx skills add GoogleCloudPlatform/DataflowTemplates --skill add-source-spanner-to-sourcedb -a codex`. Or copy the skill folder (v2/spanner-to-sourcedb/.agents/skills/add-source-spanner-to-sourcedb in GoogleCloudPlatform/DataflowTemplates) into .agents/skills/add-source-spanner-to-sourcedb in your project. Codex loads it when a task matches its description.
Can I use Add Source Spanner To Sourcedb 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/DataflowTemplates --skill add-source-spanner-to-sourcedb -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-spanner-to-sourcedb, .gemini/skills/add-source-spanner-to-sourcedb, .github/skills/add-source-spanner-to-sourcedb and .opencode/skills/add-source-spanner-to-sourcedb in your project.
What does Add Source Spanner To Sourcedb need to run?
Going by SKILL.md and its folder, Add Source Spanner To Sourcedb needs the command-line tools its instructions call (mvn).
Does Add Source Spanner To Sourcedb access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Add Source Spanner To Sourcedb 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 Spanner To Sourcedb use?
Add Source Spanner To Sourcedb 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 Spanner To Sourcedb use?
About 1.8k tokens (SKILL.md is roughly 7.3k 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 Spanner To Sourcedb?
Skills that share tags, products or a category with Add Source Spanner To Sourcedb: Io Connectors (Kilo-Org/kilo-marketplace, 189 stars), Add Library Test (osama-raddad/FireCrasher, 147 stars), Edt MCP Build Test (DitriXNew/EDT-MCP, 295 stars) and Debug Surefire (eclipse-rdf4j/rdf4j, 420 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Add Source Spanner To Sourcedb?
GoogleCloudPlatform (a GitHub organization) maintains it in GoogleCloudPlatform/DataflowTemplates, which has 1,315 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.
Source: GoogleCloudPlatform/DataflowTemplates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.