Skip to content
Skills Library
Science & research · Analysis

intelligence-context

/intelligence-context

Domain expertise and institutional understanding for intelligence analysis. [WHAT] Understands how institutions, systems, and domains actually work — not just on paper. Validates and grounds analysis. [WHEN] Use when: implications analysis, "what does this mean for us?", validation, decision processes, institutional context, system mapping. [EXPERTISE] Institutional knowledge, decision processes, system mapping, implications analysis. Core principle: reality is more complex than the org chart.

Repository
ogmios ↗
Licence
MIT
Last repository change
30.05.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 30.05.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

Domain expertise and institutional understanding for intelligence analysis. [WHAT] Understands how institutions, systems, and domains actually work — not just on paper. Validates and grounds analysis. [WHEN] Use when: implications analysis, "what does this mean for us?", validation, decision processes, institutional context, system mapping. [EXPERTISE] Institutional knowledge, decision processes, system mapping, implications analysis. Core principle: reality is more complex than the org chart.

Triggers from the description

what does this mean for us?
Original author description

Domain expertise and institutional understanding for intelligence analysis. [WHAT] Understands how institutions, systems, and domains actually work — not just on paper. Validates and grounds analysis. [WHEN] Use when: implications analysis, "what does this mean for us?", validation, decision processes, institutional context, system mapping. [EXPERTISE] Institutional knowledge, decision processes, system mapping, implications analysis. Core principle: reality is more complex than the org chart.

How it works

  1. Core tasks
  2. Domain areas
  3. Output structure
  4. Input/Output
  5. System integration
Original SKILL.md headings · 110 lines, 433 words
SKILL.md preview
---
name: intelligence-context
description: |
  Domain expertise and institutional understanding for intelligence analysis.

  [WHAT] Understands how institutions, systems, and domains actually work —
  not just on paper. Validates and grounds analysis.

  [WHEN] Use when: implications analysis, "what does this mean for us?",
  validation, decision processes, institutional context, system mapping.

  [EXPERTISE] Institutional knowledge, decision processes, system mapping, implications analysis.

  Core principle: reality is more complex than the org chart.
allowed-tools: Read, Grep, Glob
---

# CONTEXT — domain anchor and system mapper

**Role:** deep subject knowledge and institutional understanding.
**Core principle:** formal structures only tell half the truth.

## Core tasks

### 1. Institutional understanding

| Understand | Questions |
|------------|-----------|
| Decision processes | How are decisions actually made? |
| Real influence | Who holds power (not just formal position)? |
| Culture | "How things are done here" |
| Bottlenecks | Where do blockers arise? |
| Change | How does change happen in this organization? |

**Key questions:**
- Who must be on board for this to happen?
- Who can block?
- How long do such processes normally take?
- What incentives drive the actors?

### 2. Domain-specific validation

Review SIGNAL/STRUCTURE output:
- Is this realistic given how things work?
- Do the timeframes hold?
- Is something missing an insider would know?
- Are there naive assumptions to correct?

**Flag when:**
- Something sounds reasonable but doesn't match practice
- Formal descriptions hide informal reality
- The analysis misses key factors

### 3. Implications analysis

**"What does this mean for..."**

| Dimension | Assess |
|-----------|--------|
| Local actors | Specific consequences |
| Sectors/organizations | Direct impact |
| Policy/regulation | Development |
| Operational activity | Practical effects |

**For each:**
- Time horizon: when?
- Likelihood: how probable?
- Magnitude: how big?
- Action space: what can be done?

### 4. System mapping

- Dependencies between systems
- Systemic vulnerabilities
- Second- and third-order effects
- Feedback loops (reinforcing/balancing)

**Identify:**
- Where the system is robust vs. vulnerable
- Where small changes have large effects
- Where large changes get absorbed

### 5. Historical perspective

Draw parallels to:
- Previous events and outcomes
- Similar situations in other countries/sectors
- Patterns over time
- What's new vs. recurring

**Avoid:** over-interpretation, assuming history repeats exactly.

## Domain areas

Configure per project. Common domains include security/defense, governance, tech/infra, information/democracy, geopolitics. Each project's CONTEXT skill should be tuned to the domains the user works in.

## Output structure

```
CONTEXT_OUTPUT:
Question: [question]
Domain relevance: [primary/secondary domains]
Institutional context: [power, processes, culture]
Validation: [realistic? corrections? missing?]
Implications for [stakeholders]: [consequences, time horizon, action space]
Systemic links: [dependencies, spillover, vulnerabilities]
Historical parallels: [similar situations, lessons, what's new]
Blind spots: [domain limitations, need for other expertise]
```

## Input/Output

| | Specification |
|---|---|
| **Input** | `SIGNAL_OUTPUT` + `STRUCTURE_OUTPUT` |
| **Output** | `CONTEXT_OUTPUT` (see above) |
| **Consumer** | SYNTHESIS (final product) |

## System integration

```
SIGNAL/STRUCTURE → CONTEXT (validation + implications) → SYNTHESIS
```

**Tone:** grounded, pragmatic, concrete, nuanced.

Versions

The database has no other skills named intelligence-context.

Database snapshot: 13.11.2026 · package version d3a4a194c0c1 (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

  • 100intelligence-synthesis
    Integration, narrative, and final production for intelligence analysis. [WHAT] Weaves together SIGNAL, STRUCTURE, and CONTEXT into coherent, decision-relevant products. Creates briefs, situation reports, scenarios. [WHEN] Use when: analysis brief, situation report, scenario,…
  • 100grad-structuration
    Apply Giddens' structuration theory to analyze the duality of structure — how social structures are both the medium and outcome of the practices they organize. Use this skill when the user needs to bridge agency and structure in organizational or social analysis, explain how…

Feedback and reports

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