skilldrop-cli 0.16.36 → 0.16.38

package/packs/frontend/skills/web-performance-review/SKILL.md

@@ -8,8 +8,8 @@ description: Read a Lighthouse report or PageSpeed Insights result, with field d
 Reads a Lighthouse run the way a performance engineer does: real-user p75 numbers decide whether
 the page has a problem, and the one lab run explains why. The output names the element, the URL
 and the change, in the order that moves the failing vital most. Accessibility findings in the
-same report go to `accessibility-audit`. What is inside a heavy JavaScript bundle is a
-bundle analysis from the bundler's stats file, not this report. Choosing SSR, static or client rendering for a route is
+same report go to `accessibility-audit`. What is inside a heavy JavaScript bundle is
+`bundle-size-review`. Choosing SSR, static or client rendering for a route is
 `rendering-strategy`. Setting up RUM or alerting on the vitals is `observability-plan`.
 
 ## How to respond
@@ -90,7 +90,7 @@ bundle analysis from the bundler's stats file, not this report. Choosing SSR, st
 ## When NOT to use this skill
 
 - ❌ The accessibility findings in the same Lighthouse report: use `accessibility-audit`
-- ❌ What is in a JavaScript bundle and why it is heavy (source maps, stats files): that needs the bundler's stats file, not a Lighthouse report
+- ❌ What is in a JavaScript bundle and why it is heavy (source maps, stats files): use `bundle-size-review`
 - ❌ Choosing SSR, static, ISR or client rendering for routes: use `rendering-strategy`
 - ❌ Setting up RUM, web-vitals collection, dashboards or alerts: use `observability-plan`
 - ❌ Lighthouse SEO and Best Practices scores; this skill reads the Performance category only

package/packs/frontend/skills/web-performance-review/manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "web-performance-review",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Read a Lighthouse report or PageSpeed Insights result, with field data when there is any (CrUX, PSI loadingExperience or RUM p75), and say what makes the page slow for real users and what to fix first, ranked by how much each fix moves LCP, INP and CLS at the 75th percentile. Names the LCP element and which LCP phase dominates, the elements that shift and why, the long tasks and third parties by main-thread time, and treats estimated savings as lab estimates that overlap. Use when the user shares a Lighthouse JSON or PSI result and asks \"why is this page slow\", \"what should we fix first\", \"we score 92 but Search Console says LCP is poor\", \"did our change fix INP\", \"review this Lighthouse report\", or \"how do we pass Core Web Vitals\".",
   "entrypoint": "SKILL.md",
   "deps": {
@@ -13,6 +13,7 @@
   },
   "related": [
     "accessibility-audit",
+    "bundle-size-review",
     "observability-plan",
     "rendering-strategy"
   ],