How do I install the Rtl P4s Unit Test skill?

Run npx skillmds@latest add babyworm/rtl-p4s-unit-test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rtl P4s Unit Test safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rtl P4s Unit Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rtl P4s Unit Test free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rtl P4s Unit Test?

babyworm (@babyworm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rtl P4s Unit Test by babyworm — Agent Skill

Name: Rtl P4s Unit Test
Author: babyworm

File contents

Testing Tier Context:

Tier 1: Smoke Test     — connectivity, R/W, basic ops (rtl-p4-implement Wave 6)
Tier 2: Unit Test      — reference comparison, uarch features (THIS SKILL) ←
Tier 3: Module Regr.   — cocotb multi-seed (rtl-p5s-func-verify)
Tier 4: Integration    — cross-module, end-to-end (rtl-p5s-integration-test)

Outputs: sim/{module}/tb_{module}.sv testbench files + sim/{module}/{module}_unit_results.json.

All coding conventions, reference mode rules, escalation criteria, and result schemas are defined in the rtl-p4s-unit-test-policy skill (loaded via the orchestrator's skills: field).

Execution

Task(subagent_type="rtl-agent-team:p4s-unit-test-orchestrator", prompt="Execute Tier 2 unit testing. User input: $ARGUMENTS")

Do not perform any work directly. The orchestrator agent manages testbench generation, simulation, and failure triage.

Output

sim/{module}/tb_{module}.sv — Tier 2 unit test testbenches
sim/{module}/{module}_unit_results.json — results with ref_mismatches=0, coverage thresholds met, and req_ids populated

---name: rtl-p4s-unit-testdescription: P4 Tier 2 unit tests: verify each RTL module against its uarch spec and C reference model. Use after lint+smoke pass, before Tier 3 regression.---<Purpose>Write and run unit tests that verify each RTL module implements its microarchitecturespecification correctly. Compares RTL output against the C reference model for functionalcorrectness. Goes beyond Tier 1 smoke testing (rtl-p4-implement Wave 6) to exercise key featuresat uarch level: FSM state transitions, pipeline stage behavior, data transformation accuracy.**Testing Tier Context:**```Tier 1: Smoke Test — connectivity, R/W, basic ops (rtl-p4-implement Wave 6)Tier 2: Unit Test — reference comparison, uarch features (THIS SKILL) ←Tier 3: Module Regr. — cocotb multi-seed (rtl-p5s-func-verify)Tier 4: Integration — cross-module, end-to-end (rtl-p5s-integration-test)```Outputs: sim/{module}/tb_{module}.sv testbench files + sim/{module}/{module}_unit_results.json.</Purpose><Use_When>- Phase 4 RTL is lint-clean AND Tier 1 smoke test passed (rtl-p4-implement Wave 6)- Each module needs uarch-level functional verification with reference comparison- A new module's key features need targeted testing beyond connectivity- A bug fix needs regression test verifying the fix against reference model</Use_When><Do_Not_Use_When>- Only basic connectivity/R/W verification needed (covered by rtl-p4-implement Wave 6 smoke — Tier 1)- Full multi-seed regression needed (use rtl-p5s-func-verify — Tier 3)- Integration/cross-module testing (use rtl-p5s-integration-test — Tier 4)- Formal verification preferred (use rtl-p5s-sva-check instead)</Do_Not_Use_When><Why_This_Exists>Tier 1 (smoke) only verifies connectivity and basic I/O. Tier 2 unit tests verify that eachmodule implements its uarch spec — FSM states, pipeline stages, data transformations — usingthe C reference model as the golden oracle. This catches behavioral bugs that smoke tests miss,while remaining faster and more targeted than full regression (Tier 3).</Why_This_Exists><Delegation>The orchestrator writes testbenches per module (parallel via testbench-dev), selectsreference comparison mode (DPI-C or file-based), runs simulations, and handlesfailure triage with waveform analysis.All coding conventions, reference mode rules, escalation criteria, and result schemasare defined in the rtl-p4s-unit-test-policy skill (loaded via the orchestrator's skills: field).## ExecutionTask(subagent_type="rtl-agent-team:p4s-unit-test-orchestrator", prompt="Execute Tier 2 unit testing. User input: $ARGUMENTS")Do not perform any work directly.The orchestrator agent manages testbench generation, simulation, and failure triage.## Output- `sim/{module}/tb_{module}.sv` — Tier 2 unit test testbenches- `sim/{module}/{module}_unit_results.json` — results with `ref_mismatches=0`, coverage thresholds met, and `req_ids` populated</Delegation>

Frequently asked questions

Rtl P4s Unit Test