CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-state-management

Jotai state management patterns — atoms, globalAtom, contextAtom, and persistence.

70

Quality

86%

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

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 concise, highly actionable with executable code, well-organized, and appropriately self-contained with no padding or unnecessary external references. It is a strong reference-style skill body.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: locations, patterns, forbidden patterns, and executable code with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient' anchor.

3 / 3

Actionability

Provides fully executable TypeScript examples with real imports and file paths for global atoms, context atoms, and component usage — copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

A simple, single-domain pattern reference with clearly organized sections (organization, forbidden patterns, selection, examples); per the simple-skills note it scores 3 when content is clear and well-organized, and no destructive-operation validation is required here.

3 / 3

Progressive Disclosure

Self-contained with no bundle files and no nested references; content is well-organized into clean sections, satisfying the under-50-lines / no-external-references allowance for a top score.

3 / 3

Total

12

/

12

Passed

Description

72%

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 specific and well-targeted to the Jotai state-management niche with strong trigger terms, but it lacks an explicit 'when to use' clause, which caps completeness. Adding a 'Use when...' sentence would round it out.

Suggestions

Append an explicit trigger clause, e.g. 'Use when managing app or feature state with Jotai atoms, or when the user mentions globalAtom, contextAtom, or atom persistence.'

Shift from listing constructs toward concrete actions (e.g. 'Create, organize, and persist Jotai atoms') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ("Jotai state management patterns") and concrete constructs ("atoms, globalAtom, contextAtom, and persistence"), but lists concepts rather than multiple concrete actions, matching the 'names domain and some actions' anchor.

2 / 3

Completeness

Clearly answers 'what' but provides no 'Use when...' or equivalent trigger guidance, so per the rubric a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural domain terms a developer would say — "Jotai", "state management", "atoms", "globalAtom", "contextAtom", "persistence" — giving good coverage of relevant keywords.

3 / 3

Distinctiveness Conflict Risk

"Jotai state management patterns" is a specific niche with distinct triggers and is unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

Total

15

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.