菜单
Analyze IronRDP changes for RDP protocol conformance against Microsoft Open Specifications. Use when reviewing protocol behavior, wire formats, PDUs, virtual channels, codecs, security, capability negotiation, or protocol-visible errors.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Devolutions/IronRDP --skill protocol-reviewer命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Derive and validate the canonical scope for IronRDP Conventional Commit and pull-request titles. Use whenever composing, reviewing, correcting, or checking a commit or PR title, especially when several crates or product surfaces intersect.
Write or substantially revise a Rust crate's README.md as a concise, user-facing design document. Use whenever creating a crate README, documenting a planned crate, or defining a crate's purpose, role, or interface before implementation.
Create and integrate a new Rust crate in the IronRDP workspace. Use whenever adding, scaffolding, or initializing a crate under crates/, including requests that mention cargo new, a new library package, or registering a crate in the architecture.
基于 SOC 职业分类
正在显示 SKILL.md
| name | protocol-reviewer |
| description | Analyze IronRDP changes for RDP protocol conformance against Microsoft Open Specifications. Use when reviewing protocol behavior, wire formats, PDUs, virtual channels, codecs, security, capability negotiation, or protocol-visible errors. |
Use the windows-protocols skill when it is available to consult the local Microsoft Open Specifications corpus.
If it is unavailable, use the Microsoft Learn MCP server when configured: search with microsoft_docs_search, then retrieve relevant learn.microsoft.com/openspecs pages with microsoft_docs_fetch.
If neither source is available, use another authoritative specification source provided in the task and state any resulting evidence gap.
Keep the review focused on protocol conformance rather than general code quality. Identify changed wire formats, PDUs, fields, constants, state transitions, capability negotiation, security behavior, virtual channels, codecs, and protocol-visible errors. First decide whether the change is materially protocol-related; do not force a protocol review onto an unrelated change.
Identify the governing requirements before judging the implementation. Start from the relevant overview when the protocol ID is uncertain, then follow base, extension, and shared-type references. Check versioning, capability negotiation, sequencing, security, and product-behavior sections when applicable.
Map each protocol-relevant change to its requirement and attempt to falsify compliance: field order, width, signedness, constants, reserved values, optional fields, lengths, bounds, encode/decode symmetry, malformed-input handling, state-machine transitions, ordering, error paths, compatibility guards, endpoint roles, security requirements, and undocumented interoperability assumptions.
Separate normative requirements from informative text, product-specific behavior, and inference. Cite the governing source precisely and make uncertainty explicit when the corpus is inconclusive. Do not infer a requirement merely because an implementation pattern is conventional or propose architectural refactors unless the specification requires them.
