agentleFS
Happy-Technologies-LLCHappy-Technologies-LLC/happy-platform-skills/skills/grc/risk-identification/SKILL.md

risk-identification

Skill41 starsChanged 21 days agoApache-2.0View on GitHub

Identify emerging risks, prioritize intake signals, and route candidates into formal GRC risk assessment workflows

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this when risk managers need structured early detection, not only post-event summarization.

    line 39
  2. Distinctive:

    Access: Read/write access to risk identification, profile, risk, and issue tables

    line 45
  3. Distinctive:

    If your instance uses alternate table names, capture mappings before continuing.

    line 61
  4. Distinctive:

    Write final intake rationale with scoring factors and escalation decision.

    line 117
  5. Distinctive:

    Keep scoring model transparent and versioned

    line 133
  6. Distinctive:

    Use consistent category mapping to avoid duplicate risk records

    line 134
  7. Distinctive:

    Solution: Use schema discovery and update table mappings for your environment.

    line 144

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Risk Identification

Overview

This skill supports proactive risk identification in ServiceNow® before full assessment and treatment. It helps teams:

  • Gather risk signals from business applications, issues, and operational events
  • Classify and prioritize risk candidates
  • Route high-priority candidates for formal assessment
  • Maintain governance-ready evidence for risk intake decisions

Use this when risk managers need structured early detection, not only post-event summarization.

Prerequisites

  • Roles: sn_grc.manager, sn_risk.manager, or admin
  • Plugins: GRC / Risk Management enabled
  • Access: Read/write access to risk identification, profile, risk, and issue tables
  • Policy Inputs: Risk taxonomy, scoring thresholds, and escalation criteria

Procedure

Step 1: Confirm Risk Identification Schema

Validate 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.

Step 2: Ingest Risk Candidate Signals

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

Step 3: Enrich with Profile and Historical Context

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

Step 4: Score and Prioritize Candidates

Apply an intake score based on impact, likelihood, velocity, and control coverage.

Suggested decision bands:

  • High: escalate immediately to formal assessment
  • Medium: assign analyst review with due date
  • Low: monitor and capture rationale

Step 5: Create Follow-Up Actions

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

Step 6: Record Governance Evidence

Write final intake rationale with scoring factors and escalation decision.

Tool Usage

ToolPurpose
SN-Discover-Table-SchemaValidate table names and field availability
SN-Query-TableRetrieve candidate, profile, and historical risk data
SN-Get-RecordInspect individual candidate details
SN-Create-RecordCreate follow-up tasks/issues for escalated candidates
SN-Update-RecordUpdate candidate state and priority
SN-Add-Work-NotesCapture audit-ready intake rationale

Best Practices

  • Separate risk identification from risk treatment decisions
  • Keep scoring model transparent and versioned
  • Use consistent category mapping to avoid duplicate risk records
  • Time-box analyst review for medium-priority candidates
  • Link every escalation to an owner and target completion date

Troubleshooting

Risk Identification Table Not Found

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.

Too Many Low-Quality Candidates

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.

Related Skills

  • grc/risk-assessment-summarization - Summarize formal risk assessments
  • grc/risk-event-summarization - Summarize materialized risk events
  • grc/issue-validator - Validate quality of downstream GRC issues

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.