← Back to Skills Marketplace
sertug17

Blade Inspection

by Sertug17 · GitHub ↗ · v1.0.0
cross-platform ✓ Security Clean
348
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install blade-inspection
Description
Assesses wind turbine blade condition from visual inspection data. Classifies damage type and severity (1-5) across seven failure modes and recommends repair...
README (SKILL.md)

Wind Turbine Blade Inspection Intelligence

Evaluates blade condition from drone or ground-based visual inspection and produces a structured damage assessment across seven failure modes.

When to Use

Load this skill when the user wants to:

  • Assess blade health from drone inspection images or written findings
  • Classify damage type and severity on a 1-5 scale per blade and per zone
  • Determine whether a turbine should continue operating, be scheduled for repair, or shut down
  • Generate a structured blade inspection report with repair recommendations

Blade Zones

Zone Span Description
Root 0-33% Highest structural loads, bolted connection area
Mid 33-66% Transition zone, moderate aerodynamic load
Tip 66-100% Highest velocity, most erosion-prone, lightning receptor area

Surfaces: Leading Edge (LE), Trailing Edge (TE), Suction Side (SS), Pressure Side (PS)

Damage Type Definitions

Damage Type Description Typical Location
Surface crack Gelcoat or laminate cracks, linear fractures LE, TE, root transition
Erosion / wear Material loss, pitting, roughening LE tip zone
Lightning damage Burn marks, punctures, receptor damage Tip, receptor area
Lamination/structural Delamination, fiber exposure, buckling, dents Any zone
Debonding Bond line separation at LE, TE, or shear web LE, TE, internal
Ice accumulation Ice buildup on surface or edges Any zone
General visual anomaly Discoloration, contamination, coating loss Any zone

Severity Scale

Severity Label Description Action
1 Healthy No damage or cosmetic marks only Continue normal operation
2 Minor Early erosion, superficial cracks, coating loss Increase inspection frequency
3 Moderate Gelcoat breach, early debonding, defined damage Repair within 1-3 months
4 Significant Structural involvement, active debonding, lightning Repair within 2-4 weeks
5 Critical Fiber exposure, structural breach, delamination Immediate shutdown required

Procedure

  1. Collect inputs: blade IDs, inspection method, findings per blade per zone per surface.
  2. Classify each finding by damage type.
  3. Assign severity per finding using the severity scale.
  4. Determine overall blade severity as the highest finding for that blade.
  5. Determine turbine-level severity as the highest across all blades.
  6. Apply damage-specific rules:
    • Lightning damage: minimum Severity 4 until OEM confirms otherwise.
    • Debonding at LE or TE over 300 mm: escalate to Severity 4.
    • Any confirmed fiber exposure: minimum Severity 4.
    • Erosion with full gelcoat loss over 500 mm span at tip: Severity 4.
    • Active ice accumulation: always Severity 4.
  7. Generate output report using the format below.

Output Format

=== BLADE INSPECTION REPORT ===

ASSET : [Turbine ID] SITE : [Site name] INSPECTION : [Date / Method] BLADES : [Number inspected]

BLADE [ID]: Zone/Surface : [e.g., Tip / Leading Edge] Damage Type : [e.g., Erosion] Description : [e.g., Deep pitting ~600 mm span, gelcoat fully lost] Severity : [1-5] - [Label]

BLADE [ID] OVERALL SEVERITY: [1-5] - [Label]

TURBINE-LEVEL SEVERITY : [1-5] - [Label] SHUTDOWN RECOMMENDATION: [Yes / No / Conditional]

REPAIR PRIORITY:

  • [e.g., Blade 2 tip LE erosion - schedule LEP repair within 6 weeks]

MONITORING STRATEGY:

  • [e.g., Monthly drone re-inspection for all blades]

ESCALATION TRIGGERS:

  • [e.g., Debond length exceeds 500 mm - shutdown for repair]
  • [e.g., SCADA vibration or imbalance alarms - ground turbine]

Damage-Specific Guidance

Erosion: Progresses from roughening to pitting to gelcoat loss to fiber exposure. Repair with Leading Edge Protection (LEP) tape or coating. Severity 3-4 causes measurable energy production loss.

Lightning: Always notify OEM. Minor visible damage may hide internal delamination. Do not assume safe to operate until specialist confirms.

Debonding: LE debonding causes aerodynamic noise and vibration. TE debonding starts at tip and progresses toward root. Bond line gap over 300 mm is Severity 4.

Lamination/Structural: Fiber exposure is always Severity 4 minimum. Dents or buckling without fiber exposure is Severity 3.

Ice: Active ice requires immediate grounding due to rotor imbalance and ice throw risk. After melting, inspect surface for underlying damage.

Pitfalls

  • Do not classify erosion from low-resolution images. Ask for close-up zone-specific photos.
  • Lightning damage is always higher priority than it looks. Treat as Severity 4 until proven otherwise.
  • Debonding can be invisible from drone imagery. If SCADA shows imbalance alarms, flag potential hidden debonding.
  • Active ice is a safety hazard. Recommend immediate grounding.
  • Assess each blade independently. Damage distribution is rarely uniform across all three blades.

Verification

After generating the report, confirm with the user:

  • Does the severity match the inspector's on-site assessment?
  • Are all three blades accounted for?
  • Are there SCADA alarms (vibration, imbalance, power curve deviation) correlating with findings?
  • Is there a previous inspection report for trend comparison?
Usage Guidance
This skill appears coherent and low-risk, but before using it: (1) provide high-resolution, zone-specific photos and any SCADA event summaries yourself — do not hand over credentials or feeds unless you intend to; (2) treat shutdown or safety recommendations as advisory and confirm with an on-site engineer or OEM specialist before acting; (3) verify any OEM-specific escalation rules or measurement thresholds your organization requires; (4) if you plan to let an agent access SCADA or other operational systems automatically, review that integration separately because the SKILL.md assumes contextual inputs but does not itself implement secure system access.
Capability Analysis
Type: OpenClaw Skill Name: blade-inspection Version: 1.0.0 The skill bundle provides detailed instructions for an AI agent to assess wind turbine blade conditions and generate a structured report. All instructions in `SKILL.md` are domain-specific, focusing on data processing, classification, and report generation, with no evidence of prompt injection attempts, data exfiltration, arbitrary command execution, or other malicious behaviors. The content is entirely aligned with its stated purpose.
Capability Assessment
Purpose & Capability
Name/description match the content of SKILL.md: it focuses on classifying visual damage types and severities and producing a structured report. The skill declares no binaries, installs, or credentials — all consistent with an instruction-only inspection/reporting helper.
Instruction Scope
The instructions stay within blade inspection scope (classify images/findings, apply rules, generate report). They reference external operational data (SCADA vibration/imbalance alarms) and expect high-resolution or zone-specific photos; this is reasonable but implies the user must supply that contextual data. The SKILL.md does not instruct reading system files or automatically fetching SCADA data, which would be out-of-scope — clarify whether the agent will be given SCADA feeds or only user-provided summaries.
Install Mechanism
No install spec and no code files (instruction-only). This minimizes on-disk execution or third-party downloads and is proportionate for a procedural/reporting skill.
Credentials
The skill does not request environment variables or credentials. It mentions OEM contact and SCADA signals as contextual inputs but does not ask for secret keys or system access — appropriate for the stated purpose.
Persistence & Privilege
always is false and the skill does not request persistent system privileges. Autonomous invocation is allowed by platform default but the skill does not request elevated persistence or modify other skills.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install blade-inspection
  3. After installation, invoke the skill by name or use /blade-inspection
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of wind-turbine-blade-inspection skill. - Classifies visual inspection findings into seven damage types across defined blade zones and surfaces. - Assigns severity (1–5) to each finding, with clear action recommendations. - Provides structured inspection reports with operational, repair, and monitoring guidance. - Includes strict rules for escalation (e.g., lightning, large debonds, fiber exposure, ice). - Designed for both drone and ground-based inspection data inputs.
Metadata
Slug blade-inspection
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Blade Inspection?

Assesses wind turbine blade condition from visual inspection data. Classifies damage type and severity (1-5) across seven failure modes and recommends repair... It is an AI Agent Skill for Claude Code / OpenClaw, with 348 downloads so far.

How do I install Blade Inspection?

Run "/install blade-inspection" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Blade Inspection free?

Yes, Blade Inspection is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Blade Inspection support?

Blade Inspection is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Blade Inspection?

It is built and maintained by Sertug17 (@sertug17); the current version is v1.0.0.

💬 Comments