本文へ移動
cccskills
無料GitHub で公開

focus-a-model-of-sensemaking

Use for sensemaking, frame revision, anomaly handling, questioning strategy, and ambiguity diagnosis with the Data/Frame model before action is chosen. NOT for deterministic classification, settled execution planning, or situations where the frame is already stable.

インストール方法を見る

含まれるファイル(15)

  • SKILL.md6.1 KB
  • _book_identity.json4.3 KB
  • _raw_response.md105.3 KB
  • CHANGELOG.md819 B
  • diagrams/01_stateDiagram-v2_sensemaking_state_machine-_fra.md2.1 KB
  • diagrams/02_flowchart_decision_framework-_anomaly_de.md2.3 KB
  • diagrams/03_mindmap_focus_sensemaking_model-_knowl.md2.5 KB
  • diagrams/INDEX.md1020 B
  • references/data-frame-reciprocity-in-agent-systems.md9.4 KB
  • references/expert-questioning-strategies.md18.8 KB
  • references/fragmentary-mental-models-for-agents.md14.2 KB
  • references/frame-elaboration-vs-frame-comparison.md19.4 KB
  • references/INDEX.md1.1 KB
  • references/sensemaking-decision-making-separation.md15.3 KB
  • references/sensemaking-triggers-and-anomaly-detection.md20.8 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

FOCUS: A Model of Sensemaking

Source basis: the Data/Frame model from Klein Associates on how people build, test, preserve, and replace interpretive frames under ambiguity.

When to Use

  • An agent or analyst has conflicting cues and is at risk of committing too early.
  • You need to separate situation understanding from downstream decision-making.
  • A system keeps explaining away anomalies instead of updating its interpretation.
  • You are designing question-generation behavior for ambiguous, evolving situations.
  • You need to decide whether to store comprehensive models or fragmentary domain patterns.

NOT for

  • Simple classification, retrieval, or pattern matching where the situation is already clear.
  • Pure decision optimization problems where the frame is settled and only action choice remains.
  • "Ask more questions" advice that ignores the current interpretive frame and its assumptions.

Decision Points

  1. Name the current frame. If you cannot state the working interpretation, you are not ready to reason about anomalies.
  2. Decide which of the six functions is appropriate: elaborate, question, preserve, compare, seek, or re-frame.
  3. Check whether anomaly handling is still healthy or has turned into preservation-driven fixation.
  4. Set an explicit gate for moving from sensemaking to decision-making.

Decision Flow

flowchart TD
  A[Ambiguous or unstable situation] --> B[Name current frame]
  B --> C{Which function fits now?}
  C -->|Elaborate| D[Add detail within current frame]
  C -->|Question| E[Test assumptions inside the frame]
  C -->|Preserve| F[Handle minor inconsistency cheaply]
  C -->|Compare| G[Assess competing frames]
  C -->|Seek| H[Gather evidence to stress-test the frame]
  C -->|Re-frame| I[Replace the active interpretation]
  D --> J{Anomalies accumulating?}
  E --> J
  F --> J
  G --> J
  H --> J
  I --> K[Set explicit transition to decision-making]
  J -->|Yes| G
  J -->|No| K

Working Model

  • Data and frame are reciprocal. The frame tells you what matters, and the data can confirm, strain, or break that frame.
  • Experts do not rely on one giant world model. They use fragmentary mental models: local patterns, causal snippets, and heuristics assembled when needed.
  • Expertise shows up more in better knowledge structures and better discipline between sensemaking and deciding than in a totally different reasoning algorithm.
  • Preserving is necessary but dangerous. It handles small inconsistencies cheaply, but it is also where fixation usually hides.
  • Good questions target the assumptions inside the current frame, not just missing facts on the surface.

Failure Modes

  • Treating the first plausible frame as settled truth and explaining away every later anomaly.
  • Moving into action planning before the situation model is coherent enough to trust.
  • Demanding a complete model of the environment instead of using fragmentary patterns that can be assembled just in time.
  • Asking only data-seeking questions and never assumption-challenging questions.
  • Treating each anomaly independently instead of tracking whether anomalies are accumulating into a reframing signal.

Anti-Patterns and Shibboleths

  • Anti-pattern: jumping from ambiguity straight into action planning with no named frame.
  • Anti-pattern: calling every extra data request "sensemaking" even when no frame assumptions are being tested.
  • Shibboleth: if the agent cannot say whether it is preserving, comparing, or reframing, it is probably improvising without a sensemaking method.

Worked Examples

  • An incident-response agent sees three weak signs that the current diagnosis is wrong but keeps preserving the original explanation. The fix is to force comparison against a competing frame once anomaly count crosses a threshold.
  • A research assistant keeps asking "what happened next?" but never "why would that actor do this?" The fix is to generate questions from frame assumptions, not from missing fields alone.

Fork Guidance

  • Stay in-process when you are refining one dominant frame and only need a few targeted questions.
  • Fork one subagent per competing frame when ambiguity is real and you want independent frame comparisons before deciding.

Quality Gates

  • The active frame is stated explicitly.
  • The chosen sensemaking function is named rather than implied.
  • Anomaly handling includes a threshold for when comparison or reframing becomes mandatory.
  • Decision-making starts only after an explicit transition gate.
  • Questions test assumptions inside the frame, not just facts outside it.

Reference Routing

  • references/data-frame-reciprocity-in-agent-systems.md: load when designing the loop between current interpretation and next evidence sought.
  • references/fragmentary-mental-models-for-agents.md: load when choosing what kind of knowledge structures to give the system.
  • references/sensemaking-decision-making-separation.md: load when action bias is collapsing understanding and decision into one phase.
  • references/expert-questioning-strategies.md: load when question quality, not question quantity, is the real bottleneck.
  • references/frame-elaboration-vs-frame-comparison.md: load when the system is stuck preserving one frame for too long.
  • references/sensemaking-triggers-and-anomaly-detection.md: load when you need criteria for when deliberate sensemaking should start.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Expert in 2000s-era music visualization (Milkdrop, AVS, Geiss) and modern WebGL implementations. Specializes in Butterchurn integration, Web Audio API AnalyserNode FFT data, GLSL shaders for audio-reactive visuals, and psychedelic generative art. Activate on "Milkdrop", "music visualization", "WebGL visualizer", "Butterchurn", "audio reactive", "FFT visualization", "spectrum analyzer". NOT for simple bar charts/waveforms (use basic canvas), video editing, or non-audio visuals.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

Expert legal research agent for finding and scraping expungement data state by state. Knows authoritative sources, URL patterns, Firecrawl configuration, and 2026 legal landscape.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

Expert in 3D computer vision labeling tools, workflows, and AI-assisted annotation for LiDAR, point clouds, and sensor fusion. Covers SAM4D/Point-SAM, human-in-the-loop architectures, and vertical-specific training strategies. Activate on '3D labeling', 'point cloud annotation', 'LiDAR labeling', 'SAM 3D', 'SAM4D', 'sensor fusion annotation', '3D bounding box', 'semantic segmentation point cloud'. NOT for 2D image labeling (use clip-aware-embeddings), general ML training (use ml-engineer), video annotation without 3D (use computer-vision-pipeline), or VLM prompt engineering (use prompt-engineer).

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

Apply crisis decision-making research to agent routing, uncertainty triage, and coordination failure analysis in time-pressured systems. Use when diagnosing handoff failures, analytical paralysis, or expert judgment under incomplete information. NOT for routine coding, simple CRUD design, or static single-agent tasks with complete information.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

Use for insight, reframing, contradiction, impasse, and anomaly-driven problem solving when execution effort no longer helps. NOT for routine optimization, error correction, or well-specified tasks with known solution paths.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

Apply cognitive task analysis to expert work that depends on perceptual cues, branching judgment, and recurring monitoring loops. Use when decomposing expert capability into agent structure, simulation design, or validation interviews. NOT for ordinary step-by-step SOP capture or simple pipelines with no tacit cue layer.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月12日 更新

curiositech のスキルをすべて見る

このスキルの問題を報告する