MCP HubMCP Hub
스킬 목록으로 돌아가기

express-insight

pjt222
업데이트됨 Yesterday
1 조회
17
2
17
GitHub에서 보기
메타ai

정보

`express-insight` 스킬은 복잡하고 다중 도메인에 걸친 이해를 상호 연결된 본질을 유지하면서도 접근 가능하고 실행 가능한 방식으로 전달합니다. 이 스킬은 적절한 형식을 선택하고, 정직한 귀속과 함께 통찰력을 표현하며, 생산적인 피드백을 유도하는 구조화된 방법을 제공합니다. 개발자는 `integrate-gestalt` 이후에 이 스킬을 사용하여 전문가, 일반 담당자 또는 의사 결정권자에게 도메인 간 통찰력을 전달해야 합니다.

빠른 설치

Claude Code

추천
기본
npx skills add pjt222/agent-almanac -a claude-code
플러그인 명령대체
/plugin add https://github.com/pjt222/agent-almanac
Git 클론대체
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/express-insight

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Express Insight

Communicate a multi-domain gestalt so that it lands — preserving the relationships between domains, making the synthesis accessible to the audience, and being honest about where the integration simplifies or risks distortion. Expression is the final step of the synoptic cycle: without it, integrated understanding remains private and unactionable. The challenge is that language is linear but insights are not — this skill provides structures for communicating multi-dimensional understanding without reducing it to a single dimension.

When to Use

  • After integrate-gestalt has produced a cross-domain understanding that needs to be communicated
  • When a finding spans multiple domains and a single-domain framing would lose essential relationships
  • When the audience for an insight differs from the perspective that generated it
  • When an integrated understanding feels clear internally but resists straightforward expression
  • When a decision depends on seeing how multiple domains interact, not just what each domain says independently
  • When previous attempts to communicate a cross-domain finding were met with confusion or domain-specific pushback
  • When communicating findings from a synoptic-mind team session to stakeholders outside the team

Inputs

  • Required: An integrated insight (the output of integrate-gestalt or equivalent cross-domain synthesis)
  • Required: Audience — who receives this insight (domain specialists, generalists, decision-makers, or mixed)
  • Optional: Constraints on form (e.g., "must fit in a PR description", "needs to be a verbal summary")
  • Optional: The domains that were integrated (for explicit attribution)
  • Optional: Prior failed attempts to communicate this insight (what did not land)

Procedure

Step 1: Assess Audience

Determine who receives this insight and what they need from it. The same gestalt expressed to three different audiences should take three different forms.

  1. Identify the primary audience:
    • Domain specialists need their domain represented accurately — they will reject an insight that oversimplifies their field, even if the overall synthesis is correct
    • Generalists need the big picture — the relationships between domains matter more than the details within any single one
    • Decision-makers need actionable implications with trade-offs — they want to know what to do, what it costs, and what happens if they do nothing
    • Mixed audiences require layered communication: lead with the big picture, then provide domain-specific depth that specialists can verify
  2. Assess the audience's existing mental model:
    • What do they already understand about each domain involved?
    • What connections between domains will be new to them?
    • What assumptions might they hold that the insight challenges?
  3. Identify the trust requirement: how much justification does this audience need before accepting a cross-domain claim?
    • Specialists trust insight that respects their domain's rigor
    • Generalists trust insight that makes complexity navigable without oversimplifying
    • Decision-makers trust insight that honestly surfaces trade-offs rather than hiding them

Got: A clear picture of who the audience is, what they need, and what will make the insight credible to them. The audience assessment should influence every subsequent step.

If fail: If the audience is unknown or too broad to characterize, default to the mixed-audience approach: big picture first, domain depth on demand. Communicating to "everyone" is less effective than communicating to someone specific, but it is better than guessing wrong.

Step 2: Choose Form

Select the expression format that best serves the audience and the nature of the insight. Form is not decoration — it determines what the audience can perceive.

  1. Evaluate the four primary forms:

    FormStructureBest for
    NarrativeStory connecting domains — "when X happens in domain A, it creates Y in domain B, which means Z"Complex or novel insights where the audience needs to follow the reasoning path
    DiagramSpatial layout showing relationships — nodes are domain contributions, edges are connectionsStructural insights where the topology of relationships matters more than the sequence
    Comparison tableEach domain's perspective on the same issue in parallel columnsAnalytical audiences who want to verify each domain's contribution independently
    RecommendationActionable synthesis — "do X because domains A, B, and C converge on Y, with trade-off Z"Decision-makers who need to act, not just understand
  2. Match form to insight type:

    • If the insight is about a causal chain across domains, use narrative
    • If the insight is about structural relationships, use diagram
    • If the insight is about convergence or divergence between domains, use comparison table
    • If the insight is about what to do next, use recommendation
  3. Consider combining forms: a recommendation backed by a comparison table, or a narrative illustrated with a diagram. But lead with one primary form — cognitive load from multiple formats can obscure rather than clarify

  4. Account for medium constraints: a verbal summary cannot carry a comparison table; a commit message cannot carry a narrative. If the medium constrains form, adjust the form rather than forcing content into an incompatible container

Got: A chosen primary form (and optional secondary form) with a clear rationale tied to the audience and the nature of the insight.

If fail: If no form feels right, the insight may not yet be fully integrated. Return to integrate-gestalt — difficulty expressing often signals incomplete synthesis, not a communication problem.

Step 3: Express the Gestalt

Communicate the insight in the chosen form, explicitly noting what it integrates, where it simplifies, and what it enables.

  1. State the insight clearly — one to three sentences that capture the core understanding. This is the gestalt itself, not the supporting evidence
  2. Name the domains it integrates — explicitly list which domains contributed to this understanding. This is not attribution for credit; it is attribution for verification. Each named domain is an invitation: "check this against your expertise"
  3. Mark the simplifications — every multi-domain insight simplifies. State where:
    • Which domain-specific nuances were set aside?
    • Which relationships were treated as stronger or weaker than they might be?
    • What would a specialist in domain X want to add or qualify?
  4. State the emergent value — what does this insight enable that single-domain analysis does not?
    • What decision becomes possible that was not possible before?
    • What risk becomes visible that was hidden within individual domains?
    • What opportunity appears at the intersection that no single domain owns?
  5. Maintain the multi-domain texture — resist the pull to flatten the insight into one domain's language. If the insight integrates engineering and user experience, use both vocabularies. If it connects research and operations, preserve both framings. The texture is the insight
  6. Sequence for comprehension — even though the insight is non-linear, communication is sequential. Choose the entry point that gives the audience the best foothold: start with the domain they know best, then bridge outward into the unfamiliar domains. The first sentence determines whether the audience leans in or tunes out

Got: A communicated insight that the audience can understand, verify against their own expertise, and act on. The simplifications are visible, not hidden. The emergent value is clear.

If fail: If the expression feels like a list of domain contributions rather than an integrated whole, the gestalt has been decomposed during communication. Step back and re-express: start from what the combination reveals, not from what each domain says separately. The synthesis is the message, not the parts.

Step 4: Invite Challenge

State the strongest reason the insight might be wrong. Integrated insights can feel more certain than they are because they synthesize many inputs — convergence creates a sense of validity that may be unearned. This step is not a disclaimer appended for politeness; it is a structural component that makes the insight usable.

  1. Identify the weakest link — which domain connection in the insight is least well-supported? Where does the integration rely on analogy rather than evidence?
  2. Name the assumption at risk — what would need to be true for the insight to hold, and how confident are you that it is true?
  3. State the counter-insight — if someone with equal access to all the same domains reached a different conclusion, what would their strongest argument be?
  4. Frame challenge as valuable — make it clear that challenging the insight strengthens it. "The strongest objection I see is..." signals confidence and openness simultaneously
  5. Specify what would change your mind — name the evidence or argument that would revise or collapse the insight. This makes the insight falsifiable, not just persuasive

Got: An honest statement of uncertainty that increases rather than decreases the audience's trust. The insight is now challengeable — and therefore improvable.

If fail: If no weakness can be identified, that itself is a warning sign. All cross-domain insights involve translation between frameworks, and translation always loses something. If the loss is invisible, it has not been found yet, not avoided. Look harder at the domain boundaries — that is where hidden assumptions live. Common hiding places: shared metaphors that work differently in each domain, statistical correlations assumed to be causal across domain boundaries, and analogies that hold structurally but not quantitatively.

Validation

  • Audience was explicitly identified and their needs shaped the expression
  • Form was chosen based on insight type and audience, not habit or convenience
  • The insight was stated as a coherent whole, not decomposed into per-domain summaries
  • Contributing domains were named for verification, not just attribution
  • Simplifications were stated explicitly — what was set aside and what was approximated
  • Emergent value was articulated — what the integration enables that parts do not
  • Multi-domain vocabulary was preserved rather than flattened into one domain's language
  • Entry point was chosen for the audience's existing knowledge — starts where they are, bridges to where the insight goes
  • The strongest reason the insight might be wrong was stated
  • The insight is falsifiable — specific evidence or arguments that would revise it were named
  • A domain specialist reading their domain's contribution would recognize it as accurate, not caricatured

Pitfalls

  • Domain-by-domain reporting: Presenting each domain's contribution sequentially is not expressing an insight — it is presenting raw material. The insight is what emerges from the combination. Lead with the synthesis, then support with domain detail if needed
  • False certainty from convergence: When three domains all seem to point the same way, it feels like strong evidence. But if those domains share underlying assumptions or data sources, the convergence is less independent than it appears. Always check whether the domains are truly independent
  • Flattening to the audience's domain: When communicating to a specialist, the temptation is to translate the entire insight into their language. This makes it accessible but destroys the multi-domain nature. Preserve the texture — the unfamiliar vocabulary is not noise, it is signal
  • Skipping the challenge step: Omitting "here is why I might be wrong" feels like it makes the insight stronger. It does not. It makes the insight less trustworthy and less improvable. Epistemic honesty is a feature, not a weakness
  • Insight inflation: Claiming the synthesis reveals more than it does. A cross-domain observation is not automatically a breakthrough. Be precise about the scope: "this applies to X in context Y" is more valuable than "this changes everything"
  • Premature expression: Expressing before the gestalt is fully formed produces half-insights that sound integrated but collapse under scrutiny. If the expression keeps stalling, the problem is upstream in integrate-gestalt, not here
  • Hiding behind complexity: Using multi-domain vocabulary to sound sophisticated rather than to preserve genuine texture. If a simpler framing captures the same insight without losing relationships, use the simpler framing. Complexity should be necessary, not performative

Related Skills

  • integrate-gestalt — produces the insight that this skill expresses; express-insight is the communication phase of the synoptic cycle
  • argumentation — builds a logical case for a claim; express-insight communicates a perception. Argumentation says "here is why X is true"; express-insight says "here is what becomes visible when you look at A, B, and C together"
  • teach — transfers known, established knowledge; express-insight conveys emergent understanding just formed. Teaching transmits; expressing reveals
  • shine — channels authentic presence into communication; express-insight can use that radiance to carry multi-domain perception without losing warmth or honesty
  • expand-awareness — widens the perceptual field that makes integration possible; express-insight closes the cycle by communicating what that widened field revealed
  • adaptic — the meta-skill composing the full synoptic cycle; express-insight is the fifth and final step in the clear-open-perceive-integrate-express sequence

GitHub 저장소

pjt222/agent-almanac
경로: i18n/caveman-lite/skills/express-insight
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

연관 스킬

content-collections

메타

이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.

스킬 보기

polymarket

메타

이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.

스킬 보기

creating-opencode-plugins

메타

이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.

스킬 보기

sglang

메타

SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.

스킬 보기