跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

task-analysis

Analyze task trends, identify bottlenecks, predict SLA breaches, and recommend workload redistribution

Happy Technologies LLC · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Happy-Technologies-LLC/happy-platform-skills --skill task-analysis

技能说明


name: task-analysis version: 1.0.1 description: Analyze task trends, identify bottlenecks, predict SLA breaches, and recommend workload redistribution author: Happy Technologies LLC tags: [admin, task, analysis, bottleneck, sla, workload, trends, capacity, planning] platforms: [claude-code, claude-desktop, chatgpt, cursor, any] tools: mcp: - SN-Query-Table - SN-Get-Record - SN-Natural-Language-Search - SN-Execute-Background-Script - SN-Add-Work-Notes rest: - /api/now/table/task - /api/now/table/sc_task - /api/now/table/planned_task - /api/now/table/task_sla - /api/now/table/sys_user_group - /api/now/table/cmn_schedule native: - Bash complexity: intermediate estimated_time: 15-35 minutes

Task Analysis

Overview

This skill provides comprehensive analysis of task data across ServiceNow to identify operational patterns and optimize work distribution. It covers:

  • Analyzing task volume trends across task, sc_task, and planned_task tables
  • Identifying bottleneck assignment groups and individuals with excessive workloads
  • Predicting SLA breaches by analyzing task_sla records and current task aging
  • Recommending workload redistribution based on capacity and skill alignment
  • Generating task health dashboards with key performance indicators
  • Detecting patterns in task reassignment, escalation, and resolution times

When to use: When managers need visibility into team workload distribution, when SLA compliance is trending downward, when planning capacity for upcoming projects, or when identifying systemic bottlenecks in task fulfillment.

Value proposition: Proactive task analysis prevents SLA breaches, balances workload across teams, and provides data-driven input for staffing and process improvement decisions.

Prerequisites

  • Roles: itil, task_admin, assignment_group_manager, or admin
  • Access: Read access to task, sc_task, planned_task, task_sla, sys_user_group, and sys_user tables
  • Knowledge: Understanding of task lifecycle states, SLA definitions, and organizational assignment group structure

Procedure

Step 1: Assess Current Task Volume and State Distribution

Get a snapshot of active tasks across all task types.

Using MCP (Claude Code/Desktop):

Tool: SN-Execute-Background-Script
Parameters:
  description: Task volume snapshot by type and state
  script: |
    var snapshot = { timestamp: new GlideDateTime().getDisplayValue(), task_types: [] };
    var tables = ['incident', 'sc_task', 'change_request', 'problem', 'sc_req_item'];

    tables.forEach(function(tableName) {
      var typeData = { table: tableName, states: {} };
      var ga = new GlideAggregate(tableName);
      ga.addQuery('active', true);
      ga.addAggregate('COUNT');
      ga.groupBy('state');
      ga.query();

      var total = 0;
      while (ga.next()) {
        var state = ga.state.getDisplayValue();
        var count = parseInt(ga.getAggregate('COUNT'));
        typeData.states[state] = count;
        total += count;
      }
      typeData.total_active = total;
      snapshot.task_types.push(typeData);
    });

    gs.info(JSON.stringify(snapshot, null, 2));

Using REST API (for a specific task type):

GET /api/now/table/sc_task?sysparm_query=active=true&sysparm_fields=sys_id,number,state,assignment_group,assigned_to,priority,opened_at,sla_due&sysparm_limit=100&sysparm_display_value=true

Step 2: Identify Assignment Group Bottlenecks

Find groups with disproportionately high task volumes or aging tasks.

Using MCP:

Tool: SN-Execute-Background-Script
Parameters:
  description: Identify bottleneck assignment groups
  script: |
    var bottlenecks = [];

    var ga = new GlideAggregate('task');
    ga.addQuery('active', true);
    ga.addQuery('assignment_group', 'ISNOTEMPTY', '');
    ga.addAggregate('COUNT');
    ga.addAggregate('AVG', 'reassignment_count');
    ga.groupBy('assignment_group');
    ga.orderByAggregate('COUNT', 'DESC');
    ga.query();

    while (ga.next()) {
      var groupId = ga.assignment_group.toString();
      var count = parseInt(ga.getAggregate('COUNT'));

      // Get average age of active tasks
      var ageGa = new GlideAggregate('task');
      ageGa.addQuery('active', true);
      ageGa.addQuery('assignment_group', groupId);
      ageGa.addAggregate('AVG', 'sys_mod_count');
      ageGa.query();

      var avgAge = 0;
      if (ageGa.next()) {
        avgAge = parseInt(ageGa.getAggregate('AVG', 'sys_mod_count'));
      }

      // Get group member count
      var members = new GlideAggregate('sys_user_grmember');
      members.addQuery('group', groupId);
      members.addQuery('user.active', true);
      members.addAggregate('COUNT');
      members.query();
      var memberCount = 0;
      if (members.next()) memberCount = parseInt(members.getAggregate('COUNT'));

      bottlenecks.push({
        group: ga.assignment_group.getDisplayValue(),
        active_tasks: count,
        active_members: memberCount,
        tasks_per_person: memberCount > 0 ? (count / memberCount).toFixed(1) : 'N/A',
        avg_reassignments: parseFloat(ga.getAggregate('AVG', 'reassignment_count')).toFixed(1)
      });
    }

    // Sort by tasks per person descending
    bottlenecks.sort(function(a, b) {
      return parseFloat(b.tasks_per_person) - parseFloat(a.tasks_per_person);
    });

    gs.info(JSON.stringify(bottlenecks.slice(0, 20), null, 2));

Step 3: Predict SLA Breaches

Analyze task SLA records to identify tasks at risk of breaching.

Using MCP:

Tool: SN-Query-Table
Parameters:
  table_name: task_sla
  query: stage=in_progress^has_breached=false^planned_end_time<=javascript:gs.hoursAgoEnd(-24)
  fields: sys_id,task,task.number,task.short_description,task.assignment_group,task.assigned_to,task.priority,sla,planned_end_time,percentage,business_percentage,stage
  limit: 50
  order_by: planned_end_time

**Using REST A

阅读完整来源 ↗