CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ssr-hydration-scraping

Best practices for extracting data from modern React/Vue SSR pages (like Next.js or Nuxt.js) by targeting hydration state blocks (__NEXT_DATA__, __NUXT__) using regex and `jmespath`, avoiding brittle DOM selector scraping.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/ssr-hydration-scraping/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, code-first skill with executable extraction examples and a clear niche, held back by unvalidated parsing (no error handling around json.loads or match failures) and by prose that re-explains SSR/hydration concepts Claude already knows. The structure is sound for a single-file skill of this size.

Suggestions

Add explicit validation around the extraction flow — wrap json.loads in try/except, handle the no-match/empty target_list case, and present the steps as a numbered sequence with these checkpoints.

Trim the 症状 (Symptoms) and 根本原因 (Root Cause) sections to one or two lines each; the tactical value is already in the code and takeaways.

Show how to discover the right jmespath path for an unseen site (e.g., searching the serialized JSON for a known value) instead of only hardcoded candidate paths.

DimensionReasoningScore

Conciseness

The body spends sections explaining what Claude already knows — "现代前端框架...为了在客户端'注水'(Hydration)" (SSR/hydration basics) and a motivational symptom list ("停止在 DOM 树里捡垃圾") — while the actionable content is just the two code blocks. Mostly efficient but could be tightened; not 2 because there is no library tutorial padding and the takeaways carry real tactical value.

3 / 5

Actionability

Two concrete, near-complete Python code blocks: a working extract_ssr_data() regex extractor and a jmespath path-sniffing example with candidate paths. Not 5 because the second block relies on an undefined `html` variable and hardcodes illustrative paths without guidance on discovering them for a new site; not 3 because the guidance is genuinely executable rather than pseudocode.

4 / 5

Workflow Clarity

The sequence (locate SSR block → parse → jmespath sniff → iterate, with an XHR fallback in takeaway 3) is present but implicit in code order rather than explicitly sequenced, and there are no validation checkpoints — json.loads failures, missing matches, and empty target_list are unhandled. Not 4 because the error/fallback handling lives in prose takeaways rather than checkpoints in the flow.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent) and the body is a self-contained ~60-line document with clear section headers (症状/根本原因/解决方案/关键经验), which is appropriately structured at this size. Not 5 because the body slightly exceeds the under-50-lines simple-skill threshold, and the symptoms/root-cause prose could be trimmed or split if the skill grows.

4 / 5

Total

14

/

20

Passed

Description

75%Weight 40%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.

A specific, technically rich description with excellent distinctiveness, but it lacks any explicit "Use when..." trigger guidance, capping its completeness at 3. Adding a usage-trigger clause and a few natural synonyms (web scraping, crawl) would raise it substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use when scraping or crawling React/Vue SSR sites (Next.js, Nuxt) or when DOM selectors keep breaking on rendered pages."

Add natural user phrasings such as "web scraping", "crawling", and "scrape a React site" to broaden trigger term coverage.

Drop the generic "Best practices for" framing in favor of a direct third-person action verb ("Extracts data from...").

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with technical specifics: "extracting data from modern React/Vue SSR pages", "targeting hydration state blocks (__NEXT_DATA__, __NUXT__)", "using regex and jmespath", and "avoiding brittle DOM selector scraping" — comprehensive coverage of this skill's capabilities. Not 4 because coverage of the niche is essentially complete, including the extraction targets, tools, and the failure mode it prevents.

5 / 5

Completeness

The "what" is clearly and concretely answered, but there is no "Use when..." clause or equivalent explicit trigger guidance — per the judging guidelines this caps completeness at 3. Not 4 because the "when" is entirely missing rather than merely imprecise.

3 / 5

Trigger Term Quality

Good natural keyword coverage for the domain: "React/Vue SSR pages", "Next.js", "Nuxt.js", "hydration", "__NEXT_DATA__", "__NUXT__", "DOM selector scraping", "extracting data". Not 5 because common user phrasings like "web scraping", "scrape a React site", "crawling", or "hydration data" are absent or only implied.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — SSR hydration-state extraction from Next.js/Nuxt via __NEXT_DATA__/__NUXT__ — with distinct trigger identifiers, making conflict with other scraping skills minimal. Not 4 because the named globals and framework names are highly unlikely to appear in another skill's triggers.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Project-N-E-K-O/N.E.K.O

Path

.agent/skills/ssr-hydration-scraping/SKILL.md

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.