type-check

运行 TypeScript 类型检查

Quality

78%

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 ./.agents/skills/type-check/SKILL.md

Quality

Content

100%

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

The body is a model of brevity and actionability: a single heading, one orienting sentence, and an exact executable command. For a simple single-task skill it is clear, complete, and well-organized with no wasted tokens.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean — a heading, a single orienting sentence, and one command — with no padding or explanation of concepts Claude already knows, matching the score-3 anchor of lean, efficient content where every token earns its place.	3 / 3
Actionability	It provides a fully executable, specific, copy-paste-ready command ("pnpm --filter @graphif/project-graph type-check"), matching the score-3 anchor of fully executable commands that are copy-paste ready.	3 / 3
Workflow Clarity	This is a simple single-purpose skill under 50 lines with a single unambiguous command and no destructive or batch operation requiring validation, so per the rubric's simple-skills note workflow clarity can score 3.	3 / 3
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is well-organized with a heading and command block, so per the rubric guideline progressive disclosure can score 3 with just well-organized sections.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 is concise and names a clear, distinct niche, but it is minimal: it states only a single action and lacks any explicit "Use when..." trigger guidance. It is adequate but would benefit from trigger phrasing and slightly broader action coverage.

Suggestions

Add an explicit "Use when..." trigger clause, e.g. "Use when the user asks to run TypeScript type checks, find type errors, or before committing TypeScript changes."

Expand action coverage beyond a single verb to mention concrete outcomes, e.g. "Runs TypeScript type checking and reports type errors for the project."

Include common natural trigger terms users would say, such as "type errors", "type-check", and "TS types".

Dimension	Reasoning	Score
Specificity	The phrase "运行 TypeScript 类型检查" names a concrete domain (TypeScript type checking) and a single action (run it), matching the score-2 anchor of naming a domain and some actions without being comprehensive; it is not vague enough for score 1 but lists only one action rather than the multiple concrete actions required for score 3.	2 / 3
Completeness	The description states what the skill does ("运行 TypeScript 类型检查") but provides no "Use when..." or equivalent explicit trigger guidance for when to invoke it, so per the rubric guideline a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant natural terms such as "TypeScript" and "类型检查" (type-check), but coverage is limited and misses common variations a user might say (e.g., "type errors", "fix types"), fitting the score-2 anchor of some relevant keywords but missing common variations.	2 / 3
Distinctiveness Conflict Risk	"TypeScript 类型检查" targets a clear, narrow niche (running the TypeScript type checker) that is unlikely to trigger for the wrong skill such as test, build, or general lint skills, matching the score-3 anchor of a clear niche with distinct triggers.	3 / 3
	Total	9 / 12 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
description_field	'description' is very short (18 chars), consider making it more detailed	Warning

	Total	15 / 16 Passed

Repository: graphif/project-graph
Path: .agents/skills/type-check/SKILL.md
Commit: cea8af2

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