widget-coherence

Validate communication protocols among ServiceNow Service Portal widget components.

77|23|Updated Jul 16, 2025
One-click install
npx skills add https://github.com/groeimetai/snow-flow --skill widget-coherence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: widget-coherence
Source: https://github.com/groeimetai/snow-flow/tree/main/packages/opencode/src/bundled-skills/widget-coherence
Command: npx skills add https://github.com/groeimetai/snow-flow --skill widget-coherence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that the different components of a ServiceNow Service Portal widget (Server Script, Client Controller, HTML Template) communicate effectively, preventing common errors and improving widget reliability.

Core Features & Use Cases

  • Synchronized Communication: Enforces a strict three-way contract between server, client, and HTML.
  • Data Flow Validation: Provides patterns and checklists to ensure data is passed correctly.
  • Common Failure Diagnosis: Helps identify and fix issues like action name mismatches or undefined data properties.
  • Use Case: When a Service Portal widget is not displaying data correctly or buttons are unresponsive, this skill can diagnose and fix the communication breakdown between its parts.

Quick Start

Use the widget-coherence skill to validate the communication between the server script, client controller, and HTML template for the 'MyWidget' Service Portal widget.

Frequently Asked Questions about widget-coherence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug unresponsive buttons in a ServiceNow Service Portal widget?

Debug unresponsive Service Portal widget buttons by validating the communication contract between the HTML Template and Client Controller. Action name mismatches in data-action attributes often cause button click events to fail silently.

Why does my Service Portal widget display undefined data from the Server Script?

Service Portal widgets display undefined data when the Server Script output does not match the Client Controller input expectations. Validating the three-way data flow contract ensures data properties are correctly passed and defined.

How do I validate data flow between a widget Server Script and Client Controller?

Validate widget data flow by enforcing a strict three-way contract between the Server Script, Client Controller, and HTML Template. This ensures data is passed correctly and method invocations match across components.

What is the three-way contract in Service Portal widget development?

The three-way contract in Service Portal widget development synchronizes communication between the Server Script, Client Controller, and HTML Template. It ensures data flow, action handling, and method invocations maintain functional integrity.

Can I use this to diagnose action name mismatches in Service Portal widgets?

Yes, you can diagnose action name mismatches in Service Portal widgets by checking the communication protocols between components. Identifying inconsistencies between Client Controller actions and HTML Template invocations resolves common failures.

What causes communication breakdown between Service Portal widget components?

Communication breakdown between Service Portal widget components is caused by failing to adhere to the three-way contract. Issues like undefined data properties and action name mismatches disrupt the server and client synchronization.