Skip to content

Tricentis/mcp-skills / Tosca/Cloud/CLI/claude/skills/tosca-cloud

tosca-cloud

Verified

Automates Tosca Cloud via toscactl (default) and tn for CLI gaps. Use for Tosca Cloud CLI, toscactl commands, or tn --loop for Builder/DI/mobile gaps. Does NOT cover on-prem Commander (use Tosca.Commander.IDE.integration).

FileKindSize
CHANGELOG.mdmarkdown458 B
LICENSEother275 B
SKILL.mdskill md4.0 KB
apiexecution-orchestration.mdmarkdown1.0 KB
builder-orchestration.mdmarkdown1.6 KB
di-orchestration.mdmarkdown5.0 KB
execution-orchestration.mdmarkdown1.2 KB
inventory-orchestration.mdmarkdown1.1 KB
journeys-index.mdmarkdown1.9 KB
metadata.jsonconfig137 B
mobile-orchestration.mdmarkdown1.4 KB
path-selection.mdmarkdown1.4 KB
playlist-orchestration.mdmarkdown1.8 KB
reference/di/conventions.mdmarkdown1.4 KB
reference/di/index.mdmarkdown788 B
reference/di/overview.mdmarkdown1013 B
reference/di/workflows/01-row-by-row-comparison.mdmarkdown7.3 KB
reference/di/workflows/02-file-comparison.mdmarkdown660 B
reference/manifest.jsonconfig2.2 KB
reference/tools-catalog.mdmarkdown16.6 KB
reference/tools-index.mdmarkdown2.1 KB
reference/workflows-index.mdmarkdown2.0 KB
reference/workflows/analyze-run-failures.mdmarkdown576 B
reference/workflows/api-execution-connection.mdmarkdown643 B
reference/workflows/connect-tenant.mdmarkdown878 B
reference/workflows/create-playlist.mdmarkdown608 B
reference/workflows/deploy-simulation.mdmarkdown580 B
reference/workflows/di-db-expert-testcase.mdmarkdown755 B
reference/workflows/di-getting-started.mdmarkdown1.8 KB
reference/workflows/inspect-space.mdmarkdown835 B
reference/workflows/loop-autonomous.mdmarkdown1.2 KB
reference/workflows/manage-api-message.mdmarkdown684 B
reference/workflows/manage-folder.mdmarkdown1.4 KB
reference/workflows/mobile-connection.mdmarkdown724 B
reference/workflows/rename-playlist-items.mdmarkdown750 B
reference/workflows/robot-monitoring.mdmarkdown1.2 KB
reference/workflows/run-playlist.mdmarkdown576 B
reference/workflows/scaffold-test-case.mdmarkdown1.8 KB
reference/workflows/search-artifacts.mdmarkdown616 B
runtime-routing.mdmarkdown1.8 KB
simulation-orchestration.mdmarkdown993 B
space-orchestration.mdmarkdown1.8 KB
tn-invocation.mdmarkdown2.0 KB
tool-orchestration.mdmarkdown6.5 KB
tool-planning.mdmarkdown3.4 KB
toscactl-invocation.mdmarkdown2.1 KB
when-to-use-mcp.mdmarkdown4.9 KB

reference/di/workflows/01-row-by-row-comparison.md

View on GitHub
# DI workflow — row-by-row comparison

## Creating a Row-by-Row Comparison (Interactive Workflow)

When the user asks to create a row-by-row comparison test case, follow these steps:

### Step 1 — List available connections
```
Call tosca_dataintegrity_listConnections
→ Present the list to the user.
→ Ask: "Which connection should be the **source** and which should be the **target**?"
```

### Step 2 — Fetch schema for both connections
Run the two-step schema retrieval for each connection. Both can be started in parallel, but each pair (getConnectionSchema → checkSchemaResult) must be sequential.

**EXECUTION (no plan mode, no user confirmation needed for the launcher steps):**
For EACH connection:
```
a. Call tosca_dataintegrity_getConnectionSchema(connectionId="<id>")
   → Returns { launcherLink, notificationId, executorCommandId }
b. Open the launcherLink on the user's machine: Start-Process "<launcherLink>"
c. Call tosca_dataintegrity_checkSchemaResult(notificationId="<notificationId>")
   → Returns { connectionId, count, columns: [{ schemaName, tableName, columnName, dataType, isNullable }] }
```

> **If schema retrieval fails:** The connection may be a "Custom" ODBC type with no stored schema SQL.
> In that case, ask the user to describe the relevant tables and columns manually so you can write the SQL.

### Step 3 — Analyze both schemas and propose SQL + RowKey
Using the column metadata returned:
- Identify matching tables and columns between source and target.
- Propose a `SELECT` statement for each side listing only the relevant columns (avoid `SELECT *`).
- Suggest a `RowKey`: the primary key or a unique business key column.
  - Schema results do NOT include primary key info. If the primary key is not obvious from the column names, ask the user: "Which column(s) uniquely identify a row — for example, an Id or OrderNumber column?"
  - Composite key: join with semicolons, e.g. `"OrderId;LineItemId"`.
  - If no unique key exists: use `"All Source Columns"` — every source column becomes the key.

### Step 4 — Confirm with the user
Present the proposed parameters before creating:
```
Source connection: <name>
Source SQL: SELECT ...
Target connection: <name>
Target SQL: SELECT ...
RowKey: <column(s)>
```
Ask: "Does this look correct, or would you like to adjust anything?"

### Step 5 — Create the test case
```
Call tosca_dataintegrity_createRowByRowComparison with the confirmed parameters.
→ Returns { success, testCaseId, testCasePath }
```

---

## Example — Two database connections

```
► tosca_dataintegrity_listConnections
◄ { connections: [{ id: "01J...", name: "SourceDB", ... }, { id: "01K...", name: "TargetDB", ... }] }
  → User picks SourceDB as source and TargetDB as target.

► tosca_dataintegrity_getConnectionSchema(connectionId="01J...")
◄ { launcherLink: "tricentistosca://di?...", notificationId: "abc-123", executorCommandId: "..." }
► Start-Process "tricentistosca://di?..."
► tosca_dataintegrity_checkSchemaResult(notificationId="abc-123")
◄ { count: 4, columns: [
      { schemaName: "dbo", tableName: "Orders", columnName: "OrderId",    dataType: "int",      isNullable: false },
      { schemaName: "dbo", tableName: "Orders", columnName: "CustomerId", dataType: "int",      isNullable: true  },
      { schemaName: "dbo", tableName: "Orders", columnName: "OrderDate",  dataType: "datetime", isNullable: true  },
      { schemaName: "dbo", tableName: "Orders", columnName: "Total",      dataType: "decimal",  isNullable: true  }
    ]}

► tosca_dataintegrity_getConnectionSchema(connectionId="01K...")
◄ { launcherLink: "tricentistosca://di?...", notificationId: "def-456", executorCommandId: "..." }
► Start-Process "tricentistosca://di?..."
► tosca_dataintegrity_checkSchemaResult(notificationId="def-456")
◄ { count: 4, columns: [
      { schemaName: "dbo", tableName: "Orders", columnName: "OrderId",    dataType: "int",  isNullable: false },
      { schemaName: "dbo", tableName: "Orders", columnName: "CustomerId", dataType: "int",  isNullable: true  },
      { schemaName: "dbo", tableName: "Orders", columnName: "OrderDate",  dataType: "date", isNullable: true  },
      { schemaName: "dbo", tableName: "Orders", columnName: "Total",      dataType: "money",isNullable: true  }
    ]}
  → Both sides have an Orders table with matching column names.
  → OrderId is NOT NULL on both sides — good candidate for RowKey. Confirm with user.

► tosca_dataintegrity_createRowByRowComparison({
    Name: "Orders: SourceDB vs TargetDB",
    Source: { Type: "Database", ConnectionName: "SourceDB", SqlStatement: "SELECT OrderId, CustomerId, OrderDate, Total FROM dbo.Orders" },
    Target: { Type: "Database", ConnectionName: "TargetDB", SqlStatement: "SELECT OrderId, CustomerId, OrderDate, Total FROM dbo.Orders" },
    RowKey: "OrderId"
  })
◄ { success: true, testCaseId: "...", testCasePath: "/TestCases/Orders: SourceDB vs TargetDB" }
```

---

## Example — Two database connections

```
► tosca_dataintegrity_listConnections
◄ { connections: [{ id: "01J...", name: "SourceDB", ... }, { id: "01K...", name: "TargetDB", ... }] }
  → User picks SourceDB as source and TargetDB as target.

► tosca_dataintegrity_getConnectionSchema(connectionId="01J...")
◄ { launcherLink: "tricentistosca://di?...", notificationId: "abc-123", executorCommandId: "..." }
► Start-Process "tricentistosca://di?..."
► tosca_dataintegrity_checkSchemaResult(notificationId="abc-123")
◄ { count: 4, columns: [
      { schemaName: "dbo", tableName: "Orders", columnName: "OrderId",    dataType: "int",      isNullable: false },
      { schemaName: "dbo", tableName: "Orders", columnName: "CustomerId", dataType: "int",      isNullable: true  },
      { schemaName: "dbo", tableName: "Orders", columnName: "OrderDate",  dataType: "datetime", isNullable: true  },
      { schemaName: "dbo", tableName: "Orders", columnName: "Total",      dataType: "decimal",  isNullable: true  }
    ]}

► tosca_dataintegrity_getConnectionSchema(connectionId="01K...")
◄ { launcherLink: "tricentistosca://di?...", notificationId: "def-456", executorCommandId: "..." }
► Start-Process "tricentistosca://di?..."
► tosca_dataintegrity_checkSchemaResult(notificationId="def-456")
◄ { count: 4, columns: [
      { schemaName: "dbo", tableName: "Orders", columnName: "OrderId",    dataType: "int",  isNullable: false },
      { schemaName: "dbo", tableName: "Orders", columnName: "CustomerId", dataType: "int",  isNullable: true  },
      { schemaName: "dbo", tableName: "Orders", columnName: "OrderDate",  dataType: "date", isNullable: true  },
      { schemaName: "dbo", tableName: "Orders", columnName: "Total",      dataType: "money",isNullable: true  }
    ]}
  → Both sides have an Orders table with matching column names.
  → OrderId is NOT NULL on both sides — good candidate for RowKey. Confirm with user.

► tosca_dataintegrity_createRowByRowComparison({
    Name: "Orders: SourceDB vs TargetDB",
    Source: { Type: "Database", ConnectionName: "SourceDB", SqlStatement: "SELECT OrderId, CustomerId, OrderDate, Total FROM dbo.Orders" },
    Target: { Type: "Database", ConnectionName: "TargetDB", SqlStatement: "SELECT OrderId, CustomerId, OrderDate, Total FROM dbo.Orders" },
    RowKey: "OrderId"
  })
◄ { success: true, testCaseId: "...", testCasePath: "/TestCases/Orders: SourceDB vs TargetDB" }
```

---

slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall