patronum

Select and apply Patronum operators for Effector code with minimal, practical v2.x examples. Use when tasks involve choosing between Patronum operators, composing reactive state flows, replacing manual sample/combine boilerplate with Patronum utilities, explaining operator signatures and return types, or adapting legacy Patronum usage to modern v2 shorthand and import patterns.

Quality

70%

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 ./skills/patronum/SKILL.md

Quality

Content

52%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 skill has a well-organized meta-structure with a clear workflow for classifying and answering Patronum questions, but it critically lacks any concrete code examples, operator signatures, or executable guidance. It reads as a process document rather than a skill that enables Claude to actually write Patronum code. The referenced bundle files (operator-matrix.md, recipes.md, etc.) are absent, leaving the skill hollow.

Suggestions

Add at least 3-5 concrete, executable Patronum v2.x code examples showing common operators like `condition`, `spread`, `combine`, `debug` with explicit imports and return types.

Include an inline quick-reference table of the most common operators with their signatures and one-line descriptions, so the skill is useful even without bundle files.

Provide the referenced bundle files (operator-matrix.md, recipes.md, pitfalls.md, migration-notes.md) or inline their essential content to make the skill self-contained.

Add a concrete before/after migration example showing legacy Patronum v1 usage mapped to v2 shorthand to make the migration guidance actionable.

Dimension	Reasoning	Score
Conciseness	The content is efficient and assumes Claude's familiarity with Effector and reactive programming. Minor verbosity in the workflow classification section and guardrails could be tightened slightly, but overall every section earns its place.	4 / 5
Actionability	The skill provides a structured workflow and output template but contains zero executable code examples, no concrete operator signatures, and no actual Patronum code snippets. It describes what to do at a meta level but doesn't show how to do it with specific operators or code.	2 / 5
Workflow Clarity	The three-step workflow (classify → load references → build answer) is clearly sequenced and logically ordered. The progressive reference loading is a nice touch. However, there are no explicit validation or verification checkpoints, though this is less critical since the skill doesn't involve destructive operations.	4 / 5
Progressive Disclosure	The skill references four separate files (operator-matrix.md, recipes.md, pitfalls.md, migration-notes.md) with clear navigation signals, which is good design. However, no bundle files are provided, meaning all referenced paths are broken and the skill cannot function as described. The core content that would make this skill useful is entirely absent.	2 / 5
	Total	12 / 20 Passed

Description

87%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.

This is a strong, well-crafted skill description that clearly identifies its niche (Patronum operators for Effector v2.x) and provides an explicit 'Use when' clause with five concrete trigger scenarios. The specificity of the domain and the enumeration of use cases make it highly distinctive and unlikely to conflict with other skills. Minor improvements could include naming specific operators or adding more natural user phrasing.

Dimension	Reasoning	Score
Specificity	Lists several specific actions: selecting/applying Patronum operators, composing reactive state flows, replacing manual sample/combine boilerplate, explaining operator signatures and return types, adapting legacy usage to modern v2 shorthand. Minor gaps—doesn't enumerate specific operators or concrete output artifacts.	4 / 5
Completeness	Clearly answers both 'what' (select and apply Patronum operators with practical v2.x examples) and 'when' (explicit 'Use when' clause listing five concrete trigger scenarios including choosing operators, composing flows, replacing boilerplate, explaining signatures, and adapting legacy usage).	5 / 5
Trigger Term Quality	Includes strong domain-specific trigger terms like 'Patronum', 'Effector', 'v2.x', 'sample/combine', 'reactive state flows', 'operator signatures', 'import patterns'. Missing some natural user phrases like 'how to use', specific operator names (e.g., 'spread', 'debug', 'status'), or common misspellings/variations.	4 / 5
Distinctiveness Conflict Risk	Highly distinctive—targets a very specific niche (Patronum library for Effector, v2.x). The combination of 'Patronum', 'Effector', 'v2.x', and specific use cases like 'sample/combine boilerplate' makes it extremely unlikely to conflict with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: aiko-atami/effectorjs-skills
Path: skills/patronum/SKILL.md
Commit: 9a7e508

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