typescript-providers

Implement, modify, test, or document TypeScript provider packages under ts/packages/providers, including framework adapters for OpenAI, Anthropic, Google, LangChain, Mastra, Vercel, LlamaIndex, Cloudflare, Claude Agent SDK, and TypeSafe. Use for provider-specific TS work; do not use for core-only changes.

Quality

88%

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

82%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-pointer body: perfectly lean, with a real, well-signaled one-level-deep reference whose workflow includes concrete implementation rules and verification commands. The remaining gaps are the absence of any inlined overview of the workflow and of error-recovery guidance around verification.

Suggestions

Add a one-line summary of what the workflow covers (create → rules → verify) so the body serves as a true overview rather than a bare link.

Add a short feedback-loop note in the workflow (e.g., 'on typecheck/test failure, fix and re-run before build:packages') to strengthen the verification checkpoint.

Consider mentioning the verification commands inline in SKILL.md so the most common quick action is available without opening the reference.

Dimension	Reasoning	Score
Conciseness	Three lines, zero padding, no explanations of concepts Claude already knows — it points to the workflow file and stops. Matches the 5 anchor ("lean and efficient; assumes Claude's competence; every token earns its place").	5 / 5
Actionability	"Read `references/provider-workflow.md` before changing a TypeScript provider" is a concrete, executable instruction with a real file target, and the referenced file contains executable commands (pnpm create:provider, typecheck/test/build). Not a 5 because the body itself inlines no actionable step or summary — everything actionable is delegated one file away.	4 / 5
Workflow Clarity	The referenced workflow gives a clear sequence (create/locate → implementation rules → verification) with explicit verification commands ("pnpm --filter @composio/<provider> typecheck", "test", "pnpm build:packages"), so no destructive/batch cap applies. Not a 5 because there is no error-recovery feedback loop (what to do when typecheck/test fails) beyond the implicit retry.	4 / 5
Progressive Disclosure	Single reference, correctly pathed (`references/provider-workflow.md` exists in the bundle), one level deep, and clearly signaled with its trigger condition ("before changing a TypeScript provider") — scored against the actual bundle structure. Not a 5 because the body offers no overview or sectioning of what the workflow covers; navigation relies entirely on the one bare link.	4 / 5
	Total	17 / 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 description: concrete actions, a well-scoped niche with an explicit negative boundary, and rich natural trigger terms including ten framework names. The only gap is that the action verbs are somewhat broad compared to fully concrete enumerated operations.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("Implement, modify, test, or document") with a named domain ("TypeScript provider packages under ts/packages/providers") and a concrete inventory of framework adapters. Not a 5 because the verbs are broad activity classes rather than the fine-grained concrete operations of the 5 anchor (cf. "Extract text and tables... fill forms, merge documents").	4 / 5
Completeness	Explicitly answers both: what ("Implement, modify, test, or document TypeScript provider packages... including framework adapters for...") and when ("Use for provider-specific TS work; do not use for core-only changes"), including a negative boundary trigger. Matches the 5 anchor's clear-and-explicit what + concrete when; not below since the 'when' clause is explicit, not weakly implied.	5 / 5
Trigger Term Quality	Good natural-term coverage: "TypeScript"/"TS" synonym pair, the directory path, and ten real framework names ("OpenAI", "LangChain", "Vercel", "Claude Agent SDK") users would naturally say. Falls short of the 5 anchor's comprehensiveness (e.g., no file extensions or further synonyms like "adapter", "integration").	4 / 5
Distinctiveness Conflict Risk	Clear niche scoped by directory path and an enumerated framework list, with an explicit exclusion ("do not use for core-only changes") that separates it from a core/monorepo skill. Minimal conflict risk, matching the 5 anchor.	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/typescript-providers/SKILL.md
Commit: 98b10d7

Reviewed: 4 days 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.