Sub-skill of solver-benchmark: Correlation Thresholds (+1).
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add vamseeachanta/workspace-hub --skill correlation-thresholds --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Correlation Thresholds?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-correlation-thresholds-workspace-hub)More formats (shields.io, HTML) on the badges page.
---
name: solver-benchmark-correlation-thresholds
description: 'Sub-skill of solver-benchmark: Correlation Thresholds (+1).'
version: 2.0.0
category: engineering-utilities
type: reference
scripts_exempt: true
---
# Correlation Thresholds (+1)
## Correlation Thresholds
| Range | Interpretation | Action |
|-------|---------------|--------|
| > 0.99 | Excellent agreement | Solvers validated |
| 0.95 – 0.99 | Good agreement | Minor differences (phase convention, numerics) |
| 0.80 – 0.95 | Fair agreement | Investigate input differences |
| < 0.80 | Poor agreement | Likely input mismatch or unit error |
| Negative | Anti-correlated | Data extraction bug (wrong frequency order, wrong units) |
## Common Causes of Poor Correlation
1. **Negative correlations**: Frequency arrays in different order (ascending vs descending)
2. **Near-zero correlations**: Hz vs rad/s mismatch (factor of 2*pi offset)
3. **NaN correlations**: Zero standard deviation (all-zero DOF, e.g. yaw for head seas)
4. **Good amplitude, bad phase**: Different time convention (e^{+iwt} vs e^{-iwt})
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
