Sub-skill of fe-analyst: Plot Types Per Section.
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add vamseeachanta/workspace-hub --skill plot-types-per-section --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Plot Types Per Section?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-plot-types-per-section-workspace-hub)More formats (shields.io, HTML) on the badges page.
---
name: fe-analyst-plot-types-per-section
description: 'Sub-skill of fe-analyst: Plot Types Per Section.'
version: 1.0.0
category: engineering
type: reference
scripts_exempt: true
---
# Plot Types Per Section
## Plot Types Per Section
| Section | Plot Type | Plotly Trace |
|---|---|---|
| Geometry | 3D line profile (x,y,z) | `go.Scatter3d` |
| Geometry | 2D vertical profile (arc length vs. z) | `go.Scatter` |
| Mesh | Segment length distribution | `go.Bar` |
| Mesh | Adjacent ratio heatmap along arc | `go.Scatter` with color |
| Materials | Section property table | `go.Table` |
| BC | 3D model with BC markers | `go.Scatter3d` + annotations |
| Results | Time history (Te, M, z) | `go.Scatter` (time on x) |
| Results | Envelope (max/min vs. arc length) | `go.Scatter` with fill |
| Results | Statistical summary table | `go.Table` |
| Design Checks | Utilization bar chart | `go.Bar` with threshold line |
| Fatigue | Damage vs. arc length | `go.Scatter` |
---
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?".
