Use when building, automating, or debugging Cisco Packet Tracer networks through the packet-tracer MCP (the pt_* tools) — planning topologies from natural language, live-deploying into a running Packet Tracer, adding devices / links / modules, applying ACL / NAT, exporting configs, or writing raw Script-Engine JS via pt_send_raw. This is the authoritative reference for the tool catalog, the mandatory discover→plan→validate→deploy workflow, the EXACT PT Script-Engine API (so you never invent method names), and the known rough edges. Load it before driving the MCP so you act from verified facts, not guesses.
$npx -y skills add mats2208/mcp-packet-tracer --skill skillInstalls into the current project.
Run `npx skills use "https://github.com/mats2208/mcp-packet-tracer" --skill "mats2208/mcp-packet-tracer/skill"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/mats2208/mcp-packet-tracer" that are relevant to the current task. Run `npx skills add "https://github.com/mats2208/mcp-packet-tracer"` and select the relevant skills, then follow their instructions.