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

60%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/javascript-typescript-typescript-scaffold/SKILL.md

The canonical home for this skill is javascript-typescript-typescript-scaffold in rmyndharis/antigravity-skills

Quality

Content

53%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.

The content is highly actionable with copy-paste-ready scaffolding commands and configs, but it is verbose (inlining boilerplate Claude largely knows), lacks validation checkpoints in its workflow, and uses no progressive disclosure despite a clear opportunity to split per-project templates into reference files.

Suggestions

Move the per-project-type package.json/tsconfig/vite.config templates and directory trees into separate reference files (e.g., references/nextjs.md, references/nodejs-api.md) and link to them from a lean overview.

Add explicit validation checkpoints to the workflow (e.g., run 'pnpm type-check', 'pnpm test', and confirm the dev server boots) before declaring scaffolding complete.

Trim boilerplate that Claude already knows (e.g., what each tool does, generic .gitignore lines) to reduce token load.

Dimension	Reasoning	Score
Conciseness	The body inlines large blocks that largely restate what Claude already knows (full package.json/tsconfig/vite.config templates, boilerplate directory trees), padding the context window with template material that could live in bundle files.	2 / 5
Actionability	Provides fully executable, copy-paste-ready commands and complete config files (pnpm create next-app, vite.config.ts, tsconfig.json, package.json) covering the common Next.js/Vite/Node.js/library cases.	5 / 5
Workflow Clarity	Steps are numbered (Analyze -> Initialize -> Generate per type -> Configure tools), but there are no validation/verification checkpoints despite scaffolding being a batch/generative operation, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the entire content is inlined as a single monolithic document; the per-project-type templates and config blocks clearly belong in separate reference files but are buried inline with no navigation.	2 / 5
	Total	12 / 20 Passed

Description

66%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.

The description clearly conveys the skill's purpose and specific tooling, but it is truncated mid-word and entirely lacks a 'Use when...' trigger clause, which caps its completeness. Trigger-term coverage and distinctiveness are solid.

Suggestions

Complete the truncated description (it cuts off at 'Vite, N') so the full toolset and actions are visible.

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when scaffolding a new TypeScript project, setting up Next.js/Vite/Node.js app structure, or bootstrapping a TS library/CLI').

Include file extensions and synonyms (e.g., .ts/.tsx, 'bootstrap', 'initialize') to broaden natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete tools ('pnpm, Vite, N[ext.js]') and actions ('Generate complete project structures'), but the description is truncated mid-word so coverage is incomplete.	4 / 5
Completeness	It has a clear 'what' (scaffold production-ready TypeScript projects with structure, tooling, type safety, and testing) but no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Good coverage of natural terms a user would say ('TypeScript project', 'scaffolding', 'Node.js', 'frontend applications', 'pnpm', 'Vite'), though a few synonyms and file extensions are missing.	4 / 5
Distinctiveness Conflict Risk	The niche ('TypeScript project architecture expert specializing in scaffolding production-ready Node.js and frontend applications') is mostly distinct, with only minor overlap risk against generic setup/bootstrapping skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/javascript-typescript-typescript-scaffold/SKILL.md
Commit: 57c135b

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.