remove

Remove elements from Dethernety threat models with dependency checking.

2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/dether-net/dethernety-oss --skill remove
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remove
Source: https://github.com/dether-net/dethernety-oss/tree/main/apps/dethereal/skills/remove
Command: npx skills add https://github.com/dether-net/dethernety-oss --skill remove

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables users to remove elements from a Dethernety threat model while ensuring that dependencies are checked and handled appropriately.

Core Features & Use Cases

  • Dependency Checking: Ensures that removal of an element does not disrupt the model's integrity.
  • Element Identification: Identifies elements to remove based on name or ID, even in cases of ambiguity.
  • Visual Modeling: Operates within the Dethernety platform's graph-native threat modeling environment.
  • Use Case: When a component or data flow is no longer relevant or has been replaced, this Skill can be used to remove it from the model, ensuring that the threat model remains accurate and up-to-date.

Quick Start

Use the 'remove' skill to remove the element 'API Server' from the threat model.

Frequently Asked Questions about remove

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

FAQPage Schema
How do I remove a component from a threat model without breaking dependencies?

To remove an element from a threat model, this Skill performs dependency checking before deletion. It identifies components, data flows, and boundaries by name or ID to ensure removal does not disrupt the model's integrity.

Can I delete an element from a threat model using its name instead of an ID?

Yes, you can delete an element from a threat model using its name instead of an ID. The Skill identifies elements by name or ID, handling ambiguity appropriately to ensure the correct component or data flow is removed.

Does removing data flows and boundaries from a Dethernety threat model require any specific setup?

Removing data flows and boundaries from a Dethernety threat model requires the Dethernety platform with model resolution and attribute file management capabilities. The graph-native environment must be set up to execute the element removal.

What happens to threat model integrity when I remove a component?

When you remove a component, threat model integrity is preserved through dependency checking. The Skill evaluates existing connections and relationships before deletion to ensure the removal does not disrupt the overall structure.

Why should I use dependency checking before removing elements from a threat model?

You should use dependency checking before removing elements from a threat model to prevent structural disruption. It verifies that deleting a component, data flow, or boundary will not invalidate existing relationships and keeps the model accurate.

How do I clean up outdated components in a threat model?

To clean up outdated components in a threat model, use the remove Skill to delete irrelevant or replaced elements. It handles dependency checking during removal to keep your threat model accurate and up-to-date.