Skip to main content
ClaudeWave
EN, English
Skill262 repo starsupdated 7mo ago

calculate-priority-score

The calculate-priority-score Claude Code skill computes a numeric priority ranking for bugs, issues, and tasks by summing weighted scores from severity, impact, and likelihood factors, then maps the total to a priority category ranging from P0 (Critical) to P4 (Minimal). Use this skill to systematically order work items, allocate development resources, and assess security vulnerability risks based on consistent evaluation criteria.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit /tmp/calculate-priority-score && cp -r /tmp/calculate-priority-score/.claude/skills/calculate-priority-score ~/.claude/skills/calculate-priority-score
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# Calculate Priority Score

Calculate numeric priority score and category for issues based on multiple factors.

## When to Use

- Bug prioritization
- Security vulnerability risk assessment
- Task ordering
- Resource allocation decisions

## Instructions

### Step 1: Receive Issue Attributes

Accept issue attributes as input.

**Expected Input**:
```json
{
  "severity": "critical|high|medium|low",
  "impact": "breaking|major|minor|none",
  "likelihood": "certain|likely|possible|unlikely"
}
```

### Step 2: Load Scoring Matrix

Use scoring matrix to assign points.

**Severity Scores**:
- critical: 10
- high: 7
- medium: 5
- low: 2

**Impact Scores**:
- breaking: 10
- major: 7
- minor: 3
- none: 0

**Likelihood Scores**:
- certain: 10
- likely: 7
- possible: 5
- unlikely: 2

### Step 3: Calculate Total Score

Sum all factor scores.

**Formula**: `score = severity + impact + likelihood`

**Range**: 0-30

### Step 4: Determine Priority Category

Map score to priority category.

**Priority Categories**:
- **P0 (Critical)**: 25-30
  - Label: "Critical - Immediate Action Required"
  - Action: Drop everything, fix now

- **P1 (High)**: 19-24
  - Label: "High - Fix This Sprint"
  - Action: Prioritize in current sprint

- **P2 (Medium)**: 12-18
  - Label: "Medium - Schedule for Next Sprint"
  - Action: Include in backlog, address soon

- **P3 (Low)**: 5-11
  - Label: "Low - Schedule When Convenient"
  - Action: Nice to have, low priority

- **P4 (Minimal)**: 0-4
  - Label: "Minimal - Consider Closing"
  - Action: May not be worth fixing

### Step 5: Return Scored Result

Return complete priority assessment.

**Expected Output**:
```json
{
  "score": 27,
  "category": "P0",
  "label": "Critical - Immediate Action Required",
  "factors": {
    "severity": 10,
    "impact": 10,
    "likelihood": 7
  },
  "recommendation": "Drop everything, fix now"
}
```

## Error Handling

- **Invalid Severity**: Return error listing valid values
- **Invalid Impact**: Return error listing valid values
- **Invalid Likelihood**: Return error listing valid values
- **Missing Factor**: Return error requesting all factors

## Examples

### Example 1: Critical Bug

**Input**:
```json
{
  "severity": "critical",
  "impact": "breaking",
  "likelihood": "certain"
}
```

**Output**:
```json
{
  "score": 30,
  "category": "P0",
  "label": "Critical - Immediate Action Required",
  "factors": {
    "severity": 10,
    "impact": 10,
    "likelihood": 10
  },
  "recommendation": "Drop everything, fix now"
}
```

### Example 2: Medium Priority Issue

**Input**:
```json
{
  "severity": "medium",
  "impact": "minor",
  "likelihood": "likely"
}
```

**Output**:
```json
{
  "score": 15,
  "category": "P2",
  "label": "Medium - Schedule for Next Sprint",
  "factors": {
    "severity": 5,
    "impact": 3,
    "likelihood": 7
  },
  "recommendation": "Include in backlog, address soon"
}
```

### Example 3: Low Priority Enhancement

**Input**:
```json
{
  "severity": "low",
  "impact": "minor",
  "likelihood": "unlikely"
}
```

**Output**:
```json
{
  "score": 7,
  "category": "P3",
  "label": "Low - Schedule When Convenient",
  "factors": {
    "severity": 2,
    "impact": 3,
    "likelihood": 2
  },
  "recommendation": "Nice to have, low priority"
}
```

### Example 4: High-Impact but Unlikely

**Input**:
```json
{
  "severity": "high",
  "impact": "breaking",
  "likelihood": "unlikely"
}
```

**Output**:
```json
{
  "score": 19,
  "category": "P1",
  "label": "High - Fix This Sprint",
  "factors": {
    "severity": 7,
    "impact": 10,
    "likelihood": 2
  },
  "recommendation": "Prioritize in current sprint"
}
```

## Validation

- [ ] Calculates score correctly
- [ ] Maps to correct priority category
- [ ] Handles all valid factor values
- [ ] Returns clear recommendations
- [ ] Validates input factors

## Supporting Files

- `scoring-matrix.json`: Factor scoring rules (see Supporting Files section)
algorithmic-artSkill

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

artifacts-builderSkill

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

beadsSkill
beads-initSlash Command

Initialize Beads issue tracking in your project with interactive configuration setup.

canvas-designSkill

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

changelog-generatorSkill

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

cleanup-health-inlineSkill

Inline orchestration workflow for dead code detection and removal with Beads integration. Provides step-by-step phases for dead-code-hunter detection, priority-based cleanup with dead-code-remover, and verification cycles.

code-reviewSkill

Analyzes code changes for bugs, security vulnerabilities, performance problems, and architectural improvements. Generates structured markdown reports with evidence-based findings tied to specific file:line references, and creates Beads tasks for tracking. Adapts review depth based on scope — from quick pre-commit checks to thorough branch reviews. Use proactively when reviewing code before commits, after implementing features, before PRs, when checking code quality, or when the user mentions "review", "check changes", "code review", "PR review", "review branch", or any code quality assessment.