talos-sdk-parity
Ensures protocol changes are applied consistently across all language SDKs with updated conformance tests.
Install
mkdir -p .claude/skills/talos-sdk-parity && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14184" && unzip -o skill.zip -d .claude/skills/talos-sdk-parity && rm skill.zipInstalls to .claude/skills/talos-sdk-parity
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when a Talos contract, protocol primitive, frame shape, digest rule, capability field, or validation behavior must be propagated across one or more SDKs. Preserve contract ownership, avoid local reimplementation drift, update language-specific conformance tests, and call out which SDKs were intentionally left unchanged.Key capabilities
- →Identify the owning contract, vector, or protocol rule
- →Map impacted SDKs for a given change
- →Prefer consuming published contract artifacts over reimplementation
- →Update language-specific conformance tests
- →State explicitly which SDKs were updated or reviewed
- →Avoid silently forking behavior between SDKs
How it works
The skill ensures consistency across multiple Talos SDKs by identifying impacted SDKs, preferring shared artifacts, and updating conformance tests.
Inputs & outputs
When to use talos-sdk-parity
- →Update a protocol in all SDKs
- →Ensure cross-language contract parity
- →Add a new capability field
About this skill
Talos SDK Parity
Use this skill when a change must remain consistent across multiple language SDKs.
Load only what the task needs:
references/sdk-map.md../planning/program-anchor-index.md- The closest SDK
AGENTS.mdorCLAUDE.md
Workflow:
- Identify the owning contract, vector, or protocol rule first.
- Map impacted SDKs before editing. Python and TypeScript are the most likely first-order consumers, but Go, Java, and Rust may also need parity updates.
- Prefer consuming published contract artifacts or shared generated outputs over re-implementing canonical logic in each SDK.
- For each touched SDK, update the smallest test or conformance path that proves parity.
- State explicitly which SDKs were updated, which were reviewed only, and which still need follow-up.
Guardrails:
- Do not silently fork behavior between SDKs on hashed, signed, or validated payloads.
- Do not bury a protocol change inside one SDK without tracing the others.
- Do not claim multi-SDK parity without naming the validated languages.
Done checklist:
- Source-of-truth artifact identified.
- Impacted SDKs traced.
- Per-language validation updated or justified.
- Final summary names parity status by SDK.
When not to use it
- →When a change does not need to remain consistent across multiple language SDKs
- →When the change is not related to Talos contracts, primitives, or validation behavior
Limitations
- →The skill is specific to Talos contracts, protocol primitives, and SDKs.
- →The skill requires explicit naming of validated languages for multi-SDK parity claims.
- →The skill prohibits silently forking behavior between SDKs on hashed, signed, or validated payloads.
How it compares
This skill provides a structured workflow for maintaining consistency across multiple SDKs for protocol changes, preventing divergence that might occur with independent updates.
Compared to similar skills
talos-sdk-parity side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| talos-sdk-parity (this skill) | 0 | 3mo | No flags | Advanced |
| swapper-integration | 6 | 5mo | Caution | Intermediate |
| run-api-e2e-tests | 7 | 6mo | Review | Beginner |
| langfuse-ci-integration | 2 | 26d | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
swapper-integration
shapeshift
Integrate new DEX aggregators, swappers, or bridge protocols (like Bebop, Portals, Jupiter, 0x, 1inch, etc.) into ShapeShift Web. Activates when user wants to add, integrate, or implement support for a new swapper. Guides through research, implementation, and testing following established patterns.
run-api-e2e-tests
novuhq
Run e2e tests for the API service. Use when the user wants to run API E2E tests.
langfuse-ci-integration
jeremylongshore
Configure Langfuse CI/CD integration with GitHub Actions and automated testing. Use when setting up automated testing, configuring CI pipelines, or integrating Langfuse tests into your build process. Trigger with phrases like "langfuse CI", "langfuse GitHub Actions", "langfuse automated tests", "CI langfuse", "langfuse pipeline".
api-test-generator
mikopbx
Генерация полных Python pytest тестов для REST API эндпоинтов с валидацией схемы. Использовать при создании тестов для новых эндпоинтов, добавлении покрытия для CRUD операций или валидации соответствия API с OpenAPI схемами.
http-generate
spring-ai-alibaba
Generates HTTP request examples for Spring Boot Web interfaces according to task specification and saves them as .http files in module-generate.md directories
openapi-analyzer
mikopbx
Извлечение и анализ OpenAPI 3.1.0 спецификации из MikoPBX для валидации эндпоинтов. Использовать при проверке соответствия API, генерации тестов, проверке схем эндпоинтов или интеграции с навыками endpoint-validator и api-test-generator.