/risk-to-jira-transformer
Converts unstructured risk assessments into structured Jira tickets. Extracts Likelihood, Impact, Mitigation from natural language and generates JSON formatted for Jira API with clear Definition of Done criteria.
$ npx -y skills add GRCEngClub/claude-grc-engineering --skill risk-to-jira-transformer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/risk-to-jira-transformer
Context preview
The summary Claude sees to decide when to auto-load this skill.
Converts unstructured risk assessments into structured Jira tickets. Extracts Likelihood, Impact, Mitigation from natural language and generates JSON formatted for Jira API with clear Definition of Done criteria.
SKILL.md
risk-to-jira-transformer.SKILL.mdname: risk-to-jira-transformer
description: Converts unstructured risk assessments into structured Jira tickets. Extracts Likelihood, Impact, Mitigation from natural language and generates JSON formatted for Jira API with clear Definition of Done criteria.
allowed-tools: Bash, Read, Glob, Write, Edit
Risk-to-Jira Transformer
Converts unstructured risk assessments into structured engineering tickets. Turns "Risk Management" into "Task Management."
Quick Commands
**Transform a risk assessment:**
node plugins/grc-engineer/scripts/transform-risk.js "Vulnerability in authentication service discovered during pen test. High likelihood, critical impact. Mitigation: Implement OAuth2 with PKCE." SEC
**Transform with custom project:**
node plugins/grc-engineer/scripts/transform-risk.js "<risk description>" INFRA
Input Format
Accepts natural language risk descriptions. Automatically extracts:
- **Risk Description** - What is the risk?
- **Likelihood** - How likely is it to occur? (Low/Medium/High/Critical)
- **Impact** - What is the impact? (Low/Medium/High/Critical)
- **Mitigation** - How to address it?
- **Affected Systems** - Which systems are impacted?
Output Format
Generates JSON formatted for Jira API:
{
"fields": {
"project": { "key": "SEC" },
"summary": "Implement OAuth2 with PKCE for authentication service",
"description": "...",
"issuetype": { "name": "Security Task" },
"priority": { "name": "Critical" },
"labels": ["security", "authentication", "risk-mitigation"],
"customfield_10001": "High", // Likelihood
"customfield_10002": "Critical", // Impact
"customfield_10003": "Implement OAuth2 with PKCE" // Mitigation
}
}Jira Fields Generated
- **Summary** - Concise risk title
- **Description** - Full risk assessment with context
- **Priority** - Based on Likelihood × Impact matrix
- **Labels** - Auto-tagged with relevant categories
- **Issue Type** - Security Task, Bug, Story, etc.
- **Definition of Done** - Clear acceptance criteria
- **Custom Fields** - Likelihood, Impact, Mitigation (if configured)
Risk Scoring
Automatically calculates risk score:
- **Critical** - High/Critical Likelihood × High/Critical Impact
- **High** - Medium Likelihood × High Impact, or High Likelihood × Medium Impact
- **Medium** - Other combinations
- **Low** - Low Likelihood × Low Impact
Example Inputs
- "SQL injection vulnerability found in user input validation. High likelihood of exploitation, critical impact on data integrity. Mitigation: Implement parameterized queries and input sanitization."
- "Missing encryption on database backups. Medium likelihood of data breach, high impact. Mitigation: Enable encryption at rest for all backup storage."
- "Unauthorized access possible due to weak password policy. High likelihood, medium impact. Mitigation: Enforce strong password requirements and MFA."
Prerequisites
- Risk description (natural language)
- Optional: Jira project key (defaults to SEC)
- Optional: Jira API credentials (for direct posting)
Read more
name: risk-to-jira-transformer description: Converts unstructured risk assessments into structured Jira tickets. Extracts Likelihood, Impact, Mitigation from natural language and generates JSON formatted for Jira API with clear Definition of Done criteria. allowed-tools: Bash, Read, Glob, Write, Edit
Risk-to-Jira Transformer
Converts unstructured risk assessments into structured engineering tickets. Turns "Risk Management" into "Task Management."
Quick Commands
**Transform a risk assessment:**
node plugins/grc-engineer/scripts/transform-risk.js "Vulnerability in authentication service discovered during pen test. High likelihood, critical impact. Mitigation: Implement OAuth2 with PKCE." SEC
**Transform with custom project:**
node plugins/grc-engineer/scripts/transform-risk.js "<risk description>" INFRA
Input Format
Accepts natural language risk descriptions. Automatically extracts:
- **Risk Description** - What is the risk?
- **Likelihood** - How likely is it to occur? (Low/Medium/High/Critical)
- **Impact** - What is the impact? (Low/Medium/High/Critical)
- **Mitigation** - How to address it?
- **Affected Systems** - Which systems are impacted?
Output Format
Generates JSON formatted for Jira API:
{
"fields": {
"project": { "key": "SEC" },
"summary": "Implement OAuth2 with PKCE for authentication service",
"description": "...",
"issuetype": { "name": "Security Task" },
"priority": { "name": "Critical" },
"labels": ["security", "authentication", "risk-mitigation"],
"customfield_10001": "High", // Likelihood
"customfield_10002": "Critical", // Impact
"customfield_10003": "Implement OAuth2 with PKCE" // Mitigation
}
}Jira Fields Generated
- **Summary** - Concise risk title
- **Description** - Full risk assessment with context
- **Priority** - Based on Likelihood × Impact matrix
- **Labels** - Auto-tagged with relevant categories
- **Issue Type** - Security Task, Bug, Story, etc.
- **Definition of Done** - Clear acceptance criteria
- **Custom Fields** - Likelihood, Impact, Mitigation (if configured)
Risk Scoring
Automatically calculates risk score:
- **Critical** - High/Critical Likelihood × High/Critical Impact
- **High** - Medium Likelihood × High Impact, or High Likelihood × Medium Impact
- **Medium** - Other combinations
- **Low** - Low Likelihood × Low Impact
Example Inputs
- "SQL injection vulnerability found in user input validation. High likelihood of exploitation, critical impact on data integrity. Mitigation: Implement parameterized queries and input sanitization."
- "Missing encryption on database backups. Medium likelihood of data breach, high impact. Mitigation: Enable encryption at rest for all backup storage."
- "Unauthorized access possible due to weak password policy. High likelihood, medium impact. Mitigation: Enforce strong password requirements and MFA."
Prerequisites
- Risk description (natural language)
- Optional: Jira project key (defaults to SEC)
- Optional: Jira API credentials (for direct posting)
Open-source GRC Engineering resource for Claude. claude-grc-engineering turns technical evidence from cloud, SaaS, code, and security tools into framework-aligned findings, gap reports, remediation guidance, evidence packages, and OSCAL workflows.
Repo: GRCEngClub/claude-grc-engineering
Other skills on trust-center.
- /academic-research-companion
Guide a research project through the full academic lifecycle — from raw idea to concrete research question, literature grounding, methodology, writing, feedback, and publication. Use this skill whenever the user shares a research idea, asks to "flesh out" a topic, wants sources
Open skill - /aws-inspector-expert
Expertise in evaluating AWS accounts for compliance — what checks are meaningful, which SCF controls they map to, and how to interpret aws CLI output.
Open skill - /azure-inspector-expert
Expertise in evaluating Azure subscription findings from azure-inspector and mapping them to SCF controls.
Open skill - /crowdstrike-inspector-expert
Interpret CrowdStrike Falcon findings for sensor coverage, policy visibility, and host group scoping.
Open skill - /datadog-inspector-expert
Interpret datadog-inspector findings and translate Datadog monitoring, audit, log-retention, SSO, and RBAC results into GRC evidence and remediation.
Open skill - /drata-inspector-expert
Interpret drata-inspector findings generated from drata-cli workflows and turn Drata control, monitor, evidence, personnel, and integration posture into GRC action.
Open skill

