report-agent-risk-data

Populate data_risk metadata on span types for Prefactor-instrumented agents via SDK or CLI.

3|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/prefactordev/typescript-sdk --skill report-agent-risk-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-agent-risk-data
Source: https://github.com/prefactordev/typescript-sdk/tree/main/skills/report-agent-risk-data
Command: npx skills add https://github.com/prefactordev/typescript-sdk --skill report-agent-risk-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use when an agent is instrumented with Prefactor and you need to populate data_risk metadata on its span types to enable compliance tracking and data governance.

Core Features & Use Cases

  • Discover, map, and populate action_profile fields for each span type to reflect data handling, with an emphasis on risk categorization and GDPR considerations.
  • Validate and deliver the data_risk schema through the agent's SDK or CLI, and verify the registered schema_version includes data_risk for all span types.

Quick Start

Run the risk data workflow on an instrumented agent to populate span-type data_risk fields.

Frequently Asked Questions about report-agent-risk-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I populate data risk metadata on agent spans for compliance tracking?

Populating data risk metadata involves analyzing span definitions and filling action_profile and data_categories fields for each span type. This enables compliance tracking and data governance for agents instrumented with Prefactor.

What is data risk categorization for agent spans and when do I need it?

Data risk categorization maps input and output data categories to reflect data handling with an emphasis on risk and GDPR considerations. You need it when your agent requires compliance tracking and data governance instrumentation.

Does Prefactor instrumentation support GDPR data governance requirements?

Prefactor instrumentation supports GDPR considerations by populating action_profile fields for each span type to reflect data handling. This categorization enables governance and compliance tracking across span discovery and data mapping.

How do I validate and deliver the data risk schema through an agent SDK or CLI?

You validate and deliver the data risk schema through the agent's SDK or CLI after populating action_profile and data_categories. You must then verify that the registered schema_version includes data_risk for all span types.

What are the limitations of populating risk data without verifying schema version registration?

Without verifying schema version registration, your data_risk metadata may not be officially recognized for all span types. Verifying the registered schema_version ensures your compliance tracking and governance instrumentation are valid and complete.