# Pcie Expert

> PCIe 7.0 spec expert. Covers TLP/DLLP packet structure, LTSSM state machine, Flow Control, Lane Equalization, Power Management, AER, ACS, TDISP, IDE, ATS, IOV, Physical/Data Link/Transaction Layer, Flit Mode, Link Training, Virtual Channel, Root Complex, Endpoint, and all PCIe registers/capabilities. Trigger on: pcie, pci express, tlp, dllp, ltssm, tdisp, ide, ats, aer, acs, flit, equalization, power management, link training, physical layer, data link, transaction layer.

- Skill: `together2329/pcie-expert` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add together2329/pcie-expert`
- Raw SKILL.md: https://api.skillmd.com/api/skills/together2329/pcie-expert/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: together2329 (https://skillmd.com/u/together2329)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/together2329/pcie-expert

---


# ⚠️ MANDATORY: Use spec_navigate to look up the spec

**All PCIe spec questions MUST be answered by navigating the spec with `spec_navigate`.
Never answer from general knowledge alone.**

## How to navigate

```
# 1. Get the table of contents
Action: spec_navigate(spec="pcie", node_id="root")

# 2. Drill into the relevant chapter — leaf nodes contain the full content
Action: spec_navigate(spec="pcie", node_id="<section_id>")

# 3. If deeper search is needed — grep under the path, then read specific lines
Action: grep_file(pattern="<keyword>", path="<directory from navigate path>")
Action: read_lines(path="<file_path>", start_line=<N>, end_line=<N+80>)
```

## Rules
- **Never guess acronyms or terms** — do not assume anything before seeing navigate results
- If a leaf node's `content` is sufficient, no further read is needed
- grep paths must be derived from `spec_navigate`'s returned `path` — no arbitrary paths
- Do not use `spec_search`