Produces a structured summary of a requirements document — the key obligations, grouped by actor and concern, with the MUST/SHOULD/MAY breakdown. Use when onboarding to a large spec, when deciding what to implement first, or when the user asks what a 200-page standard actually requires.
82
93%
Does it follow best practices?
Impact
25%
0.36xAverage score across 1 eval scenario
Passed
No findings from the security scan
Obligation-level compliance summary of RFC 8725 JWT BCP
MUST before SHOULD ordering
100%
0%
Separate MUST and SHOULD sections
100%
0%
Compression section present
0%
0%
Section references throughout
100%
60%
Verbatim RFC 2119 keywords retained
100%
90%
No informative content leaked
100%
40%
Source section present
25%
37%
Scope section present
0%
37%
Key definitions section present
14%
0%
47d56bb
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.