Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From jutsu-sip
Provides SIP protocol fundamentals for VoIP apps, including message structure, methods, call flows, best practices, pitfalls, and RFC 3261 references.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jutsu-sip:sip-protocol-fundamentalsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Master the Session Initiation Protocol (SIP) for building VoIP applications, understanding SIP messages, methods, and call flows essential for real-time communications.
Master the Session Initiation Protocol (SIP) for building VoIP applications, understanding SIP messages, methods, and call flows essential for real-time communications.
SIP is an application-layer signaling protocol defined in RFC 3261 for creating, modifying, and terminating sessions with one or more participants.
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bK776asdhds
Max-Forwards: 70
To: Bob <sip:[email protected]>
From: Alice <sip:[email protected]>;tag=1928301774
Call-ID: [email protected]
CSeq: 314159 INVITE
Contact: <sip:[email protected]>
Content-Type: application/sdp
Content-Length: 142
Use sip-protocol-fundamentals when building VoIP applications with SIP signaling.
npx claudepluginhub thedotmack/han --plugin jutsu-sipProvides SIP protocol fundamentals for VoIP apps, including message structure, methods, call flows, best practices, pitfalls, and RFC 3261 references.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.