safety-engineer
SolidEstablishes a tailored safety lifecycle from hazards through operational feedback and assurance evidence. Use when a system can create unacceptable harm.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- Agile-V
- Repository
- Agile-V/agile_v_skills
- Created
- 7 months ago
- Last Updated
- 1 weeks ago
- Language
- Python
- License
- CC-BY-SA-4.0
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
senior-ai-safety-engineer
Use when threat modeling an LLM or agent system, defending against prompt injection (direct and indirect), designing output safety pipelines, hardening tool use authorization, running an authorized red team set, classifying a system under EU AI Act / NIST AI RMF / ISO 42001, responding to an AI safety incident (jailbreak gone public, harmful output reported, system prompt leak), or evaluating training data privacy risk. Triggers: AI safety, LLM security, prompt injection, indirect prompt injection, jailbreak, output safety, content filter, moderation, model exfiltration, prompt extraction, system prompt leak, agent safety, tool safety, EU AI Act, NIST AI RMF, ISO 42001, OWASP LLM Top 10, red team AI, refusal, harmful content. Produces AI threat models, defense in depth diagrams, red team sets, output safety pipelines, tool authorization matrices, regulatory classification docs, incident response plans. Not for the agent loop itself, see senior-ai-agent-engineer.
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.
safety-compliance-scoping
Scope which safety and regulatory compliance frameworks plausibly apply to a system — functional safety standards, medical device classification pathways, industrial safety directives — based on its actual use case and failure consequence, before deep technical or product investment. Use early, whenever a system's use case touches health, safety, or regulated industrial contexts, to identify what compliance burden is coming rather than discovering it after the architecture is locked in. This produces a scoping map, not a certification — a qualified regulatory/compliance professional and, where relevant, legal counsel must own the actual compliance path.