CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

typescript-style

Validate TypeScript/React code against style and architectural conventions

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/pragma/skills/typescript-style/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body is a well-organized, actionable rule catalog with a clear workflow and concrete output contract, weakened mainly by repeated scope/assumption statements and no progressive disclosure into reference files.

Suggestions

Deduplicate the scope/assumptions content (stated in Scope Declaration, Language Scope, and again in Assumptions) into a single section to tighten conciseness.

Move the long rule catalog and/or the JSON output schema into a references/ file referenced one level deep from SKILL.md to improve progressive disclosure.

Add an explicit validation checkpoint (e.g. re-check that every changed file appears in files_checked and that pass reflects hard/should counts) before emitting the JSON.

DimensionReasoningScore

Conciseness

The rule listings earn their place, but scope/assumptions are restated across the Scope Declaration, Language Scope, and Assumptions sections, and the Anti-Pattern Propagation block is over-explained.

3 / 5

Actionability

Provides an executable git-diff command for gathering changed files and a precise JSON output schema with concrete categorized rules; minor gaps in how each rule should be mechanically checked.

4 / 5

Workflow Clarity

Clear input (changed files) -> analyze rules in order -> categorize HARD/SHOULD/WARN -> emit JSON sequence with batch handling for 50+ files; the operation is read-only so the destructive-feedback-loop cap does not apply, though an explicit output self-check is missing.

4 / 5

Progressive Disclosure

No bundle files exist, so all content sits inline in one well-sectioned file with no one-level-deep references to split out the rule catalog or output schema.

3 / 5

Total

14

/

20

Passed

Description

53%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 what the skill validates but omits any 'when to use it' trigger guidance, which caps its completeness. Trigger terms are relevant but thin on synonyms and file extensions.

Suggestions

Add a 'Use when ...' clause naming natural triggers, e.g. 'Use when reviewing TypeScript/React (.ts/.tsx) changes for style and architecture violations.'

Include file extensions and synonyms (.ts, .tsx, React components, hooks) to broaden trigger-term coverage.

Optionally list 1-2 more concrete actions (e.g. 'flags anti-patterns, checks hook dependencies') to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ('TypeScript/React code') and one concrete action ('Validate ... against style and architectural conventions'), but the action set is minimal rather than comprehensive.

3 / 5

Completeness

Clearly states what the skill does, but provides no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes relevant keywords (TypeScript, React, style, architectural conventions) but lacks natural synonyms and file extensions (.ts, .tsx) users would commonly say.

3 / 5

Distinctiveness Conflict Risk

The TypeScript/React style-validation niche is mostly distinct from other skills, with only minor overlap risk against general linters.

4 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

peteski22/agent-pragma

Path

plugins/pragma/skills/typescript-style/SKILL.md

Reviewed

Table of Contents

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.