© 2015 IEEE. This paper looks into ways of supporting social Web services react to the behaviors that their peers expose at run time. Examples of behaviors include selfishness and unfairness. These reactions are associated with actions packaged into capabilities. A capability allows a social Web service to stop exchanging private details with a peer and/or to suspend collaborating with another peer, for example. The analysis of capability results into three types referred to as functional (what a social Web service does), non-functional (how a social Web service runs), and social (how a social Web service reacts to peers). To avoid cross-cutting concerns among these capabilities aspect-oriented programming is used for implementing a system.