skills/grc/risk-identification/SKILL.md
Identify emerging risks, prioritize intake signals, and route candidates into formal GRC risk assessment workflows
npx skillsauth add happy-technologies-llc/happy-servicenow-skills risk-identificationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill supports proactive risk identification in ServiceNow® before full assessment and treatment. It helps teams:
Use this when risk managers need structured early detection, not only post-event summarization.
sn_grc.manager, sn_risk.manager, or adminValidate table and fields used in your instance for risk identification workflows.
Using MCP:
Tool: SN-Discover-Table-Schema
Parameters:
table_name: sn_risk_identification
If your instance uses alternate table names, capture mappings before continuing.
Pull new or updated risk candidates and supporting context.
Using MCP:
Tool: SN-Query-Table
Parameters:
table_name: sn_risk_identification
query: stateINnew,under_review^sys_updated_on>=javascript:gs.daysAgoStart(7)
fields: number,short_description,state,category,profile,owner,likelihood,impact,sys_updated_on
limit: 100
Gather profile posture and related historical risk records.
Using MCP:
Tool: SN-Query-Table
Parameters:
table_name: sn_grc_risk
query: profile=[profile_sys_id]^active=true
fields: number,short_description,state,residual_risk,inherent_risk,risk_score
limit: 50
Apply an intake score based on impact, likelihood, velocity, and control coverage.
Suggested decision bands:
Route high/medium items into accountable next steps.
Using MCP:
Tool: SN-Create-Record
Parameters:
table_name: task
fields:
short_description: "Risk identification follow-up"
description: "Perform formal assessment for high-priority risk candidate."
priority: 2
Write final intake rationale with scoring factors and escalation decision.
| Tool | Purpose |
|---|---|
| SN-Discover-Table-Schema | Validate table names and field availability |
| SN-Query-Table | Retrieve candidate, profile, and historical risk data |
| SN-Read-Record | Inspect individual candidate details |
| SN-Create-Record | Create follow-up tasks/issues for escalated candidates |
| SN-Update-Record | Update candidate state and priority |
| SN-Add-Work-Notes | Capture audit-ready intake rationale |
Symptom: Query fails for sn_risk_identification.
Cause: Instance uses alternate table naming or scoped table variants.
Solution: Use schema discovery and update table mappings for your environment.
Symptom: Intake queue grows without actionable prioritization.
Cause: Risk signal sources are noisy or scoring thresholds are too permissive.
Solution: Tighten intake criteria and require minimum evidence before escalation.
grc/risk-assessment-summarization - Summarize formal risk assessmentsgrc/risk-event-summarization - Summarize materialized risk eventsgrc/issue-validator - Validate quality of downstream GRC issuestesting
Manage supplier onboarding, qualification, performance monitoring, and offboarding with auditable lifecycle controls
documentation
Screen inbound documents for completeness, policy risk, and routing readiness before extraction or case workflows
testing
Generate concise task summaries with status, timeline, blockers, SLA risk, and recommended next actions
development
Triage, prioritize, and assign ServiceNow incidents using impact/urgency matrix and category-based routing. Use when an alert fires, a ticket lands unassigned, an outage is reported, an escalation is needed, severity must be classified, an on-call team must be paged, or an SLA is at risk.