CtrlK
BlogDocsLog inGet started
Tessl Logo

typescript-sdk

Implement or modify TypeScript SDK behavior in @composio/core or shared TypeScript packages, including tools, toolkits, sessions, auth configs, connected accounts, modifiers, and generated SDK surfaces. Use for TS runtime/API work; pair with typescript-testing for verification and cross-sdk-parity when Python must match.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 exemplary minimal skill body: lean, zero padding, one unambiguous directive, and a well-placed single reference that carries the detail. The only refinements are dropping the redundant restatement of the description and optionally inlining one quick verification command.

DimensionReasoningScore

Conciseness

The three-line body has no conceptual explanation and fully delegates detail to the reference file, assuming Claude's competence. One minor trim exists: "Use this skill for TypeScript SDK implementation work." restates the frontmatter description, so not quite every token earns its place.

4 / 5

Actionability

"Read `references/core-sdk.md` before editing `ts/packages/core` or shared TypeScript SDK packages" is a concrete directive with real paths, and the referenced file contains executable commands (pnpm --filter @composio/core typecheck/test). This is mostly executable guidance with a minor gap: no inline quick-start command or example in the body itself.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill under 50 lines whose single action — read the reference before editing core packages — is unambiguous and correctly sequenced (read before edit). No destructive or batch operations are involved, so no validation cap applies.

5 / 5

Progressive Disclosure

The body is a clean overview pointing to a single well-signaled, one-level-deep reference (references/core-sdk.md) that actually exists and matches the referenced scope (ts/packages/core file map, patterns, and verification commands). Navigation is trivial and content is appropriately split.

5 / 5

Total

18

/

20

Passed

Description

78%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 description: concrete domain surfaces, named packages, explicit use-for guidance, and clear separation from sibling skills. The main improvement space is a richer set of trigger phrases and more varied action verbs.

DimensionReasoningScore

Specificity

"Implement or modify TypeScript SDK behavior... including tools, toolkits, sessions, auth configs, connected accounts, modifiers, and generated SDK surfaces" enumerates many concrete surfaces and named packages (@composio/core), but the action verbs are limited to "implement or modify", so coverage of specific actions has minor gaps rather than being comprehensive.

4 / 5

Completeness

It clearly answers "what" (implement/modify SDK behavior in named packages with an enumerated surface list) and includes an explicit "Use for TS runtime/API work" trigger clause, satisfying the 'Use when' requirement. The "when" is a single brief trigger phrase rather than multiple concrete trigger conditions, so it falls at anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Natural terms include "TypeScript SDK", "@composio/core", "TS runtime/API work", and "Python must match", with a TypeScript/TS synonym pair. A few natural phrasings users might say (e.g., "Composio", package-level terms) are missing, so keyword coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

"in @composio/core or shared TypeScript packages" pins a clear niche, and the routing to sibling skills ("pair with typescript-testing for verification and cross-sdk-parity when Python must match") makes it clearly distinguishable with minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

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
Reviewed

Table of Contents

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.