You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
vitals-review: run log for skilld-dev/skilld.dev #679
2026-10-31T06:21:00.000Z — vitals-review on skilld-dev/skilld.dev | 0 found | 0 new | 0 already known | 0 outside allowed scope | 0 over 5 files | 0 issues requested
Site: s_08aae654, https://skilld.dev. Matched exactly against tracked nuxt.config.ts → site.url.
Field coverage: Cloudflare returned one Poor finding. CrUX summary and trend are unavailable, so origin p75 direction is unknown.
Lab coverage: 16 pages, 32 strategy groups, 100 retained Scans. Judged 99 completed Scans; excluded one failed Scan. Read FCP details for the latest two completed Scans of each eligible group, plus reference details. History is bounded by the retained limit.
No new fix ready to file. Poor measurements remain.
No persistent Lab drop was established. No Suspect or MissingMetric verdict arose in the judged suffixes. Older FCP onset remains undated where only the latest Poor pair was needed.
Excluded failed Scan: 075a50cd-0c8c-4650-9065-bf51a87a114a, basecamp mobile, September 25. Its null metrics were not treated as zeros.
Poor lab dispositions
Homepage LCP: latest mobile values are 5101 and 5851 ms. Both name a demo image. Observed resource load delays are approximately 3598 and 4967 ms. These observed phases do not partition modeled LCP.
app/pages/_HomeDemoCarousel.vue shuffles the current demo during onMounted. PR #576 explicitly requests a random starting order per visit. Changing that behavior requires Harlan’s decision about preserving variety without replacing the initial image after hydration. No proposal overrides that decision.
Shared CSS and FCP: action 01M2J4SG3QK0095X6TVB0BP6T9 names blocking entry and component stylesheets. PR #500 already restored inline component styles and recorded remaining homepage and Skill LCP cost. Current configuration retains that fix. Live homepage HTML still links entry, DemoWriting, and WhyVisual CSS.
No distinct new CSS fix was established. Harlan owns remaining-cost triage. The other Poor pages share this evidence, so they receive no separate proposals. Several retained Skill and org Scans also measure missing-page content after redirects; their measurements do not establish a new route repair.
Fix follow-up and coverage limits
No closed routine:vitals-review issues were returned. No routine-owned fix qualified for a post-deploy Scan.
Public repository visibility was verified. Open issues, open PR bodies, matching closed issues, and relevant merged PRs were read. No matching open performance repair was found.
Site status is degraded because health.crawlBlockerCount is unavailable. Its Next Action concerns indexing, outside this routine. Lighthouse versions vary across retained history, limiting causal comparisons.
Repository and GitHub stayed read only. No NuxtSEO write was made.
Confidence: 88/100. Untested: local causal replay and field recovery after today’s deploy.
2026-11-04T01:00:00.000Z — vitals-review on skilld-dev/skilld.dev | 0 found | 0 new | 0 already known | 0 outside allowed scope | 0 over 5 files | 0 issues requested
Site: s_08aae654, https://skilld.dev. Exactly matched sites list against tracked nuxt.config.ts → site.url.
Field coverage: unavailable. CrUX summary and trend report insufficient traffic. Origin p75 direction is unknown. Web Analytics findings report source: null, no field element data, and total: 0. This does not establish good performance.
Lab coverage: 20 pages, 40 separate page/strategy series. Read 100 retained Scans, including 99 completed and one failed. Read 76 successful Scan details for FCP and cause evidence.
No proposals returned. Poor lab measurements exist, but current cause confirmation and duplicate checks remain incomplete.
Lab verdicts
Each cell lists LCP / FCP / TBT / CLS. Short means ShortSeries. Counts cover the contiguous latest Lighthouse release only.
No Lab drop was established. The mobile TBT Suspect and desktop TBT Unstable series file nothing.
Version boundaries excluded older measurements for homepage mobile; both nuxt-seo strategies; mobile torch_npu, code-review and szeyu; desktop theory-of-constraints, omarchy, vercel-ai-sdk and tristanmanchester; and mobile better-chatbot-patterns. Single Scans after version changes prove neither persistence nor recovery.
FCP details establish the latest-pair verdicts above. Earlier FCP details were intentionally bounded for Poor series. They do not establish a complete FCP history or an earlier onset.
Skipped failed Scan: 075a50cd-0c8c-4650-9065-bf51a87a114a, mobile omarchy, 2026-09-25. Its null metrics were excluded.
Poor measurements and disposition
Pairs below run from older to newer. Values are milliseconds.
Withheld: current cause and ownership checks incomplete
/skills/api/git/openclaw-multi-search-engine
4972 → 5791
4620 → 4533
Withheld: current cause and ownership checks incomplete
/orgs/tristanmanchester
Not persistently Poor
3696 → 3241
Withheld: current cause and ownership checks incomplete
The four Skill pages map through legacy redirects to /gh routes and layers/registry/app/components/SkillDetail.vue. Retired /orgs routes map through layers/registry/server/utils/orgs-route-policy.ts to author profiles.
Performance action 01M2J4SG3QK0095X6TVB0BP6T9 identifies shared render-blocking CSS. Its producer evidence is aged, dated 2026-10-14. The detail response exposes 50 of 51 evidence items, with a continuation cursor.
Scan details identify blocking entry CSS, SkillDetail CSS and DemoWriting CSS on the affected Skill pages. SkillDetail.vue statically imports _SkillDemo.vue, which imports _DemoWriting.vue. This provides a possible shared cause, but does not prove the change needed to remove the measured delay.
Live read-only checks followed the api/git and omarchy redirects. Both responses still link three stylesheets. Their entry asset is now entry.UM25vn7w.css, while the latest Poor Scans cite entry.CvwryD2V.css. Current configuration also contains the component-style build change from commit 80d9b79c, PR #500. These observations do not establish current lab persistence or confirm a fix outcome.
No page was selected as the highest-traffic representative of this shared cause. No separate proposals were created for its affected pages or metrics.
Ownership and fix follow-up
The controller supplied complete open issue and pull request lists. Most ownership bodies were complete. Issue #655 and PR #680 bodies were truncated.
For each of the five Poor page series above, the missing duplicate check is the complete body comparison against #655 and #680. Their visible dependency scope does not establish ownership of the CSS defect. It also does not justify claiming complete duplicate checks. No existing owner was positively matched.
Closed issue history was absent. Matching prior fixes, closing pull requests and their deployments could not be checked. Fix follow-up is incomplete. No fix was declared confirmed, failing or recurrent.
Next actor: controller, supply complete ownership bodies and closed routine history. A later review also needs current cause evidence before proposing a shared CSS fix.
All required Skills were present. Repository and GitHub access remained read only. No NuxtSEO mutation ran. Evidence is retained under /home/agent/scratch/vitals-review/20261104T113600Z/.
Confidence: 85/100. Current performance impact, complete duplicate checks and prior-fix deployment outcomes remain unverified.
Activity
harlan-github-agent commentedon Oct 31, 2026
2026-10-28T01:00:00.000Z — Skipped. This run was due more than 6 hours ago, so it was skipped.
harlan-github-agent commentedon Oct 31, 2026
2026-10-31T06:21:00.000Z — vitals-review on skilld-dev/skilld.dev | 0 found | 0 new | 0 already known | 0 outside allowed scope | 0 over 5 files | 0 issues requested
Site:
s_08aae654,https://skilld.dev. Matched exactly against trackednuxt.config.ts→site.url.Field coverage: Cloudflare returned one Poor finding. CrUX summary and trend are unavailable, so origin p75 direction is unknown.
Lab coverage: 16 pages, 32 strategy groups, 100 retained Scans. Judged 99 completed Scans; excluded one failed Scan. Read FCP details for the latest two completed Scans of each eligible group, plus reference details. History is bounded by the retained limit.
No new fix ready to file. Poor measurements remain.
Full report and diagram
Field disposition
/,#hero-heading: LCP p75 4532 ms, Poor, 210 estimated views, Cloudflare window October 4–31. Latest mobile lab CLS: 0.048.The finding qualifies by severity and traffic. A distinct new fix was not established:
private, no-storedoes not establish an edge cache failure.786a28a1, finishing at 05:30:41 UTC.The field heading and lab demo image are different LCP elements. Their causes cannot be substituted.
Every lab series
Each cell lists LCP / FCP / TBT / CLS.
P = Poor series; S = Steady; U = Unstable; Short = ShortSeries for all four metrics.
//gh/harlan-zw/nuxt-seo/skills/api/git/openclaw-multi-search-engine/skills/basecamp/omarchy/omarchy/skills/fal3/claude-skills-collection/swift-modern-architecture-skill/skills/jackspace/claudeskillz/better-chatbot-patterns/skills/existential-birds/beagle/vercel-ai-sdk/skills/finos/morphir-dotnet/elm-to-fsharp-guru/skills/ascend-ai-coding/awesome-ascend-skills/torch_npu/skills/andurilcode/skills/theory-of-constraints/skills/amorriscode/agent-grimoire/code-review/orgs/tristanmanchester/orgs/harlan-zw/orgs/jaredstewart/orgs/szeyu/orgs/g1cloudNo persistent Lab drop was established. No Suspect or MissingMetric verdict arose in the judged suffixes. Older FCP onset remains undated where only the latest Poor pair was needed.
Excluded failed Scan:
075a50cd-0c8c-4650-9065-bf51a87a114a, basecamp mobile, September 25. Its null metrics were not treated as zeros.Poor lab dispositions
Homepage LCP: latest mobile values are 5101 and 5851 ms. Both name a demo image. Observed resource load delays are approximately 3598 and 4967 ms. These observed phases do not partition modeled LCP.
app/pages/_HomeDemoCarousel.vueshuffles the current demo duringonMounted. PR #576 explicitly requests a random starting order per visit. Changing that behavior requires Harlan’s decision about preserving variety without replacing the initial image after hydration. No proposal overrides that decision.Shared CSS and FCP: action
01M2J4SG3QK0095X6TVB0BP6T9names blocking entry and component stylesheets. PR #500 already restored inline component styles and recorded remaining homepage and Skill LCP cost. Current configuration retains that fix. Live homepage HTML still links entry, DemoWriting, and WhyVisual CSS.No distinct new CSS fix was established. Harlan owns remaining-cost triage. The other Poor pages share this evidence, so they receive no separate proposals. Several retained Skill and org Scans also measure missing-page content after redirects; their measurements do not establish a new route repair.
Fix follow-up and coverage limits
routine:vitals-reviewissues were returned. No routine-owned fix qualified for a post-deploy Scan.Public repository visibility was verified. Open issues, open PR bodies, matching closed issues, and relevant merged PRs were read. No matching open performance repair was found.
Site status is degraded because
health.crawlBlockerCountis unavailable. Its Next Action concerns indexing, outside this routine. Lighthouse versions vary across retained history, limiting causal comparisons.Repository and GitHub stayed read only. No NuxtSEO write was made.
Confidence: 88/100. Untested: local causal replay and field recovery after today’s deploy.
harlan-github-agent commentedon Nov 4, 2026
2026-11-04T01:00:00.000Z — vitals-review on skilld-dev/skilld.dev | 0 found | 0 new | 0 already known | 0 outside allowed scope | 0 over 5 files | 0 issues requested
s_08aae654,https://skilld.dev. Exactly matchedsites listagainst trackednuxt.config.ts→site.url.source: null, no field element data, andtotal: 0. This does not establish good performance.No proposals returned. Poor lab measurements exist, but current cause confirmation and duplicate checks remain incomplete.
Lab verdicts
Each cell lists LCP / FCP / TBT / CLS.
Shortmeans ShortSeries. Counts cover the contiguous latest Lighthouse release only.//gh/harlan-zw/nuxt-seo/orgs/tristanmanchester/orgs/g1cloud/orgs/harlan-zw/orgs/jaredstewart/orgs/szeyu/skills/jackspace/claudeskillz/better-chatbot-patterns/skills/existential-birds/beagle/vercel-ai-sdk/skills/basecamp/omarchy/omarchy/skills/fal3/claude-skills-collection/swift-modern-architecture-skill/skills/finos/morphir-dotnet/elm-to-fsharp-guru/skills/amorriscode/agent-grimoire/code-review/skills/andurilcode/skills/theory-of-constraints/skills/api/git/openclaw-multi-search-engine/skills/ascend-ai-coding/awesome-ascend-skills/torch_npu/skills/atemndobs/nebula-rfp/convex-patterns/skills/camera-2018/astrbot-plugin-dev-skill/astrbot-plugin-dev/skills/data-fair/lib/data-fair-ws/skills/dawiddutoit/custom-claude/test-property-basedNo Lab drop was established. The mobile TBT Suspect and desktop TBT Unstable series file nothing.
Version boundaries excluded older measurements for homepage mobile; both nuxt-seo strategies; mobile torch_npu, code-review and szeyu; desktop theory-of-constraints, omarchy, vercel-ai-sdk and tristanmanchester; and mobile better-chatbot-patterns. Single Scans after version changes prove neither persistence nor recovery.
FCP details establish the latest-pair verdicts above. Earlier FCP details were intentionally bounded for Poor series. They do not establish a complete FCP history or an earlier onset.
Skipped failed Scan:
075a50cd-0c8c-4650-9065-bf51a87a114a, mobile omarchy, 2026-09-25. Its null metrics were excluded.Poor measurements and disposition
Pairs below run from older to newer. Values are milliseconds.
/skills/jackspace/claudeskillz/better-chatbot-patterns/skills/basecamp/omarchy/omarchy/skills/fal3/claude-skills-collection/swift-modern-architecture-skill/skills/api/git/openclaw-multi-search-engine/orgs/tristanmanchesterThe four Skill pages map through legacy redirects to
/ghroutes andlayers/registry/app/components/SkillDetail.vue. Retired/orgsroutes map throughlayers/registry/server/utils/orgs-route-policy.tsto author profiles.Performance action
01M2J4SG3QK0095X6TVB0BP6T9identifies shared render-blocking CSS. Its producer evidence is aged, dated 2026-10-14. The detail response exposes 50 of 51 evidence items, with a continuation cursor.Scan details identify blocking entry CSS, SkillDetail CSS and DemoWriting CSS on the affected Skill pages.
SkillDetail.vuestatically imports_SkillDemo.vue, which imports_DemoWriting.vue. This provides a possible shared cause, but does not prove the change needed to remove the measured delay.Live read-only checks followed the api/git and omarchy redirects. Both responses still link three stylesheets. Their entry asset is now
entry.UM25vn7w.css, while the latest Poor Scans citeentry.CvwryD2V.css. Current configuration also contains the component-style build change from commit80d9b79c, PR #500. These observations do not establish current lab persistence or confirm a fix outcome.No page was selected as the highest-traffic representative of this shared cause. No separate proposals were created for its affected pages or metrics.
Ownership and fix follow-up
The controller supplied complete open issue and pull request lists. Most ownership bodies were complete. Issue #655 and PR #680 bodies were truncated.
For each of the five Poor page series above, the missing duplicate check is the complete body comparison against #655 and #680. Their visible dependency scope does not establish ownership of the CSS defect. It also does not justify claiming complete duplicate checks. No existing owner was positively matched.
Closed issue history was absent. Matching prior fixes, closing pull requests and their deployments could not be checked. Fix follow-up is incomplete. No fix was declared confirmed, failing or recurrent.
Next actor: controller, supply complete ownership bodies and closed routine history. A later review also needs current cause evidence before proposing a shared CSS fix.
All required Skills were present. Repository and GitHub access remained read only. No NuxtSEO mutation ran. Evidence is retained under
/home/agent/scratch/vitals-review/20261104T113600Z/.Confidence: 85/100. Current performance impact, complete duplicate checks and prior-fix deployment outcomes remain unverified.