Spinal Pro

End-to-end SpinalHDL skill for generating, reviewing, explaining, and validating RTL (Scala HDL). Covers DSL semantics (`:=`, `<>`, `Reg`, `Stream`, `Flow`, `Bundle`, `Vec`, `ClockDomain`, `StateMachine`, `Mem`, `BusSlaveFactory`), pipeline and plugin composition (`spinal.lib.misc.pipeline`, `spinal.lib.misc.plugin`), simulation with `SimConfig`/`doSim`, and architecture patterns drawn from official SpinalHDL docs and VexRiscv. Load for SpinalHDL DSL questions, module implementation, interface design, SoC integration, bug hunting, error-message decoding, and simulation or build validation.

9 stars 1 forksSecurity

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add Zeeh-Lin/spinal-pro --skill spinal-pro

Manual install

git clone --depth 1 https://github.com/Zeeh-Lin/spinal-pro.git /tmp/spinal-pro
mkdir -p ~/.claude/skills
cp -r /tmp/spinal-pro/. ~/.claude/skills/spinal-pro

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Spinal Pro

Target SpinalHDL version: 1.10+ (rules and APIs validated against the
`master` branch of SpinalDoc-RTD).

## When To Use

Load this skill when the task involves:

- writing or modifying SpinalHDL RTL
- reviewing SpinalHDL for semantic bugs, interface bugs, timing-risky
  structure, or maintainability issues
- explaining SpinalHDL DSL behavior (`:=`, `\=`, `<>`, `when`, `switch`,
  `ClockDomain`, `Stream`, `Flow`, `Bundle`, `Vec`, `StateMachine`, `Mem`)
- decoding SpinalHDL elaboration errors (`WIDTH MISMATCH`, `LATCH
  DETECTED`, `CLOCK CROSSING VIOLATION`, …)
- designing parameterized blocks, buses, peripherals, plugin-oriented
  components, or CPU/SoC structure
- validating SpinalHDL work through `SimConfig` / `doSim`, focused
  simulation, or repo-native tests
- using VexRiscv as a pattern source for larger architecture decisions

## Do Not Use

Do not load this skill for tasks that are purely about general Scala,
vendor EDA flows, RTL in non-SpinalHDL languages, or unrelated hardware
topics — unless SpinalHDL semantics or SpinalHDL code is central to the
task.

## Workflow

1. **Identify the task type**: generate, modify, review, explain,
   retrieve, or design.
2. **Open the relevant references** for the task type (see table below).
3. **Inspect the local repository** *if* the task touches code:
   target file(s), build entry points, tests, generators, simulation
   hooks, and nearby conventions. Skip this step for pure
   explanation/retrieval tasks.

Read the full skill on GitHub

Details

Skill name: spinal-pro
Repository: Zeeh-Lin/spinal-pro
License: MIT
Repo updated: 20 May 2026

FAQ

What does the Spinal Pro skill do?

How do I install the Spinal Pro skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Zeeh-Lin/spinal-pro --skill spinal-pro. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Spinal Pro popular?

It lives in Zeeh-Lin/spinal-pro, which has 9 GitHub stars and 1 forks.

Related skills

Oma Lwm2m Expert

svdwalt007/Best-LwM2M-Agentic-Skills

OMA LwM2M expert: specs v1.0–v1.2.2 plus v2.0 roadmap, object/resource data model, transports, security, ecosystem. Trigger on: LwM2M, Lightweight M2M, OMA SpecWorks, OMNA registry, OMA-TS-LightweightM2M, CoAP (RFC 7252/7641/7959/8323), DTLS, DTLS CID (RFC 9146), DTLS 1.3, RRC (RFC 9853), OSCORE (RFC 8613), PSK, RPK, X.509, EST, SNI, NoSec, TLV, SenML JSON/CBOR, LwM2M CBOR, bootstrap, Bootstrap-Pack, registration, endpoint name, Profile ID, Queue Mode, bindings (UDP/TCP/SMS/Non-IP/LoRaWAN/MQTT/HTTP/ WebSockets), Read/Write/Execute/Discover, composite operations, Send, observe/notify, notificat

Security

Skill Security Reviewer

oguzhantopgul/skill-security-reviewer

Security review and threat analysis for agent skills. Use when reviewing, auditing, or validating skills for security issues including prompt injection, code execution risks, data exfiltration, supply chain vulnerabilities, and policy violations. Triggers on requests to "review a skill", "audit skill security", "check skill for vulnerabilities", "validate skill safety", or any security assessment of SKILL.md files and their associated scripts/assets.

Security

Security Review

Dilaz/security-review-skill

Use when performing security audits, vulnerability assessments, penetration testing, or when asked to find security issues. Use when encountering code that handles user input, executes commands, reads files, or makes network requests.

Security

SAAS Security

vitormiziara/saas-security

Comprehensive SaaS security skill covering code auditing, checklist generation, and vulnerability reporting. TRIGGER this skill whenever the user asks to: audit code for security issues, review a codebase for vulnerabilities, generate a security checklist, check for OWASP compliance, review authentication or authorization logic, check for injection risks, race conditions, or insecure configurations, or asks anything related to SaaS security hardening. Also trigger proactively when the user shares code and asks for a review — always include a security perspective using this skill.

Security

Solidity Security Audit

mariano-aguero/solidity-security-audit-skill

Comprehensive Solidity smart contract security auditing and vulnerability analysis skill. Based on methodologies from Trail of Bits, OpenZeppelin, Consensys Diligence, Sherlock, CertiK, Cyfrin, Spearbit, Halborn, and other leading Web3 security firms. This skill should be used whenever the user asks to "audit a smart contract", "review Solidity code for security", "find vulnerabilities", "check for reentrancy", "analyze gas optimization", "review access control", "check proxy patterns", "analyze DeFi protocol security", "review ERC20/ERC721 implementation", "check oracle manipulation risks", "

Security

Repo Seed

EricSanchezok/repo-seed

Seed, audit, adopt, and progressively evolve an agent-native repository with risk-triggered specs, durable decisions, resident governance skills, capability state, deterministic gates, and safe upgrades. Use when initializing or upgrading a repository, when an unmanaged repository grows complex, or when delivery, ownership, security, release, or incident signals suggest a governance capability is missing.

Security

Browse the most popular Claude skills, all security skills, or write your own with the skills generator.