Skip to content
Back to skills

Systems Thinking

ASecurity

Use when reasoning about architecture, holistic analysis, feedback loops, or emergent behavior — sees components, connections, feedback loops, and emergent properties to prevent the tunnel vision of analyzing parts in isolation. Default skill for Starlight Architect and Starlight Prime.

  • 10 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 11, 2026
ai-agents

Security analysis

A100/100

Scanned June 11, 2026

npx -y skills add frankxai/Starlight-Intelligence-System --skill systems-thinking --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Systems Thinking?

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

Security grade badge for Systems Thinking
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/frankxai-systems-thinking/badge)](https://www.skillsdirectory.com/skills/frankxai-systems-thinking)

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: intelligence/systems-thinking
description: Use when reasoning about architecture, holistic analysis, feedback loops, or emergent behavior — sees components, connections, feedback loops, and emergent properties to prevent the tunnel vision of analyzing parts in isolation. Default skill for Starlight Architect and Starlight Prime.
type: substrate
---

# Systems Thinking

> *"Everything is connected. See the connections, see the truth."*

## When This Skill Activates

- Architecture discussions, holistic analysis, understanding emergent behavior
- Keywords: "system", "architecture", "holistic", "feedback", "emergent", "ecosystem"
- Default for: Starlight Architect, Starlight Prime

## What This Skill Does

Enables holistic analysis that sees components, connections, feedback loops, and emergent properties. Prevents the tunnel vision of looking at parts in isolation.

## Procedures

### Procedure 1: System Mapping

1. Identify all components in the system
2. Map connections between components (data, control, dependency)
3. Identify feedback loops (reinforcing and balancing)
4. Find leverage points (where small changes have big effects)
5. Identify emergent properties (what the whole does that parts don't)
6. Document system boundaries (what's inside vs. outside)

### Procedure 2: Impact Analysis

1. Identify the proposed change
2. Trace first-order effects (direct impacts)
3. Trace second-order effects (impacts of impacts)
4. Trace third-order effects (if significant)
5. Check for unintended consequences
6. Identify affected feedback loops
7. Assess net system impact

### Procedure 3: Ecosystem View

1. Map the FrankX ecosystem: Starlight, ACOS, Arcanea, AI-Ops
2. Identify shared resources and dependencies
3. Find integration points and gaps
4. Assess ecosystem health (is it balanced? growing?)
5. Identify opportunities for better connection
6. Recommend ecosystem-level improvements

## Integration Points

- **Vault:** Technical Vault (system patterns), Wisdom Vault (system principles)
- **Agents:** Architect (primary), Prime (ecosystem), All (system awareness)
- **Transmissions:** All channels (ecosystem-wide implications)

## Quality Criteria

- Did you consider the whole system, not just the part being changed?
- Are feedback loops identified?
- Are second-order effects considered?
- Is the ecosystem perspective included?

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…