[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVQR3910QHNBPDHC3PSDQS":3,"skill-same:01M7EVQR3910QHNBPDHC3PSDQS":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EVQR3910QHNBPDHC3PSDQS","renewable-resource-assessment",null,"Assessing wind, solar, and hydro resources — measurement, modeling, uncertainty, and bankable energy-yield estimates.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-renewable-resource-assessment\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: renewable-resource-assessment\ndescription: Assessing wind, solar, and hydro resources — measurement, modeling, uncertainty, and bankable energy-yield estimates.\ncategory: scientific\n---\n\n## Overview\n\nA renewable energy project lives or dies on the resource assessment: how\nmuch wind, sun, or water the site actually gets. This skill covers\nmeasurement campaigns (met masts, lidar, pyranometers), long-term\ncorrection with reanalysis (MCP), energy-yield modeling, and the\nuncertainty accounting that makes a yield estimate bankable.\n\n## When to use\n\n- Siting a wind or solar farm: screening sites and designing the measurement campaign\n- Converting a year of site data into a long-term (P50\u002FP90) energy-yield estimate\n- Reviewing a resource assessment report for financing or acquisition\n- Estimating rooftop or distributed solar potential for a region\n- Assessing hydro resource variability and climate-change exposure\n\n## Core concepts\n\n- **Wind:** power ∝ v³ — small wind-speed errors become large energy errors; the Weibull distribution describes the speed frequency; shear (power law or log law) extrapolates mast height to hub height; turbulence intensity affects loads and production.\n- **Solar:** GHI (global horizontal), DNI (direct normal), DHI (diffuse); plane-of-array irradiance via transposition models; temperature derates PV output (~−0.35%\u002F°C for silicon); soiling and shading are site-specific losses.\n- **MCP (measure–correlate–predict):** correlate short site measurements with long-term reference data (ERA5, MERRA-2) to estimate the long-term climate — the standard fix for interannual variability.\n- **P50\u002FP90:** P50 is the median expected yield; P90 the conservative value exceeded 90% of the time — lenders size debt on P90; the P50–P90 gap measures total uncertainty.\n- **Loss stack:** availability, wake effects, electrical losses, soiling, curtailment, degradation — each small, together 10–20%; itemize rather than applying a single fudge factor.\n- **Hydro:** flow-duration curves from gauged records; firm vs secondary energy; sedimentation reduces storage; climate shifts alter both means and extremes.\n\n- **Shear extrapolation risk:** the power-law\u002Flog-law extrapolation from measurement height to hub height is a leading uncertainty source — measure as close to hub height as possible; lidar makes this cheap now.\n- **Interannual variability vs climate change:** 10–20 years of reference data captures variability; the climate-change signal in wind\u002Fsolar resources is smaller but non-zero — check trends in the reference period before assuming stationarity.\n- **Curtailment and grid constraints:** the resource at the site is not the energy delivered — grid capacity, curtailment risk, and offtake terms belong in the yield assessment, not just the financial model.\n\n## Practical workflow\n\n### 1. Measure the resource\n\n1. **Wind:** met mast or lidar at\u002Fnear hub height, ≥12 months; calibrate anemometers; measure shear with multiple heights and direction with vanes.\n2. **Solar:** secondary-standard pyranometers (GHI + DHI) or reference cells, cleaned and calibrated; ≥12 months; log soiling with a paired clean\u002Fdirty sensor if dust is suspected.\n3. Document everything: sensor models, calibration certificates, heights, boom orientation, data recovery rate (>90% target).\n\n### 2. Build the long-term estimate\n\n1. Select reference data (ERA5\u002FMERRA-2 nodes, nearby long-term stations); validate correlation with concurrent site data (R², bias by direction\u002Fseason).\n2. Apply MCP to synthesize a long-term (10–30 year) site time series; check that the reference period is climatologically representative.\n3. For wind, fit the long-term speed distribution and compute gross energy from the turbine power curve; for solar, transpose to plane-of-array and apply the temperature model.\n\n### 3. Model energy yield and losses\n\n1. **Wind:** wake modeling (analytical or CFD-lite), availability (typically 97–98%), electrical losses, curtailment, icing if relevant.\n2. **Solar:** shading analysis, inverter clipping, mismatch, soiling, degradation (~0.5%\u002Fyr), availability.\n3. Present gross → net with each loss itemized; never bury losses in a single \"derate.\"\n\n### 4. Quantify uncertainty (the bankable part)\n\n1. List uncertainty components: measurement, MCP\u002Freference, interannual variability, model\u002Fwake, losses — combine in quadrature (root-sum-square) with stated distributions.\n2. Report P50, P75, P90 (and P99 for stress tests); show which components dominate — that tells you what extra measurement would buy.\n3. Sensitivity-test key assumptions (shear exponent, soiling rate, degradation) — lenders will ask.\n\n### 5. Audit a resource assessment report\n\n1. Check the measurement: duration (≥12 months?), heights, calibration certificates, data recovery rate — no measurement, no bankability.\n2. Check the MCP: reference dataset choice, correlation quality (R², directional\u002Fseasonal bias), reference-period representativeness.\n3. Check the uncertainty: itemized components combined properly, P90 derived not guessed, and loss stack itemized rather than lumped — then verify the P50 against independent data if any exists.\n\n### 6. Quick-reference checklist\n\n- [ ] ≥12 months of site measurement at\u002Fnear hub height (wind) or with calibrated pyranometers (solar)\n- [ ] Sensor calibrations current with certificates on file\n- [ ] Data recovery rate >90% with gaps documented\n- [ ] MCP performed against a validated long-term reference\n- [ ] Shear extrapolation minimized (measure high; lidar preferred)\n- [ ] Loss stack itemized (wakes, availability, electrical, soiling, curtailment, degradation)\n- [ ] Uncertainty components combined properly; P50\u002FP90\u002FP99 reported\n- [ ] Key assumptions sensitivity-tested (shear, soiling, degradation)\n\n## Common pitfalls\n\n- **One windy year extrapolated forever:** interannual variability is ±10% or more — MCP correction is mandatory, not optional.\n- **v³ amplification:** a 5% wind-speed bias is a ~15% energy bias — calibrate anemometers and scrutinize shear extrapolation.\n- **Ignoring wakes and blockage:** gross turbine yield ≠ farm yield; array effects cost 5–15%.\n- **Soiling and shading hand-waving:** in dusty or built environments these dominate uncertainty — measure, don't assume.\n- **Degradation optimism:** PV warranties promise ≤0.5%\u002Fyr; actuals vary — use measured fleet data where available.\n- **Climate non-stationarity:** 30-year historical normals may misstate the next 30 years for hydro and, increasingly, wind\u002Fsolar regimes — check trends.\n- **Vendor power curves as truth:** manufacturer power curves are measured under ideal conditions — apply realistic turbulence, shear, and availability derates; validate against operational fleet data.\n- **Soiling assumed zero:** in arid and agricultural regions soiling losses of 5–20% are normal — a zero-soiling assumption needs site-specific justification, not optimism.\n","## Overview\n\nA renewable energy project lives or dies on the resource assessment: how\nmuch wind, sun, or water the site actually gets. This skill covers\nmeasurement campaigns (met masts, lidar, pyranometers), long-term\ncorrection with reanalysis (MCP), energy-yield modeling, and the\nuncertainty accounting that makes a yield estimate bankable.\n\n## When to use\n\n- Siting a wind or solar farm: screening sites and designing the measurement campaign\n- Converting a year of site data into a long-term (P50\u002FP90) energy-yield estimate\n- Reviewing a resource assessment report for financing or acquisition\n- Estimating rooftop or distributed solar potential for a region\n- Assessing hydro resource variability and climate-change exposure\n\n## Core concepts\n\n- **Wind:** power ∝ v³ — small wind-speed errors become large energy errors; the Weibull distribution describes the speed frequency; shear (power law or log law) extrapolates mast height to hub height; turbulence intensity affects loads and production.\n- **Solar:** GHI (global horizontal), DNI (direct normal), DHI (diffuse); plane-of-array irradiance via transposition models; temperature derates PV output (~−0.35%\u002F°C for silicon); soiling and shading are site-specific losses.\n- **MCP (measure–correlate–predict):** correlate short site measurements with long-term reference data (ERA5, MERRA-2) to estimate the long-term climate — the standard fix for interannual variability.\n- **P50\u002FP90:** P50 is the median expected yield; P90 the conservative value exceeded 90% of the time — lenders size debt on P90; the P50–P90 gap measures total uncertainty.\n- **Loss stack:** availability, wake effects, electrical losses, soiling, curtailment, degradation — each small, together 10–20%; itemize rather than applying a single fudge factor.\n- **Hydro:** flow-duration curves from gauged records; firm vs secondary energy; sedimentation reduces storage; climate shifts alter both means and extremes.\n\n- **Shear extrapolation risk:** the power-law\u002Flog-law extrapolation from measurement height to hub height is a leading uncertainty source — measure as close to hub height as possible; lidar makes this cheap now.\n- **Interannual variability vs climate change:** 10–20 years of reference data captures variability; the climate-change signal in wind\u002Fsolar resources is smaller but non-zero — check trends in the reference period before assuming stationarity.\n- **Curtailment and grid constraints:** the resource at the site is not the energy delivered — grid capacity, curtailment risk, and offtake terms belong in the yield assessment, not just the financial model.\n\n## Practical workflow\n\n### 1. Measure the resource\n\n1. **Wind:** met mast or lidar at\u002Fnear hub height, ≥12 months; calibrate anemometers; measure shear with multiple heights and direction with vanes.\n2. **Solar:** secondary-standard pyranometers (GHI + DHI) or reference cells, cleaned and calibrated; ≥12 months; log soiling with a paired clean\u002Fdirty sensor if dust is suspected.\n3. Document everything: sensor models, calibration certificates, heights, boom orientation, data recovery rate (>90% target).\n\n### 2. Build the long-term estimate\n\n1. Select reference data (ERA5\u002FMERRA-2 nodes, nearby long-term stations); validate correlation with concurrent site data (R², bias by direction\u002Fseason).\n2. Apply MCP to synthesize a long-term (10–30 year) site time series; check that the reference period is climatologically representative.\n3. For wind, fit the long-term speed distribution and compute gross energy from the turbine power curve; for solar, transpose to plane-of-array and apply the temperature model.\n\n### 3. Model energy yield and losses\n\n1. **Wind:** wake modeling (analytical or CFD-lite), availability (typically 97–98%), electrical losses, curtailment, icing if relevant.\n2. **Solar:** shading analysis, inverter clipping, mismatch, soiling, degradation (~0.5%\u002Fyr), availability.\n3. Present gross → net with each loss itemized; never bury losses in a single \"derate.\"\n\n### 4. Quantify uncertainty (the bankable part)\n\n1. List uncertainty components: measurement, MCP\u002Freference, interannual variability, model\u002Fwake, losses — combine in quadrature (root-sum-square) with stated distributions.\n2. Report P50, P75, P90 (and P99 for stress tests); show which components dominate — that tells you what extra measurement would buy.\n3. Sensitivity-test key assumptions (shear exponent, soiling rate, degradation) — lenders will ask.\n\n### 5. Audit a resource assessment report\n\n1. Check the measurement: duration (≥12 months?), heights, calibration certificates, data recovery rate — no measurement, no bankability.\n2. Check the MCP: reference dataset choice, correlation quality (R², directional\u002Fseasonal bias), reference-period representativeness.\n3. Check the uncertainty: itemized components combined properly, P90 derived not guessed, and loss stack itemized rather than lumped — then verify the P50 against independent data if any exists.\n\n### 6. Quick-reference checklist\n\n- [ ] ≥12 months of site measurement at\u002Fnear hub height (wind) or with calibrated pyranometers (solar)\n- [ ] Sensor calibrations current with certificates on file\n- [ ] Data recovery rate >90% with gaps documented\n- [ ] MCP performed against a validated long-term reference\n- [ ] Shear extrapolation minimized (measure high; lidar preferred)\n- [ ] Loss stack itemized (wakes, availability, electrical, soiling, curtailment, degradation)\n- [ ] Uncertainty components combined properly; P50\u002FP90\u002FP99 reported\n- [ ] Key assumptions sensitivity-tested (shear, soiling, degradation)\n\n## Common pitfalls\n\n- **One windy year extrapolated forever:** interannual variability is ±10% or more — MCP correction is mandatory, not optional.\n- **v³ amplification:** a 5% wind-speed bias is a ~15% energy bias — calibrate anemometers and scrutinize shear extrapolation.\n- **Ignoring wakes and blockage:** gross turbine yield ≠ farm yield; array effects cost 5–15%.\n- **Soiling and shading hand-waving:** in dusty or built environments these dominate uncertainty — measure, don't assume.\n- **Degradation optimism:** PV warranties promise ≤0.5%\u002Fyr; actuals vary — use measured fleet data where available.\n- **Climate non-stationarity:** 30-year historical normals may misstate the next 30 years for hydro and, increasingly, wind\u002Fsolar regimes — check trends.\n- **Vendor power curves as truth:** manufacturer power curves are measured under ideal conditions — apply realistic turbulence, shear, and availability derates; validate against operational fleet data.\n- **Soiling assumed zero:** in arid and agricultural regions soiling losses of 5–20% are normal — a zero-soiling assumption needs site-specific justification, not optimism.\n",{"name":5,"category":24,"description":7},"scientific","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-renewable-resource-assessment",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill renewable-resource-assessment",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill renewable-resource-assessment",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill renewable-resource-assessment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-renewable-resource-assessment\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]