Skip to content
Back to skills

Assess System Boundary

ASecurity

Define and challenge the system boundary: what actors, processes, externalities, timescales, and value assumptions are included or excluded.

  • 499 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 24, 2026
research

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill assess-system-boundary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Assess System Boundary?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Assess System Boundary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-assess-system-boundary/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-assess-system-boundary)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: assess-system-boundary
description: "Define and challenge the system boundary: what actors, processes, externalities, timescales, and value assumptions are included or excluded."
---

# assess-system-boundary
## Purpose
Define and challenge which actors, processes, externalities, timescales, and values are inside or outside a system boundary.
## Input contract
```yaml
required: [target_system, boundary_candidate]
optional: [actors, processes, externalities, time_horizon, value_assumptions]
constraints: [every inclusion and exclusion must be explicit]
```
## Procedure
1. Inventory actors, processes, externalities, and timescales.
2. Mark each item inside, outside, or contested under the candidate boundary.
3. Generate boundary alternatives and compare consequences for the research question.
## Output contract
```yaml
produces: [system_boundary, inclusion_exclusion_register, boundary_alternatives, consequence_map]
delta_fields: [findings, assumption_updates, uncertainties, decisions]
```
## Quality gates
- Boundary is reproducible from the register; contested items and value assumptions remain visible.
## Failure and counterexamples
Reject a boundary that hides material externalities or treats excluded stakeholders as irrelevant.
## Provenance map
- `critical-systems-heuristics/boundary-critique`: resolved.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…