javascript-typescript-typescript-scaffold

You are a TypeScript project architecture expert specializing in scaffolding production-ready Node.js and frontend applications. Generate complete project structures with modern tooling (pnpm, Vite, N

Quality

52%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/javascript-typescript-typescript-scaffold/SKILL.md

Quality

Content

65%

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

The body is highly actionable with executable commands and complete configs, but it is verbose (repeated intro, inline full-config dumps) and lacks verification checkpoints in its workflow. Splitting per-project templates into reference files and adding a validate/build-confirm step would improve it.

Suggestions

Add an explicit verification step to the workflow (e.g. run "pnpm install && pnpm type-check && pnpm test" and only report success when they pass).

Move the per-project package.json/tsconfig/directory-tree detail into reference files (e.g. references/nextjs.md, references/nodejs-api.md) and keep SKILL.md as an overview with one-level-deep links.

Trim the repeated intro sentence and the generic "Context" section to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete code and configs that earn their place, but it repeats the frontmatter intro ("You are a TypeScript project architecture expert..."), includes a padded "Context" section, and dumps full package.json/tsconfig blocks that could be tightened.	2 / 3
Actionability	It provides copy-paste-ready, executable commands ("pnpm create next-app@latest . --typescript --tailwind --app", "pnpm create vite . --template react-ts") and complete config files (tsconfig.json, vite.config.ts, app.ts), leaving little ambiguity.	3 / 3
Workflow Clarity	A numbered sequence exists (analyze → init → generate structure → configure tools), but there are no validation or verification checkpoints such as running "pnpm type-check" or confirming the build before declaring the scaffold complete.	2 / 3
Progressive Disclosure	Content is organized into numbered sections, but it is a monolithic ~250-line SKILL.md with all per-project-type configs inline and no bundle files; the per-project detail would be better split into separate reference files.	2 / 3
	Total	9 / 12 Passed

Description

40%

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

The description establishes a clear domain but is truncated mid-sentence, uses second-person voice, and omits an explicit 'Use when' trigger clause, so it answers 'what' only partially and 'when' not at all. Fixing the truncation, switching to third person, and adding trigger guidance would lift most dimensions.

Suggestions

Complete the truncated description and rewrite in third person (e.g. "Scaffolds production-ready TypeScript projects...") instead of "You are a...".

Add an explicit 'Use when...' clause with natural trigger terms users would say (scaffold, boilerplate, starter, project setup, TypeScript project).

List multiple concrete actions beyond 'generate project structures' (e.g. configure type safety, set up testing, add linting) to raise specificity.

Dimension	Reasoning	Score
Specificity	"Generate complete project structures with modern tooling (pnpm, Vite, N" names the domain and a couple of actions, but the description is truncated and does not list multiple distinct concrete actions; the second-person phrasing "You are a TypeScript project architecture expert" incurs the voice penalty, dropping it to 1.	1 / 3
Completeness	It states what the skill does (scaffolding TypeScript projects) but provides no "Use when..." trigger clause, capping completeness at 2, and the truncation at "Vite, N" further weakens the what.	2 / 3
Trigger Term Quality	Terms like "TypeScript", "Node.js", "pnpm", and "Vite" are relevant, but common natural variations (e.g. "scaffold", "boilerplate", "starter") are missing and the sentence is cut off mid-list.	2 / 3
Distinctiveness Conflict Risk	"TypeScript project scaffolding" is a recognizable niche, but without explicit triggers and given the truncation it could still overlap with general coding or build-tooling skills.	2 / 3
	Total	7 / 12 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: rmyndharis/antigravity-skills
Path: skills/javascript-typescript-typescript-scaffold/SKILL.md
Commit: e63f7dd

Reviewed: about 23 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.