jquery-4
Migrate jQuery 3.x to 4.0.0 safely in WordPress and legacy web projects. Covers all breaking changes: removed APIs ($.isArray, $.trim, $.parseJSON, $.type), focus event order changes, slim build differences, ES modules migration, and Trusted Types support. Use when: upgrading jQuery to 4.0, fixing "$.isArray is not a function" errors, WordPress jQuery migration, updating legacy JavaScript, or troubleshooting focus/blur event order issues.
87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 an excellent skill description that excels across all dimensions. It provides specific technical details about what breaking changes are covered, includes natural trigger terms users would actually search for (including specific error messages), has an explicit 'Use when:' clause, and occupies a clear niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technical details: 'removed APIs ($.isArray, $.trim, $.parseJSON, $.type), focus event order changes, slim build differences, ES modules migration, and Trusted Types support' - these are highly specific capabilities. | 3 / 3 |
Completeness | Clearly answers both what (migrate jQuery 3.x to 4.0.0, covers breaking changes with specific examples) AND when (explicit 'Use when:' clause with multiple trigger scenarios including error messages and common tasks). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'upgrading jQuery to 4.0', '$.isArray is not a function errors', 'WordPress jQuery migration', 'legacy JavaScript', 'focus/blur event order issues' - includes both technical error messages and common task descriptions. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting specifically jQuery 3.x to 4.0.0 migration with WordPress context. The specific version numbers, API names, and error messages make it unlikely to conflict with general JavaScript or other migration skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable jQuery 4.0 migration skill with excellent code examples and clear workflow guidance. The main weakness is verbosity - the document includes explanatory content Claude doesn't need and could be split into a concise overview with linked reference files. The migration checklist and known issues prevention sections are particularly valuable.
Suggestions
Remove explanatory prose like 'Why this matters' sections and browser support details - Claude knows these concepts
Split into SKILL.md (quick start + critical rules) with separate REFERENCE.md (full API mapping table) and WORDPRESS.md (WordPress-specific content)
Condense the 'Known Issues Prevention' section into a simple table rather than verbose issue-by-issue format
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations (e.g., 'Why this matters' section, browser support details Claude already knows). The content could be tightened by removing explanatory prose and focusing purely on the migration mappings and code examples. | 2 / 3 |
Actionability | Excellent actionability with complete, executable code examples throughout. The migration patterns show exact before/after code, the polyfill section is copy-paste ready, and the WordPress PHP code is complete and functional. | 3 / 3 |
Workflow Clarity | Clear multi-step migration workflow with explicit validation checkpoints: add migrate plugin first, check console for warnings, fix issues, then remove migrate plugin. The migration checklist provides a comprehensive verification sequence with clear ordering. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but it's a monolithic document (~400 lines) that could benefit from splitting detailed reference tables and WordPress-specific content into separate files. All content is inline rather than appropriately distributed. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (502 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.