Agent skill

Stpa Step4 Loss Scenarios

by sandgardenhq in sandgardenhq/sgai

STPA Step 4 - Identify Loss Scenarios by tracing causal pathways back through control loops to understand why UCAs might occur.

Custom licenceAuto-check passed

Install Stpa Step4 Loss Scenarios

skills CLI
$ npx skills add sandgardenhq/sgai --skill stpa-step4-loss-scenarios -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sandgardenhq/sgai stpa-step4-loss-scenarios --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sandgardenhq/sgai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cmd/sgai/skel/.sgai/skills/stpa/stpa-step4-loss-scenarios .claude/skills/stpa-step4-loss-scenarios && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
stpa-step4-loss-scenarios
GitHub stars
137
Token cost
~1.9k tokens
SKILL.md length
721 words
Files
1
Skills in repo
53
Repo updated
First seen
Licence
Custom licence

At a glance

STPA Step 4 - Identify Loss Scenarios by tracing causal pathways back through control loops to understand why UCAs might occur.

  • Works in 3 steps: Trace back through the control structure… → Identify causal factors at each level → Develop recommendations to prevent or…
  • SKILL.md covers Objective, Announce at Start, Two Types of Scenarios and Causal Factor Categories, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Stpa Step4 Loss Scenarios is an agent skill from sandgardenhq/sgai. STPA Step 4 - Identify Loss Scenarios by tracing causal pathways back through control loops to understand why UCAs might occur. After completing STPA Step 3. When you need to understand WHY unsafe control actions might happen. When developing recommendations and mitigations.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Sandgarden AI Software Factory.

Example prompts

  • “/stpa-step4-loss-scenarios”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Trace back through the control structure to find why it might occur
  2. Identify causal factors at each level
  3. Develop recommendations to prevent or mitigate

What it can do on your machine

Read from SKILL.md and the folder at commit 9efbb7b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Stpa Step4 Loss Scenarios loads about 1.9k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 721 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 721 words (~1,856 tokens).

“For each Unsafe Control Action (UCA) identified in Step 3:”

— opening of SKILL.md by sandgardenhq, Custom licence
name
stpa-step4-loss-scenarios
metadata.tags
stpa, safety, loss-scenarios, causal-analysis, mitigations

Read the full SKILL.md on GitHub

Files

Just SKILL.md in cmd/sgai/skel/.sgai/skills/stpa/stpa-step4-loss-scenarios of sandgardenhq/sgai.

Open the folder on GitHubat commit 9efbb7b

Compare with similar skills

Stpa Step4 Loss Scenarios next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Stpa Step4 Loss Scenarios compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stpa Step4 Loss Scenarios this skillsandgardenhq/sgai137—~1.9kAutomated safety check: PassCustom licence
Observe Traceruvnet/ruflo74k—~522Automated safety check: NotesMIT
Distributed Tracingwshobson/agents40k12 repos~527Automated safety check: PassMIT
Tracezereight/gitlab-mcp2k1 repos~412Automated safety check: PassMIT
Arize Tracegithub/awesome-copilot40k1 repos~5.9kAutomated safety check: NotesMIT
Evidence-Driven TraceYeachan-Heo/oh-my-claudecode40k—~2.6kAutomated safety check: PassMIT

Similar skills

  • Observe Trace

    ruvnet/ruflo

    Trace agent execution by collecting spans and building a trace tree for a task

    74k GitHub stars~522 tokensUpdated yesterday
    Auto-check: notes
  • Distributed Tracing

    wshobson/agents

    Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks.

    40k GitHub starsUsed in 12 repos~527 tokens
    DevOps & CloudAuto-check passed
  • Trace

    zereight/gitlab-mcp

    Evidence-driven tracing with competing hypotheses in parallel.

    2k GitHub starsUsed in 1 repo~412 tokens
    DevelopmentAuto-check passed
  • Arize Trace

    github/awesome-copilot

    Official

    Downloads, exports, and inspects existing Arize traces and spans to understand what an LLM app is doing or debug runtime issues.

    40k GitHub starsUsed in 1 repo~5.9k tokens
    DevelopmentAuto-check: notes
  • Evidence-Driven Trace

    Yeachan-Heo/oh-my-claudecode

    Explains why something happened by generating competing hypotheses, gathering evidence in parallel, ranking explanations and proposing the next discriminating probe.

    40k GitHub stars~2.6k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Scenario

    scenario-labs/skills

    A skill your agent uses when connecting an AI agent to Scenario (scenario.com) through MCP, or when a task involves generating images, video, 3D, audio, sprites, textures, or game assets.

    946 GitHub stars~6.2k tokensUpdated yesterday
    Game DevelopmentAuto-check passed

More from sandgardenhq/sgai

All 53 skills in this repo
  • Root Cause Tracing

    sandgardenhq/sgai

    A skill your agent uses when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation…

    137 GitHub starsUsed in 4 repos~1.4k tokens
    Auto-check passed
  • Condition Based Waiting

    sandgardenhq/sgai

    A skill your agent uses when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state…

    137 GitHub starsUsed in 3 repos~933 tokens
    Auto-check passed
  • Defense In Depth

    sandgardenhq/sgai

    A skill your agent uses when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally…

    137 GitHub starsUsed in 3 repos~970 tokens
    Auto-check passed
  • Agent Native Architecture

    sandgardenhq/sgai

    Build AI agents using prompt-native architecture where features are defined in prompts, not code.

    137 GitHub stars~2k tokensUpdated 20 days ago
    Auto-check passed
  • Adhoc

    sandgardenhq/sgai

    Run and manage ad-hoc AI prompts in sgai workspaces without starting a full agentic session.

    137 GitHub stars~1.2k tokensUpdated 20 days ago
    Auto-check passed
  • You must use this skill when debugging web UI bugs or testing interactive components that require multi-step browser interactions.

    137 GitHub stars~3.7k tokensUpdated 20 days ago
    Auto-check passed

Questions about Stpa Step4 Loss Scenarios

What does Stpa Step4 Loss Scenarios do?

STPA Step 4 - Identify Loss Scenarios by tracing causal pathways back through control loops to understand why UCAs might occur. Stpa Step4 Loss Scenarios is an agent skill from sandgardenhq/sgai. STPA Step 4 - Identify Loss Scenarios by tracing causal pathways back through control loops to understand why UCAs might occur.

How do I install Stpa Step4 Loss Scenarios in Claude Code?

Run `npx skills add sandgardenhq/sgai --skill stpa-step4-loss-scenarios -a claude-code`. Or copy the skill folder (cmd/sgai/skel/.sgai/skills/stpa/stpa-step4-loss-scenarios in sandgardenhq/sgai) into .claude/skills/stpa-step4-loss-scenarios in your project. Claude Code loads it when a task matches its description.

How do I install Stpa Step4 Loss Scenarios in Codex?

Run `npx skills add sandgardenhq/sgai --skill stpa-step4-loss-scenarios -a codex`. Or copy the skill folder (cmd/sgai/skel/.sgai/skills/stpa/stpa-step4-loss-scenarios in sandgardenhq/sgai) into .agents/skills/stpa-step4-loss-scenarios in your project. Codex loads it when a task matches its description.

Can I use Stpa Step4 Loss Scenarios in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sandgardenhq/sgai --skill stpa-step4-loss-scenarios -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stpa-step4-loss-scenarios, .gemini/skills/stpa-step4-loss-scenarios, .github/skills/stpa-step4-loss-scenarios and .opencode/skills/stpa-step4-loss-scenarios in your project.

What does Stpa Step4 Loss Scenarios need to run?

SKILL.md names no scripts, command-line tools or credentials: Stpa Step4 Loss Scenarios is instructions for the agent only.

Does Stpa Step4 Loss Scenarios access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Stpa Step4 Loss Scenarios safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Stpa Step4 Loss Scenarios use?

Stpa Step4 Loss Scenarios has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Stpa Step4 Loss Scenarios use?

About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Stpa Step4 Loss Scenarios?

Skills that share tags, products or a category with Stpa Step4 Loss Scenarios: Observe Trace (ruvnet/ruflo, 74k stars), Distributed Tracing (wshobson/agents, 40k stars), Trace (zereight/gitlab-mcp, 2k stars) and Arize Trace (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stpa Step4 Loss Scenarios?

sandgardenhq (a GitHub organization) maintains it in sandgardenhq/sgai, which has 137 GitHub stars. The repository holds 53 skills in this directory. The repository was last updated on September 21, 2026.

Source: sandgardenhq/sgai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.