Windows Protocols Corpus Navigator
Overview
- The corpus is already extracted next to
SKILL.md.
- Use local files only; do not use network lookup, downloads, or setup commands.
Corpus Layout
README.md — top-level index. Start with Overview Documents for topical discovery.LEGAL.md — legal and redistribution notice.<PROTOCOL-ID>/ — protocol directories.<PROTOCOL-ID>/<PROTOCOL-ID>.md — primary markdown spec content.<PROTOCOL-ID>/media/ — extracted figures and image assets referenced by the markdown.
When the question is broad, start from Overview Documents or protocol families such as MS-RDP*, MS-AD*, or MS-MQ*.
Reference File
- Use
SKILL.md for the default workflow, worked example, and answer contract.
- Open
REFERENCE.md only for these lookup aids: Domain Clusters, Canonical Spec Structure, and Section-First Routing.
Navigation Workflow
Use this unified workflow for all queries:
- Topical questions: identify the domain, open the matching Overview document from
README.md, and follow its member-spec links.
- Anti-pattern: do not rely on README keyword search alone; Overview documents provide the authoritative topic-to-protocol mapping.
- Known protocol ID: Validate against
README.md and directory names (<PROTOCOL-ID>/), then open the spec directly.
- If the protocol is missing, say so and ask for the exact protocol ID or a narrower scope.
- Ambiguous acronyms: List 2–4 likely protocols (via Overview docs) and ask the user to choose before deep analysis.
- Scan the spec TOC (
<summary> blocks and numbered entries) before deep reading.
- Read sections in this order: orientation/versioning → syntax → behavior/sequencing → security/product behavior.
- Cross-check base vs. extension specs when requirements are split, following cross-reference links as needed.
- Answer with explicit protocol IDs and exact section headings; separate confirmed facts from inference.
Link-Following
- Follow Overview-document references and inline links rather than guessing paths.
- Treat Overview → spec → related spec as the intended path.
- When a spec references another spec for types, extensions, or dependencies, follow that link to the authoritative source.
- Do not stop at the first mention; keep following links until the authoritative section answers the question.
Worked Example
User question: "In SMB2, how does the server signal that it supports persistent handles?"
Path: File Access Overview → MS-SMB2 → 2.2.4 NEGOTIATE Response → 3.3.5.4 Receiving an SMB2 NEGOTIATE Request.
Answer: cite MS-SMB2, note that the server signals support by setting SMB2_GLOBAL_CAP_PERSISTENT_HANDLES (0x00000010) in the NEGOTIATE Response Capabilities field, and put version-specific caveats under uncertainty or product behavior notes.
Answer Contract
Default answer shape:
Protocols consulted: list exact IDs.Sections used: list exact section titles (and numbers when available).Findings: concise facts tied to those sections.Inference / uncertainty: explicit separation from confirmed text.
Guidance:
- Prefer section-grounded answers and include exact protocol IDs.
- For non-obvious, contested, or security-sensitive claims, include section-grounded evidence.
- For straightforward facts, concise section references are enough.
- If two specs disagree, report both and identify likely version or context scope.
- State uncertainty explicitly, and never present inferred behavior as normative requirement text.
1---2name: windows-protocols3description: Local Microsoft Open Specifications corpus navigator for Windows protocols. Parses protocol message formats, looks up field definitions, maps data types, traces protocol state machines, and performs cross-reference analysis across related specifications. Use when the user asks protocol-level questions, needs message/structure details or wire-format field definitions, wants section-by-section summaries, needs to trace protocol state machines or sequencing rules, or requires cross-references across related MS-* specifications.4---56# Windows Protocols Corpus Navigator78## Overview910- The corpus is already extracted next to `SKILL.md`.11- Use local files only; do not use network lookup, downloads, or setup commands.1213## Corpus Layout1415- `README.md` — top-level index. Start with Overview Documents for topical discovery.16- `LEGAL.md` — legal and redistribution notice.17- `<PROTOCOL-ID>/` — protocol directories.18- `<PROTOCOL-ID>/<PROTOCOL-ID>.md` — primary markdown spec content.19- `<PROTOCOL-ID>/media/` — extracted figures and image assets referenced by the markdown.2021When the question is broad, start from Overview Documents or protocol families such as `MS-RDP*`, `MS-AD*`, or `MS-MQ*`.2223## Reference File2425- Use `SKILL.md` for the default workflow, worked example, and answer contract.26- Open `REFERENCE.md` only for these lookup aids: Domain Clusters, Canonical Spec Structure, and Section-First Routing.2728## Navigation Workflow2930Use this unified workflow for all queries:31321. **Topical questions**: identify the domain, open the matching Overview document from `README.md`, and follow its member-spec links.33 - **Anti-pattern**: do not rely on README keyword search alone; Overview documents provide the authoritative topic-to-protocol mapping.342. **Known protocol ID**: Validate against `README.md` and directory names (`<PROTOCOL-ID>/`), then open the spec directly.35 - If the protocol is missing, say so and ask for the exact protocol ID or a narrower scope.363. **Ambiguous acronyms**: List 2–4 likely protocols (via Overview docs) and ask the user to choose before deep analysis.374. Scan the spec TOC (`<summary>` blocks and numbered entries) before deep reading.385. Read sections in this order: orientation/versioning → syntax → behavior/sequencing → security/product behavior.396. Cross-check base vs. extension specs when requirements are split, following cross-reference links as needed.407. Answer with explicit protocol IDs and exact section headings; separate confirmed facts from inference.4142### Link-Following4344- Follow Overview-document references and inline links rather than guessing paths.45- Treat Overview → spec → related spec as the intended path.46- When a spec references another spec for types, extensions, or dependencies, follow that link to the authoritative source.47- Do not stop at the first mention; keep following links until the authoritative section answers the question.4849## Worked Example5051**User question**: "In SMB2, how does the server signal that it supports persistent handles?"5253Path: File Access Overview → `MS-SMB2` → `2.2.4 NEGOTIATE Response` → `3.3.5.4 Receiving an SMB2 NEGOTIATE Request`.5455Answer: cite `MS-SMB2`, note that the server signals support by setting `SMB2_GLOBAL_CAP_PERSISTENT_HANDLES (0x00000010)` in the NEGOTIATE Response `Capabilities` field, and put version-specific caveats under uncertainty or product behavior notes.5657## Answer Contract5859Default answer shape:60611. `Protocols consulted`: list exact IDs.622. `Sections used`: list exact section titles (and numbers when available).633. `Findings`: concise facts tied to those sections.644. `Inference / uncertainty`: explicit separation from confirmed text.6566Guidance:6768- Prefer section-grounded answers and include exact protocol IDs.69- For non-obvious, contested, or security-sensitive claims, include section-grounded evidence.70- For straightforward facts, concise section references are enough.71- If two specs disagree, report both and identify likely version or context scope.72- State uncertainty explicitly, and never present inferred behavior as normative requirement text.
awakecoding