메뉴
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에서 현재 제공할 수 있는 파일을 다운로드하세요.
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.
