How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

get-step-info - Prompt - OpenSmartRoute

Name: get-step-info
Author: tango238

Prompt file imported from tango238/property-management-system (.claude/commands/teamkit/get-step-info.md). Fill in {{baseDir}}, {{specDir}}, {{stepName}}, {{versionNumber}}, {{checkSum}}, {{lastModified}} before use. Copyright stays with the author.

Setup

Set baseDir: specs
Get specDir: Read the first argument from the slash command.
- If no argument is provided → Display error message "エラー: specDir 引数が必要です。使用法: /tk-get-step-info <specDir> <stepName>" and STOP execution.
Get stepName: Read the second argument from the slash command.
- If no argument is provided → Display error message "エラー: stepName 引数が必要です。使用法: /tk-get-step-info <specDir> <stepName>" and STOP execution.

Execution

Using baseDir, specDir, and stepName, execute the following steps.

Important:

All output to users (status messages, completion notifications) must be in Japanese.
Save files without asking for user confirmation.

Mission

Read {{baseDir}}/{{specDir}}/status.json and return the version information for the step specified in the arguments. Execute the following process immediately without asking for user confirmation.

Execution Steps

1. Pre-check

Verify that the following files exist:

Target Files:
- {{baseDir}}/{{specDir}}/feature.yml
- {{baseDir}}/{{specDir}}/status.json
Validation:
- If any of these files do not exist → Display the message "エラー: status.json または feature.yml が存在しません。/tk-clean を実行してください" and STOP execution.

2. Load status.json

Read {{baseDir}}/{{specDir}}/status.json.

3. Retrieve step information

From status.json, find the object in steps array that matches the specified stepName.
Set versionNumber: Extract the version field from the matched step object.
Set checkSum: Extract the checksum field from the matched step object.
Set lastModified: Extract the last_modified field from the matched step object.

4. Display results

Display the result in the following format:

ステータス: 成功
ステップ: {{stepName}}
バージョン: {{versionNumber}}
チェックサム: {{checkSum}}
最終更新日時: {{lastModified}}

Execution Example

Input

/teamkit:get-step-info FacilityManagement feature

Output Example

ステータス: 成功
ステップ: feature
バージョン: 1
チェックサム: abc123def456
最終更新日時: 2025-11-24T10:30:00+09:00
メッセージ: ステップ情報を取得しました。

Output Format

The output follows this structure:

ステータス: Execution status (成功 for success, 失敗 for failure)
ステップ: The name of the step queried
バージョン: The version number of the step
チェックサム: The checksum of the step artifact
最終更新日時: The last modified timestamp
メッセージ: A user-friendly message in Japanese

Install get-step-info and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Setup 1. **Set `baseDir`**: `specs` 2. **Get `specDir`**: Read the first argument from the slash command. - If no argument is provided → Display error message "エラー: `specDir` 引数が必要です。使用法: `/tk-get-step-info <specDir> <stepName>`" and **STOP** execution. 3. **Get `stepName`**: Read the second argument from the slash command. - If no argument is provided → Display error message "エラー: `stepName` 引数が必要です。使用法: `/tk-get-step-info <specDir> <stepName>`" and **STOP** execution. # Execution Using `baseDir`, `specDir`, and `stepName`, execute the following steps. **Important**: - All output to users (status messages, completion notifications) must be in **Japanese**. - Save files without asking for user confirmation. --- ## Mission Read `{{baseDir}}/{{specDir}}/status.json` and return the version information for the step specified in the arguments. Execute the following process immediately without asking for user confirmation. ## Execution Steps ### 1. Pre-check Verify that the following files exist: - **Target Files**: - `{{baseDir}}/{{specDir}}/feature.yml` - `{{baseDir}}/{{specDir}}/status.json` - **Validation**: - If any of these files do not exist → Display the message "エラー: `status.json` または `feature.yml` が存在しません。/tk-clean を実行してください" and **STOP** execution. ### 2. Load status.json - Read `{{baseDir}}/{{specDir}}/status.json`. ### 3. Retrieve step information 1. From `status.json`, find the object in `steps` array that matches the specified `stepName`. 2. **Set `versionNumber`**: Extract the `version` field from the matched step object. 3. **Set `checkSum`**: Extract the `checksum` field from the matched step object. 4. **Set `lastModified`**: Extract the `last_modified` field from the matched step object. ### 4. Display results Display the result in the following format: ``` ステータス: 成功ステップ: {{stepName}} バージョン: {{versionNumber}} チェックサム: {{checkSum}} 最終更新日時: {{lastModified}} ``` --- ## Execution Example ### Input ```bash /teamkit:get-step-info FacilityManagement feature ``` ### Output Example ``` ステータス: 成功ステップ: feature バージョン: 1 チェックサム: abc123def456 最終更新日時: 2025-11-24T10:30:00+09:00 メッセージ: ステップ情報を取得しました。 ``` ### Output Format The output follows this structure: - **ステータス**: Execution status (成功 for success, 失敗 for failure) - **ステップ**: The name of the step queried - **バージョン**: The version number of the step - **チェックサム**: The checksum of the step artifact - **最終更新日時**: The last modified timestamp - **メッセージ**: A user-friendly message in Japanese

{ "prompt": "# Setup\n\n1. **Set `baseDir`**: `specs`\n2. **Get `specDir`**: Read the first argument from the slash command.\n - If no argument is provided → Display error message \"エラー: `specDir` 引数が必要です。使用法: `/tk-get-step-info <specDir> <stepName>`\" and **STOP** execution.\n3. **Get `stepName`**: Read the second argument from the slash command.\n - If no argument is provided → Display error message \"エラー: `stepName` 引数が必要です。使用法: `/tk-get-step-info <specDir> <stepName>`\" and **STOP** execution.\n\n# Execution\n\nUsing `baseDir`, `specDir`, and `stepName`, execute the following steps.\n\n**Important**:\n- All output to users (status messages, completion notifications) must be in **Japanese**.\n- Save files without asking for user confirmation.\n\n---\n\n## Mission\n\nRead `{{baseDir}}/{{specDir}}/status.json` and return the version information for the step specified in the arguments.\nExecute the following process immediately without asking for user confirmation.\n\n## Execution Steps\n\n### 1. Pre-check\n\nVerify that the following files exist:\n\n- **Target Files**:\n - `{{baseDir}}/{{specDir}}/feature.yml`\n - `{{baseDir}}/{{specDir}}/status.json`\n\n- **Validation**:\n - If any of these files do not exist → Display the message \"エラー: `status.json` または `feature.yml` が存在しません。/tk-clean を実行してください\" and **STOP** execution.\n\n### 2. Load status.json\n\n- Read `{{baseDir}}/{{specDir}}/status.json`.\n\n### 3. Retrieve step information\n\n1. From `status.json`, find the object in `steps` array that matches the specified `stepName`.\n2. **Set `versionNumber`**: Extract the `version` field from the matched step object.\n3. **Set `checkSum`**: Extract the `checksum` field from the matched step object.\n4. **Set `lastModified`**: Extract the `last_modified` field from the matched step object.\n\n### 4. Display results\n\nDisplay the result in the following format:\n\n```\nステータス: 成功\nステップ: {{stepName}}\nバージョン: {{versionNumber}}\nチェックサム: {{checkSum}}\n最終更新日時: {{lastModified}}\n```\n\n---\n\n## Execution Example\n\n### Input\n\n```bash\n/teamkit:get-step-info FacilityManagement feature\n```\n\n### Output Example\n\n```\nステータス: 成功\nステップ: feature\nバージョン: 1\nチェックサム: abc123def456\n最終更新日時: 2025-11-24T10:30:00+09:00\nメッセージ: ステップ情報を取得しました。\n```\n\n### Output Format\n\nThe output follows this structure:\n- **ステータス**: Execution status (成功 for success, 失敗 for failure)\n- **ステップ**: The name of the step queried\n- **バージョン**: The version number of the step\n- **チェックサム**: The checksum of the step artifact\n- **最終更新日時**: The last modified timestamp\n- **メッセージ**: A user-friendly message in Japanese", "variables": [ "baseDir", "specDir", "stepName", "versionNumber", "checkSum", "lastModified" ], "notes": "Get step information Tools: Bash, Read, Edit, Write, Glob. Arguments: <specDir> <stepName>.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/tango238/property-management-system", "path": ".claude/commands/teamkit/get-step-info.md", "ref": "4a9138c34886f5fccd6451728396af27fbf16612", "url": "https://github.com/tango238/property-management-system/blob/4a9138c34886f5fccd6451728396af27fbf16612/.claude/commands/teamkit/get-step-info.md", "key": "tango238/property-management-system/.claude/commands/teamkit/get-step-info.md" } } }

get-step-info

About

Setup

Execution

Mission

Execution Steps

1. Pre-check

2. Load status.json

3. Retrieve step information

4. Display results

Execution Example

Input

Output Example

Output Format

Install get-step-info and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews