cross-sdk-parity

Keep TypeScript and Python SDK behavior, generated client usage, public API naming, and docs examples aligned. Use when a change affects both SDKs, when generated client pins move, when comparing TS/Python behavior, or when a backend API contract changed. Do not use for single-language internal-only changes.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplar of progressive disclosure: a minimal body that delegates detail to a real, well-organized reference file. The only weakness is that executable commands live entirely in the reference rather than inline, slightly reducing standalone actionability.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean — a single when-to-use line and one pointer to the workflow reference — with every token earning its place and no over-explanation of concepts Claude already knows.	5 / 5
Actionability	The body gives a concrete, executable directive ('Read `references/parity-workflow.md` before changing shared SDK behavior or generated client pins'), with the actual commands living in the referenced file; the body itself contains no inline code or commands, a minor gap.	4 / 5
Workflow Clarity	The referenced workflow lays out a clear sequence (compare contract, generated-client bumps, naming, verification) with a verification checkpoint present, though explicit validate→fix→retry feedback loops are not spelled out.	4 / 5
Progressive Disclosure	A clear overview points to a single, well-signaled, one-level-deep reference (references/parity-workflow.md) that exists in the bundle; content is appropriately split and navigation is trivial.	5 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that crisply defines a niche domain and gives explicit positive and negative triggers. Slight room to broaden trigger-term synonyms, but completeness and distinctiveness are excellent.

Dimension	Reasoning	Score
Specificity	Names the TS/Python parity domain and lists several concrete areas to keep aligned ('SDK behavior, generated client usage, public API naming, and docs examples'), with only minor gaps in enumerating discrete actions.	4 / 5
Completeness	Explicitly states both what to do (keep behavior, client usage, naming, and docs aligned) and when to use it, with multiple concrete trigger phrases plus a negative boundary ('Do not use for single-language internal-only changes').	5 / 5
Trigger Term Quality	Good natural trigger coverage ('a change affects both SDKs', 'generated client pins move', 'comparing TS/Python behavior', 'backend API contract changed'), though a few common synonyms like 'SDK parity' or 'keep SDKs in sync' are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (cross-SDK TS/Python parity) with distinct triggers and an explicit exclusion clause, minimizing conflict with single-language skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ComposioHQ/composio
Path: .agents/skills/cross-sdk-parity/SKILL.md
Commit: b0cf0f9

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.