# Send Vibration Analysis to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "vibration-analysis", "name": "Vibration Analysis", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/Sertug17/vibration-analysis", "canonicalUrl": "https://clawhub.ai/Sertug17/vibration-analysis", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/vibration-analysis", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=vibration-analysis", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "vibration-analysis", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-01T14:38:50.802Z", "expiresAt": "2026-05-08T14:38:50.802Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=vibration-analysis", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=vibration-analysis", "contentDisposition": "attachment; filename=\"vibration-analysis-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "vibration-analysis" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/vibration-analysis" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/vibration-analysis", "downloadUrl": "https://openagent3.xyz/downloads/vibration-analysis", "agentUrl": "https://openagent3.xyz/skills/vibration-analysis/agent", "manifestUrl": "https://openagent3.xyz/skills/vibration-analysis/agent.json", "briefUrl": "https://openagent3.xyz/skills/vibration-analysis/agent.md" } } ``` ## Documentation ### Wind Turbine Drivetrain Vibration Analysis Evaluates drivetrain vibration health across three subsystems: main bearing, gearbox, and generator. ### When to Use Load this skill when the user wants to: Assess drivetrain vibration health from CMS or SCADA data Interpret RMS, peak-to-peak, or spectral findings for main bearing, gearbox, or generator Correlate vibration alarms with operational events Decide whether to continue operating, increase monitoring, or shut down ### Drivetrain Components ComponentSensor LocationKey FrequenciesMain BearingNon-drive end, drive endBPFO, BPFI, BSF, FTFGearbox LSSLow speed shaftGear mesh (LSS x teeth), bearing defect freqsGearbox IMSIntermediate shaftIMS gear mesh harmonicsGearbox HSSHigh speed shaftHSS gear mesh, bearing defect freqsGenerator NDENon-drive end bearingElectrical harmonics, bearing defect freqsGenerator DEDrive end bearingBearing defect freqs, rotor unbalance ### Vibration Thresholds (ISO 10816 / CMS Reference) LocationNormalWarningCriticalMain Bearing RMS (g)< 0.30.3 - 0.8> 0.8Gearbox HSS RMS (g)< 0.50.5 - 1.5> 1.5Gearbox LSS/IMS RMS (g)< 0.30.3 - 1.0> 1.0Generator RMS (g)< 0.50.5 - 1.2> 1.2Peak-to-peak step change< 10%10-30%> 30% Note: Always evaluate against site-specific baseline. A 20% rise from stable baseline is more significant than an absolute value alone. ### Frequency Fault Signatures FaultFrequency SignatureBearing outer race (BPFO)(N/2) x (1 - d/D x cos a) x RPMBearing inner race (BPFI)(N/2) x (1 + d/D x cos a) x RPMGear meshnumber of teeth x shaft RPMGear mesh sidebandsGMF +/- shaft frequencyRotor unbalance1x RPM dominantMisalignment2x RPM dominant, axial componentLoosenessSub-harmonics (0.5x, 1.5x) or high harmonic content ### Severity Scale SeverityLabelDescriptionAction1HealthyAll values normal, stable trendContinue normal operation2Early warning1-2 parameters in warning zone, stableIncrease CMS polling frequency3ModerateMultiple warning flags or single criticalInspect within 2 weeks4SignificantCritical zone or rapid trend growthPlan shutdown within 48-72 hours5CriticalMultiple critical flags, step-changeImmediate shutdown required ### Procedure Collect inputs: CMS trend (last 30-90 days), current RMS and peak-to-peak per component, frequency spectrum findings, SCADA alarms, operational context. Evaluate RMS values against thresholds. Flag Warning or Critical zones. Analyze trend: Stable: value in warning zone but flat for >30 days = lower urgency Gradual rise: value increasing steadily = schedule inspection Step change: sudden jump >30% = treat as Critical regardless of absolute value Interpret frequency spectrum if available: Match dominant peaks to fault signatures table Note sidebands around gear mesh frequencies Note sub-harmonics or 1x/2x dominance Correlate with SCADA alarms and operational events. Assign severity per component, then determine drivetrain-level severity as highest. Generate output report using the format below. ### Output Format === DRIVETRAIN VIBRATION REPORT === ASSET : [Turbine ID] SITE : [Site name] DATA PERIOD : [Date range of CMS/SCADA data] MISSING DATA : [List any unavailable inputs] MAIN BEARING: RMS : [value] g - [Normal / Warning / Critical] Trend : [Stable / Gradual rise / Step change] Spectrum : [Key findings or not available] SCADA Alarms : [Count and type] Severity : [1-5] - [Label] GEARBOX (LSS / IMS / HSS): RMS : LSS [value] g / IMS [value] g / HSS [value] g Trend : [per shaft] Spectrum : [Key findings] SCADA Alarms : [Count and type] Severity : [1-5] - [Label] GENERATOR (DE / NDE): RMS : DE [value] g / NDE [value] g Trend : [per bearing] Spectrum : [Key findings] SCADA Alarms : [Count and type] Severity : [1-5] - [Label] DRIVETRAIN SEVERITY : [1-5] - [Label] SHUTDOWN : [Yes / No / Conditional] FAULT HYPOTHESIS: [e.g., HSS bearing outer race defect - BPFO peak confirmed at X Hz] [e.g., Gear mesh sideband modulation - possible gear wear or load variation] RECOMMENDED ACTIONS: [e.g., Increase CMS polling to daily for HSS channel] [e.g., Oil sample with ferrography within 72 hours] [e.g., Plan HSS bearing replacement at next scheduled outage] ESCALATION TRIGGERS: [e.g., RMS exceeds 1.5 g on HSS - immediate shutdown] [e.g., Step change >30% on any channel - treat as critical] [e.g., New BPFO or BPFI peak confirmed in spectrum - escalate to Severity 4] ### Cross-Skill Correlation If gearbox visual data is available, load wind-turbine-gearbox skill and cross-correlate: High Fe ppm + rising HSS vibration = active wear confirmation Spalling in borescope + BPFO peak in spectrum = bearing failure progression Normal oil + rising vibration = early fault not yet generating debris (higher urgency) If blade inspection data is available, check for rotor imbalance: 1x RPM dominant in main bearing spectrum + blade damage = aerodynamic imbalance Asymmetric blade damage across A/B/C = mass or aerodynamic imbalance source ### Pitfalls Do not evaluate vibration in isolation. Cross-reference with oil analysis and visual inspection. A single high RMS reading during a storm or grid fault is not a fault indicator. Check operational context. Spectrum analysis requires RPM-normalized data. Raw frequency peaks are meaningless without shaft RPM. Generator electrical faults can appear as vibration. Check electrical data before attributing to mechanical cause. Stable high RMS is less urgent than rapidly rising moderate RMS. Trend rate matters more than absolute value. ### Verification After generating the report, confirm with the user: Does the severity match CMS system alerts or OEM recommendations? Is shaft RPM data available to normalize spectrum frequencies? Are there recent maintenance events that could explain vibration changes? Is SCADA power curve deviation consistent with vibration findings? ## Trust - Source: tencent - Verification: Indexed source record - Publisher: Sertug17 - Version: 1.0.0 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-05-01T14:38:50.802Z - Expires at: 2026-05-08T14:38:50.802Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/vibration-analysis) - [Send to Agent page](https://openagent3.xyz/skills/vibration-analysis/agent) - [JSON manifest](https://openagent3.xyz/skills/vibration-analysis/agent.json) - [Markdown brief](https://openagent3.xyz/skills/vibration-analysis/agent.md) - [Download page](https://openagent3.xyz/downloads/vibration-analysis)