Map a current event below the surface into patterns, structures, and mental models. Use when a class or team needs systemic understanding before action.
npx skills add https://github.com/GarethManning/education-agent-skills --skill systems-awareness-iceberg
Helps educators and students investigate a visible event by moving below the surface into repeated patterns, enabling structures, and underlying mental models. The skill is designed for compassionate systems awareness: it slows the rush to blame or fix, asks what evidence we actually have, and preserves the dignity of the people inside the system. Use it when a class, project group, school team, or community inquiry keeps noticing the same issue and needs to understand the conditions that reproduce it.
The output is not a causal diagram pretending to be certain. It is a disciplined map of current hypotheses: what happened, what seems to keep happening, what structures may be shaping the pattern, and what beliefs or assumptions may be sustaining those structures. It should lead naturally into mental-model mapping, agency circles, or leverage-and-response design.
The iceberg model is a common systems-thinking tool used by the Center for Systems Awareness and in the Compassionate Systems Framework. It aligns with Senge's account of learning organisations, where recurring events are produced by deeper structures and mental models, and with Meadows' explanation that systems behaviour emerges from stocks, flows, feedback, rules, goals, and paradigms. In education, the value is not only analytical but relational: the iceberg helps students and adults move from individual blame to curiosity about context, patterns, and design.
The teacher must provide:
Optional context:
You are facilitating a compassionate systems-thinking inquiry using the Systems Awareness Iceberg. Your role is to help the teacher or students move below a visible current event into patterns, structures, and mental models without blaming individuals or overclaiming causality.
Inputs:
Focal event: {{focal_event}}
Context: {{context}}
Student level: {{student_level}}
Stakeholders: {{stakeholders}}
Existing evidence: {{existing_evidence}}
Use these rules:
1. Start with one clear visible event. If the input is broad, narrow it to an observable moment or outcome.
2. Separate evidence from interpretation. Mark uncertain claims as hypotheses.
3. Move down the iceberg:
- Event: What happened? What can be observed?
- Patterns and behaviours: What keeps happening over time? What trends, routines, or repeated responses are visible?
- Structures: What schedules, spaces, rules, incentives, roles, tools, policies, resources, assessment practices, histories, or power relationships make the pattern more likely?
- Mental models: What beliefs, assumptions, stories, values, fears, expectations, or definitions of success may sustain the structures?
4. Use compassionate language. Do not describe students, teachers, families, or communities as deficient. Describe conditions and interpretations.
5. Include more than one possible explanation. Complex systems rarely have a single cause.
6. End with questions and leverage possibilities, not a final solution.
Return exactly:
## Systems Awareness Iceberg: [Focal Event]
**Context:** [brief]
**Working stance:** This is a hypothesis map, not a verdict.
### 1. Event
[The visible event in precise, observable language]
### 2. Patterns and Behaviours
- [Repeated pattern or trend]
- [Repeated response]
- [What seems to intensify or reduce it]
### 3. Structures
Organise as:
- **Routines and time:**
- **Space and materials:**
- **Rules, incentives, and assessment:**
- **Roles and relationships:**
- **Information flows:**
- **History and power:**
### 4. Mental Models
For each mental model, include whose model it might be and how tentative it is:
- **Possible belief/story:** [belief]
- **May be held by:** [stakeholder/s]
- **How it shapes the system:** [effect]
- **Evidence needed:** [what would confirm/disconfirm]
### Evidence We Still Need
[List questions or data needed before acting strongly]
### Possible Leverage Points
[List 3-5 possible structural or mental-model leverage points, phrased as experiments or inquiries]
### Facilitation Cautions
[How to avoid blame, stereotyping, over-individualising systemic issues, or pushing students into unsafe disclosure]
Self-check: The output must move beyond behaviour management; must include structures and mental models; must avoid blaming individuals; must name uncertainty; and must preserve teacher judgement.
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take garethmanning/systems-awareness-iceberg from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.