Individual skill

ai-safety

Practice AI safety across the lifecycle — risk assessment, alignment concepts, evaluation, deployment safeguards, and governance. Use when building or deploying AI systems responsibly.

skills/ai-safety/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# AI Safety

AI safety is the practice of building systems that do what we intend, don't cause unintended harm, 
and remain under meaningful human control. It spans technical work (alignment, evaluation, 
robustness) and governance (policies, oversight, accountability) — this skill covers both at a 
practitioner level.

## Overview

Think in layers. Technical: train models to follow intent faithfully (alignment), test for 
dangerous capabilities and failure modes (evaluation), harden against adversaries (robustness), and 
keep humans meaningfully in control of consequential actions (oversight). Organizational: risk 
assessments before deployment, clear ownership, incident response plans, and honest communication 
about limitations. Safety isn't a feature added at the end — it's a property of how you build.
Back to top