Skip to content
Skills Library
Programming · Writing

system-mapping

/system-mapping

Map systems with diagrams—components, data flows, feedback loops, and causal relationships. Use for architecture understanding or stakeholder communication. Triggers: "system map", "architecture diagram", "data flow", "C4", "how does this fit together".

Licence
MIT
Last repository change
20.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Map systems with diagrams—components, data flows, feedback loops, and causal relationships. Use for architecture understanding or stakeholder communication. Triggers: "system map", "architecture diagram", "data flow", "C4", "how does this fit together".

Triggers from the description

system maparchitecture diagramdata flowhow does this fit together
Original author description

Map systems with diagrams—components, data flows, feedback loops, and causal relationships. Use for architecture understanding or stakeholder communication. Triggers: "system map", "architecture diagram", "data flow", "C4", "how does this fit together".

How it works

  1. When to use
  2. When not to use
  3. Workflow
  4. Diagram tips
  5. Output template
  6. Related skills
Original SKILL.md headings · 51 lines, 205 words
SKILL.md preview
---
name: system-mapping
description: Map systems with diagrams—components, data flows, feedback loops, and causal relationships. Use for architecture understanding or stakeholder communication. Triggers: "system map", "architecture diagram", "data flow", "C4", "how does this fit together".
---

# System Mapping

Lightweight system mapping before deep implementation or refactor. Produces diagrams and narrative that clarify boundaries and dependencies.

## When to use

- Onboarding to unfamiliar codebase or pipeline
- Planning integration between services
- Explaining credit/ML/data flows to stakeholders

## When not to use

- Formal ADR decision (use `architecture-decision-records`)
- Auto-generating code from diagram

## Workflow

1. **Scope** — system boundary; actors; in/out of scope
2. **Components** — services, stores, queues, humans, external APIs
3. **Flows** — primary happy path; note sync vs async
4. **Feedback** — loops, retries, batch vs realtime
5. **Risks** — single points of failure, PII paths, manual steps
6. **Diagram** — Mermaid or C4-style; keep readable in markdown

## Diagram tips

- Start context/container level; drill to component only where needed
- Label data classifications on flows with sensitive data
- Version diagram with date in doc title or footer

## Output template

```markdown
## System map: [name]
- **Purpose:**
- **Actors:**
- **Components:** (table: name, role, owner)
- **Primary flows:**
- **Diagram:** (mermaid block)
- **Open questions:**
```

## Related skills

- `architecture-decision-records` — record resulting decisions
- `doubt-driven-review` — challenge critical assumptions
- `internal-credit-train-lifecycle` — credit platform context (if available)

*Clean-room system mapping workflow.*

Versions

RepositoryScoreLicence
This page · charlieviettq/awesome-agent-skill100MIT
charlieviettq/awesome-agent-skill100MIT

Database snapshot: 13.11.2026 · package version 3d40b4913428 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100systems-thinking
    Analyze complex problems through feedback loops, system dynamics, causal relationships, and leverage points to understand WHY a system behaves the way it does. Use when the user asks to map feedback loops, trace causal chains, identify why a problem keeps recurring, find…
  • 100c4-architecture
    Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include…
  • 100architecture-diagram
    This skill should be used when the user asks to "create a diagram", "make an architecture diagram", "design a system diagram", "draw an architecture", "create a technical diagram", "make a deployment diagram", "visualize infrastructure", "create a data flow diagram", "draw…
  • 80intelligence/systems-thinking
    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.
  • 100architecture-diagram
    Create or update architecture and flow diagrams for agent-desktop's docs site in apps/docs. Use when a docs page needs a diagram of components, data flow, or a command pipeline, or when an existing diagram in apps/docs/public/desktop/diagrams changes.
  • 100c4-architecture
    Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, or generate context/container/component/deployment diagrams.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.