Name: typescript
Author: cogikyo

Imported from cogikyo/dotfiles (config/opencode/skills/comments/typescript/SKILL.md). Install upstream with npx skills add cogikyo/dotfiles --skill typescript. Copyright stays with the author.

TypeScript comments

This skill adds TypeScript conventions to comments, which owns the general procedure.

Use TSDoc /** */ blocks for exported functions, types, classes, and object or array values that need documentation.
Give exported scalar constants a right-side // comment instead, per comments.
Add @param, @returns, @throws, or @example only when names and types leave the contract unclear, and do not restate the type signature in prose.
Mark deprecation with @deprecated and name the replacement.
Link related symbols with {@link Name} when the reference helps the reader.
Prefer the project's existing TSDoc or JSDoc conventions and lint rules over new tags.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install typescript 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.

{ "ocm": "1", "id": "cogikyo-dotfiles-typescript", "kind": "skill", "name": "typescript", "description": "Use with comments when auditing or editing TypeScript doc comments or TSDoc on exported surfaces.", "publisher": "cogikyo", "version": "1.0.0", "capabilities": { "domains": [ "coding", "legal" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use with comments when auditing or editing TypeScript doc comments or TSDoc on exported surfaces." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/cogikyo/dotfiles", "path": "config/opencode/skills/comments/typescript/SKILL.md", "ref": "fc16edee21a471946276be52cf14d550a241b45b", "url": "https://github.com/cogikyo/dotfiles/blob/fc16edee21a471946276be52cf14d550a241b45b/config/opencode/skills/comments/typescript/SKILL.md", "key": "cogikyo/dotfiles/config/opencode/skills/comments/typescript/SKILL.md" } }, "instructions": "# TypeScript comments\n\nThis skill adds TypeScript conventions to `comments`, which owns the general procedure.\n\n- Use TSDoc `/** */` blocks for exported functions, types, classes, and object or array values that need documentation.\n- Give exported scalar constants a right-side `//` comment instead, per `comments`.\n- Add `@param`, `@returns`, `@throws`, or `@example` only when names and types leave the contract unclear, and do not restate the type signature in prose.\n- Mark deprecation with `@deprecated` and name the replacement.\n- Link related symbols with `{@link Name}` when the reference hel", "cost": { "context_tokens": 175 } }

typescript

About

TypeScript comments

Use it

Install typescript and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews