CtrlK
BlogDocsLog inGet started
Tessl Logo

setup-agent-code-style-strict

Use when the user asks to add TypeScript strict-mode code-style rules to AGENTS.md for a TypeScript project using strict mode. Do NOT trigger for Deno projects (use setup-agent-code-style-deno) or non-strict TS configurations.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 delivers a fully executable, copy-paste-ready payload with a clear insertion point and tight structure. The main weakness is the Workflow: it is inconsistent with the Injection Location section and lacks an explicit validation feedback loop for the AGENTS.md file mutation.

Suggestions

Reconcile the insertion-point guidance: the Workflow says 'Locate the Architecture section' and 'Insert before Architecture', but the Injection Location section anchors on 'after the Project tooling Stack section, before Architecture' — make both describe the same anchors.

Add an explicit validation/feedback step to the Workflow, e.g. 'Verify the inserted section sits between Project tooling Stack and Architecture; if a Code Style section already exists, abort or merge rather than duplicate'.

Consider moving the large Code Style Rules block into a references/ file (e.g. code-style-strict.md) referenced from the body, to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Mostly lean with no concept over-explanation; the large 'Code Style Rules' block is the legitimate payload rather than padding, though the Purpose/Prerequisites lightly restate the description.

4 / 5

Actionability

Provides the exact markdown block to inject, a precise insertion location, prerequisites, and a copy-paste-ready inline TS example, making the core action fully executable.

5 / 5

Workflow Clarity

A sequenced checklist with verification items exists, but the insertion-point description is inconsistent between the 'Injection Location' section and the Workflow, and validation is a bare checklist item with no validate-fix-retry feedback loop.

3 / 5

Progressive Disclosure

No bundle files exist; the single-purpose skill is organized into clear sections and the injected payload is appropriately inlined, though it slightly exceeds the simple-skill line where pure sectioning would warrant a 5.

4 / 5

Total

16

/

20

Passed

Description

87%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 is tight, specific, and well-scoped with explicit what/when triggers and a clear negative boundary that prevents mis-triggering against sibling skills. Minor room to add synonyms and file extensions for broader natural-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('TypeScript strict-mode code-style rules', 'AGENTS.md') and a precise single action ('add ... rules to AGENTS.md') plus an exclusion refinement, sitting between anchor 3 and 5 but above the not-comprehensive midpoint.

4 / 5

Completeness

Explicitly answers both what (add TypeScript strict-mode code-style rules to AGENTS.md) and when ('Use when the user asks ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes a natural 'Use when the user asks to add ...' trigger plus concrete qualifiers (strict mode, Deno, non-strict TS), but lacks synonyms and file extensions like .ts or 'TS strict'.

4 / 5

Distinctiveness Conflict Risk

A narrow niche (TypeScript strict mode + AGENTS.md) with an explicit negative trigger excluding Deno and non-strict configs, minimizing overlap with sibling skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
korchasa/flowai-plugins
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.