Agent skill

Quality Code

A skill your agent uses when writing or reviewing TypeScript/full-stack code.

Install Quality Code

skills CLI

$ npx skills add vvedantb/eva --skill quality-code -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install vvedantb/eva quality-code --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/vvedantb/eva.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/quality-code .claude/skills/quality-code && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "quality-code" agent skill from https://github.com/vvedantb/eva/tree/main/.agents/skills/quality-code into .claude/skills/quality-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-code", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/vvedantb/eva/tree/main/.agents/skills/quality-code

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add vvedantb/eva --skill quality-code -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install vvedantb/eva quality-code --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vvedantb/eva.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/quality-code .agents/skills/quality-code && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "quality-code" agent skill from https://github.com/vvedantb/eva/tree/main/.agents/skills/quality-code into .agents/skills/quality-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-code", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vvedantb/eva --skill quality-code -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install vvedantb/eva quality-code --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vvedantb/eva.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/quality-code .cursor/skills/quality-code && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "quality-code" agent skill from https://github.com/vvedantb/eva/tree/main/.agents/skills/quality-code into .cursor/skills/quality-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-code", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/vvedantb/eva.git --path .agents/skills/quality-code

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add vvedantb/eva --skill quality-code -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install vvedantb/eva quality-code --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vvedantb/eva.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/quality-code .gemini/skills/quality-code && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "quality-code" agent skill from https://github.com/vvedantb/eva/tree/main/.agents/skills/quality-code into .gemini/skills/quality-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-code", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install vvedantb/eva quality-code

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add vvedantb/eva --skill quality-code -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/vvedantb/eva.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/quality-code .github/skills/quality-code && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "quality-code" agent skill from https://github.com/vvedantb/eva/tree/main/.agents/skills/quality-code into .github/skills/quality-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-code", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vvedantb/eva --skill quality-code -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install vvedantb/eva quality-code --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vvedantb/eva.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/quality-code .opencode/skills/quality-code && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "quality-code" agent skill from https://github.com/vvedantb/eva/tree/main/.agents/skills/quality-code into .opencode/skills/quality-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quality-code", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: quality-code
GitHub stars: 101
Used in: 1 other repo
Token cost: ~797 tokens
SKILL.md length: 262 words
Files: 1
Skills in repo: 23
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when writing or reviewing TypeScript/full-stack code.

Reviewing TypeScript/full-stack code
SKILL.md covers Make impossible states…, Let the types flow end-to-end, Pass objects, not positional… and Standard Schema for shared…, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Tasks that involve Observability

What it does

Quality Code is an agent skill from vvedantb/eva. Use when writing or reviewing TypeScript/full-stack code. Encodes principles for type safety (branded types, discriminated unions, end-to-end types), real tests over mocks, OpenTelemetry observability, and picking the right abstractions instead of premature ones.

Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Observability, Type safety and End-to-end testing. It works with OpenTelemetry and TypeScript. The repository describes itself as: Orchestrate sandboxed agents that run in the cloud while you work. The licence is MIT.

When your agent uses it

Reviewing TypeScript/full-stack code
Tasks that involve Observability
Tasks that involve Type safety

Example prompts

“/quality-code”

What it can do on your machine

Read from SKILL.md and the folder at commit 166d464. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quality Code loads about 797 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 262 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~69
When it runs · the whole SKILL.md, loaded when a task matches: ~797

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vvedantb/eva at commit 166d464, republished under its MIT licence (© vvedantb). 262 words, ~797 tokens.

Download SKILL.mdSave it as .claude/skills/quality-code/SKILL.md (or your agent's skills folder).

name: quality-code
description: Use when writing or reviewing TypeScript/full-stack code. Encodes principles for type safety (branded types, discriminated unions, end-to-end types), real tests over mocks, OpenTelemetry observability, and picking the right abstractions instead of premature ones.

Writing quality full-stack TypeScript

Apply these principles when writing or reviewing TypeScript code.

Make impossible states unrepresentable

Use the type system to make invalid states fail at compile time. Fewer reachable states = easier code to read and change.

Branded types

Brand primitives so they can't be mixed up. Validate once at the boundary; downstream code trusts the type.

type PhoneNumber = string & { __brand: "PhoneNumber" };

function parsePhone(input: string): PhoneNumber {
  if (!/^\+?\d{10,15}$/.test(input)) throw new Error(`Invalid: ${input}`);
  return input as PhoneNumber;
}

function sendSMS(to: PhoneNumber, body: string) {
  /* input is trusted */
}

If the project already uses a library with native branded-type support (e.g. Effect), use their primitives instead of rolling your own.

Discriminated unions over flag bags

// Don't — invalid combos representable
type State = { loading: boolean; user?: User; error?: string };

// Do — only valid states exist
type State =
  | { status: "loading" }
  | { status: "success"; user: User }
  | { status: "error"; error: string };

Let the types flow end-to-end

DB schema → server → client should share types without manual duplication. Use whatever end-to-end type tool the project already has (tRPC, oRPC, Elysia, TanStack Start). A users.email branded as Email should arrive on the client still branded.

Don't restate types you can derive. Reach for Pick, Omit, Parameters, ReturnType, Awaited, typeof etc. before writing a new interface. For function arguments, infer from the source instead of typing them by hand:

// Don't — duplicate shape, drifts when the row changes
type UserSummary = { id: string; email: Email };
function renderUser(u: UserSummary) {
  /* ... */
}

// Do — derive from the source of truth
type User = Awaited<ReturnType<typeof db.query.users.findFirst>>;
function renderUser(u: Pick<User, "id" | "email">) {
  /* ... */
}

Pass objects, not positional args

// Don't — swap two args, still compiles
sendEmail("Welcome!", "Hi there");
// Do — order-independent, self-documenting
sendEmail({ to: "alice@x.com", body: "Hi there" });

Skip on hot perf-critical paths; use elsewhere by default.

Standard Schema for shared validation

For libraries or code that doesn't want to pick a validator, accept StandardSchemaV1<unknown, T>.

Tests as real as possible

Don't mock things you can run. Spin up real services:

LocalStack for AWS
Miniflare for Cloudflare Workers
Real Postgres/SQLite (e.g. bun:sqlite), not a mock DB

Mock only third-party services that have no test environment.

OpenTelemetry, not print logging

When adding observability, instrument with OTel spans. The setup cost pays back the first time a user sends a request ID and you can answer instead of guess.

Files

Just SKILL.md in .agents/skills/quality-code of vvedantb/eva.

Open the folder on GitHubat commit 166d464

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in vvedantb/eva, which our catalogue first saw on October 7, 2026.

RhysSullivan/skillsskills/quality-code

Compare with similar skills

Quality Code next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quality Code compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Quality Code this skillvvedantb/eva	101	1 repos	~797	Automated safety check: Pass	MIT	today
Sls Dashboard Builderalibaba/loongsuite-pilot	198	—	~1.8k	Automated safety check: Pass	Apache-2.0	8 days ago
Logfire Instrumentationbasicmachines-co/basic-memory	4.1k	—	~2.3k	Automated safety check: Pass	AGPL-3.0	today
Loongsuite Pilot Insightalibaba/loongsuite-pilot	198	—	~944	Automated safety check: Pass	Apache-2.0	8 days ago
Azure Monitor Opentelemetry TSmicrosoft/skills	3.1k	6 repos	~2.2k	Automated safety check: Pass	MIT	yesterday
Otel JSollygarden/opentelemetry-agent-skills	106	—	~655	Automated safety check: Pass	Apache-2.0	4 days ago

Similar skills

Sls Dashboard Builder
alibaba/loongsuite-pilot
当任务需要创建、修改、扩展或重组阿里云 SLS 的 dashboard JSON 或可导入的大盘配置时使用；尤其适用于线上大盘、强对比的分析看板、已校验的查询包，或需要专业中文标签与指标定义的运维向大盘。
198 GitHub stars~1.8k tokensUpdated 8 days ago
DevOps & CloudAuto-check passed
Logfire Instrumentation
basicmachines-co/basic-memory
Adds Pydantic Logfire tracing, logging and metrics to Python, JavaScript or TypeScript and Rust projects, with the correct setup order and library extras.
4.1k GitHub stars~2.3k tokensUpdated today
DevOps & CloudAuto-check passed
Loongsuite Pilot Insight
alibaba/loongsuite-pilot
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。
198 GitHub stars~944 tokensUpdated 8 days ago
DevOps & CloudAuto-check passed
Azure Monitor Opentelemetry TS
microsoft/skills
Official
Instrument applications with Azure Monitor and OpenTelemetry for JavaScript (@azure/monitor-opentelemetry).
3.1k GitHub starsUsed in 6 repos~2.2k tokens
DevOps & CloudAuto-check passed
Otel JS
ollygarden/opentelemetry-agent-skills
OpenTelemetry in Node.js / JavaScript / TypeScript — NodeSDK, declarative YAML configuration, auto-instrumentations, ESM vs CJS import patterns.
106 GitHub stars~655 tokensUpdated 4 days ago
DevOps & CloudAuto-check passed
Golem Enable Otlp TS
golemcloud/golem
Enabling the OpenTelemetry (OTLP) plugin for a TypeScript Golem agent — exporting traces, logs, and metrics to an OTLP collector, adding custom spans with the invocation context API or…
1.5k GitHub stars~2k tokensUpdated today
DevOps & CloudAuto-check passed

Questions about Quality Code

What does Quality Code do?

A skill your agent uses when writing or reviewing TypeScript/full-stack code. Quality Code is an agent skill from vvedantb/eva. Use when writing or reviewing TypeScript/full-stack code.

When should I use Quality Code?

Quality Code fits situations like: reviewing TypeScript/full-stack code; tasks that involve Observability; tasks that involve Type safety.

How do I install Quality Code in Claude Code?

Run `npx skills add vvedantb/eva --skill quality-code -a claude-code`. Or copy the skill folder (.agents/skills/quality-code in vvedantb/eva) into .claude/skills/quality-code in your project. Claude Code loads it when a task matches its description.

How do I install Quality Code in Codex?

Run `npx skills add vvedantb/eva --skill quality-code -a codex`. Or copy the skill folder (.agents/skills/quality-code in vvedantb/eva) into .agents/skills/quality-code in your project. Codex loads it when a task matches its description.

Can I use Quality Code in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vvedantb/eva --skill quality-code -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quality-code, .gemini/skills/quality-code, .github/skills/quality-code and .opencode/skills/quality-code in your project.

What does Quality Code need to run?

SKILL.md names no scripts, command-line tools or credentials: Quality Code is instructions for the agent only.

Does Quality Code access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quality Code safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quality Code use?

Quality Code is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quality Code use?

About 797 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Quality Code?

Skills that share tags, products or a category with Quality Code: Sls Dashboard Builder (alibaba/loongsuite-pilot, 198 stars), Logfire Instrumentation (basicmachines-co/basic-memory, 4.1k stars), Loongsuite Pilot Insight (alibaba/loongsuite-pilot, 198 stars) and Azure Monitor Opentelemetry TS (microsoft/skills, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quality Code?

vvedantb (a GitHub user) maintains it in vvedantb/eva, which has 101 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 6, 2026.

Source: vvedantb/eva on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Quality Code

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Writing quality full-stack TypeScript

Make impossible states unrepresentable

Branded types

Discriminated unions over flag bags

Let the types flow end-to-end

Pass objects, not positional args

Standard Schema for shared validation

Tests as real as possible

OpenTelemetry, not print logging

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from vvedantb/eva

Related

Questions about Quality Code