frontend-lint

코드 품질 검사 에이전트. 린팅과 포맷팅을 관리합니다.

Quality

23%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/frontend-lint/SKILL.md

Quality

Discovery

32%

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

This description provides a basic understanding of the skill's purpose (code quality via linting and formatting) but is too brief and lacks critical selection guidance. The absence of explicit trigger conditions ('Use when...') significantly limits Claude's ability to correctly choose this skill from a large skill library. The description would benefit from more specific actions and natural trigger terms.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios like 'when user asks to lint code, format files, check code style, or run ESLint/Prettier'

List specific concrete actions such as 'run linters, auto-fix formatting issues, check style compliance, configure lint rules'

Include common tool names and file types as trigger terms: 'ESLint, Prettier, Black, .eslintrc, code style, formatting errors'

Dimension	Reasoning	Score
Specificity	Names the domain (code quality) and mentions two actions (linting and formatting), but lacks specific concrete actions like 'run ESLint', 'apply Prettier', or 'fix style violations'.	2 / 3
Completeness	Describes what it does (manages linting and formatting) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant terms '린팅' (linting) and '포맷팅' (formatting), but misses common variations users might say like 'lint', 'format code', 'style check', 'code style', or specific tool names.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to code quality/linting domain, but '코드 품질' (code quality) is broad enough to potentially overlap with code review, testing, or static analysis skills.	2 / 3
	Total	7 / 12 Passed

Implementation

14%

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

This skill content is essentially a job description rather than actionable guidance. It tells Claude what a lint agent does but provides zero concrete instructions on how to actually lint code, configure ESLint/Prettier, or run TypeScript checks. The content lacks any executable examples, commands, or workflows.

Suggestions

Add executable ESLint and Prettier commands with example usage (e.g., `npx eslint . --fix`, `npx prettier --write .`)

Include sample configuration files or snippets for .eslintrc and .prettierrc with recommended settings

Define a clear workflow: 1) Run lint check 2) Review errors 3) Auto-fix what's possible 4) Report remaining issues

Add concrete TypeScript checking commands (e.g., `npx tsc --noEmit`) and how to interpret common errors

Dimension	Reasoning	Score
Conciseness	The content is brief but lacks substance - it's more of a role description than actionable guidance. While not verbose, it doesn't provide enough useful information to justify its tokens.	2 / 3
Actionability	No concrete code, commands, or executable guidance provided. Only lists responsibilities abstractly (e.g., 'ESLint 설정/실행') without showing how to actually perform any task.	1 / 3
Workflow Clarity	No workflow or process steps defined. Simply lists areas of responsibility without any sequence, validation steps, or guidance on how to execute linting/formatting tasks.	1 / 3
Progressive Disclosure	No structure for discovery - just flat bullet lists. No references to detailed documentation, examples, or configuration templates that would help Claude perform the tasks.	1 / 3
	Total	5 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

Reviewed: 29 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.