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

express-insight

pjt222
업데이트됨 2 days ago
7 조회
17
2
17
GitHub에서 보기
메타ai

정보

이 기술은 복잡하고 다중 영역의 통찰력을 상호 연결성을 유지하면서도 접근 가능하고 실행 가능하게 전달하는 구조를 제공합니다. 적절한 형식을 선택하고, 명확한 출처 표시와 함께 통합된 이해를 제시하며, 건설적인 피드백을 유도하는 절차를 포함합니다. 개발자들은 `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

Say multi-domain gestalt so it lands — keep links between domains, make synthesis open to audience, be honest about where integration shrinks or risks distortion. Express is final step of synoptic cycle: without it, integrated understanding stays private and unactionable. Challenge is language is linear but insights are not — this skill gives shapes for talking multi-dimensional understanding without shrinking to single dimension.

When Use

  • After integrate-gestalt has made cross-domain understanding that needs to be said
  • When find spans many domains and single-domain frame would lose key links
  • When audience for insight differs from view that made it
  • When integrated understanding feels clear inside but resists plain talk
  • When pick depends on seeing how many domains touch, not just what each domain says alone
  • When prior tries to talk cross-domain find met with confusion or domain-specific pushback
  • When talking finds from synoptic-mind team session to stakeholders outside team

Inputs

  • Required: Integrated insight (output of integrate-gestalt or same cross-domain synthesis)
  • Required: Audience — who gets this insight (domain specialists, generalists, decision-makers, or mixed)
  • Optional: Limits on form (e.g., "must fit in PR description", "needs to be verbal summary")
  • Optional: Domains that were integrated (for clear credit)
  • Optional: Past failed tries to talk this insight (what did not land)

Steps

Step 1: Assess Audience

Figure who gets this insight and what they need from it. Same gestalt said to three different audiences should take three different forms.

  1. Spot main audience:
    • Domain specialists need their domain shown right — they will reject insight that oversimplifies their field, even if whole synthesis is right
    • Generalists need big picture — links between domains matter more than details inside any single one
    • Decision-makers need actionable implications with trade-offs — they want to know what to do, what it costs, what happens if they do nothing
    • Mixed audiences need layered talk: lead with big picture, then give domain-specific depth specialists can check
  2. Check audience existing mind-model:
    • What do they already know about each domain?
    • What links between domains will be new to them?
    • What assumptions might they hold that insight challenges?
  3. Spot trust need: how much backing does this audience need before they take cross-domain claim?
    • Specialists trust insight that respects their domain rigor
    • Generalists trust insight that makes complex stuff navigable without oversimplify
    • Decision-makers trust insight that honest shows trade-offs rather than hides them

Got: Clear picture of who audience is, what they need, what will make insight credible to them. Audience check should shape every later step.

If fail: Audience unknown or too broad to pin? Default to mixed-audience way: big picture first, domain depth on demand. Talking to "everyone" is less useful than talking to someone specific, but it is better than guessing wrong.

Step 2: Choose Form

Pick express format that best serves audience and nature of insight. Form is not decoration — it picks what audience can see.

  1. Check four main 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:

    • Insight is about causal chain across domains? Use narrative
    • Insight is about structural links? Use diagram
    • Insight is about convergence or divergence between domains? Use comparison table
    • Insight is about what to do next? Use recommendation
  3. Think mix forms: recommendation backed by comparison table, or narrative shown with diagram. But lead with one main form — cognitive load from many formats can hide rather than clear

  4. Account for medium limits: verbal summary can't carry comparison table; commit msg can't carry narrative. If medium limits form, tune form rather than forcing content into wrong container

Got: Picked main form (and optional second form) with clear reason tied to audience and nature of insight.

If fail: No form feels right? Insight may not yet be fully integrated. Go back to integrate-gestalt — hard express often signals thin synthesis, not talk problem.

Step 3: Express the Gestalt

Say insight in picked form, clear note what it integrates, where it shrinks, and what it enables.

  1. State insight clear — one to three sentences that catch core understanding. This is gestalt itself, not backing evidence
  2. Name domains it integrates — clear list which domains fed this understanding. This is not credit for credit; it is credit for check. Each named domain is invite: "check this vs your expertise"
  3. Mark shrinks — every multi-domain insight shrinks. State where:
    • Which domain-specific nuances were set aside?
    • Which links treated as stronger or weaker than they might be?
    • What would specialist in domain X want to add or qualify?
  4. State emergent value — what does this insight enable that single-domain analysis does not?
    • What pick becomes possible that was not before?
    • What risk becomes visible that was hidden inside single domains?
    • What chance shows at the crossing that no single domain owns?
  5. Keep multi-domain texture — resist pull to flatten insight into one domain language. If insight integrates engineering and UX, use both vocabs. If it links research and ops, keep both framings. Texture is the insight
  6. Sequence for grasp — even though insight is non-linear, talk is sequential. Pick entry point that gives audience best foothold: start with domain they know best, then bridge out into unfamiliar domains. First sentence picks whether audience leans in or tunes out

Got: Said insight audience can grasp, check vs own expertise, and act on. Shrinks are visible, not hidden. Emergent value clear.

If fail: Express feels like list of domain contributions rather than integrated whole? Gestalt got broken during talk. Step back and re-express: start from what combination shows, not from what each domain says apart. Synthesis is message, not parts.

Step 4: Invite Challenge

State strongest reason insight might be wrong. Integrated insights can feel more certain than they are since they blend many inputs — convergence gives sense of validity that may be unearned. This step is not disclaimer slapped on for polite; it is structural part that makes insight usable.

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

Got: Honest statement of uncertainty that raises rather than drops audience trust. Insight is now challengeable — and so improvable.

If fail: No weakness can be spotted? That itself is warn sign. All cross-domain insights need translation between frames, and translation always loses something. If loss invisible, it has not been found yet, not avoided. Look harder at domain edges — that is where hidden assumptions live. Common hide spots: shared metaphors that work differently in each domain, stat correlations assumed causal across domain edges, and analogies that hold structurally but not quantitatively.

Validation

  • Audience was clear named and their needs shaped express
  • Form was picked by insight type and audience, not habit or convenience
  • Insight stated as coherent whole, not broken into per-domain summaries
  • Contributing domains named for check, not just credit
  • Shrinks stated clear — what was set aside and what was approximated
  • Emergent value said — what integration enables that parts do not
  • Multi-domain vocab kept rather than flattened into one domain language
  • Entry point picked for audience existing knowledge — starts where they are, bridges to where insight goes
  • Strongest reason insight might be wrong was stated
  • Insight is falsifiable — specific evidence or arguments that would revise it were named
  • Domain specialist reading their domain contribution would know it as right, not caricatured

Pitfalls

  • Domain-by-domain report: Showing each domain contribution one by one is not expressing insight — it is showing raw stuff. Insight is what shows up from combo. Lead with synthesis, then back with domain detail if needed
  • False certainty from convergence: When three domains all seem to point same way, it feels like strong evidence. But if those domains share hidden assumptions or data sources, convergence is less independent than it looks. Always check whether domains truly independent
  • Flatten to audience domain: When talking to specialist, urge is to translate whole insight into their language. This makes it open but destroys multi-domain nature. Keep texture — unfamiliar vocab is not noise, it is signal
  • Skip challenge step: Leaving out "here is why I might be wrong" feels like it makes insight stronger. It does not. It makes insight less trustworthy and less improvable. Epistemic honesty is feature, not weakness
  • Insight inflation: Claim synthesis shows more than it does. Cross-domain watch is not auto-breakthrough. Be precise about scope: "this applies to X in context Y" is more valuable than "this changes everything"
  • Premature express: Express before gestalt fully formed gives half-insights that sound integrated but fall under scrutiny. If express keeps stalling, problem is upstream in integrate-gestalt, not here
  • Hide behind complex: Use multi-domain vocab to sound fancy rather than to keep real texture. If simpler frame catches same insight without losing links, use simpler frame. Complex should be needed, not performed

See Also

  • integrate-gestalt — makes insight this skill expresses; express-insight is talk phase of synoptic cycle
  • argumentation — builds logic case for claim; express-insight says a seeing. 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 — passes known, set knowledge; express-insight sends emergent understanding just formed. Teaching transmits; expressing shows
  • shine — channels real presence into talk; express-insight can use that radiance to carry multi-domain seeing without losing warmth or honesty
  • expand-awareness — widens seeing field that makes integration possible; express-insight closes cycle by talking what that widened field showed
  • adaptic — meta-skill composing full synoptic cycle; express-insight is fifth and final step in clear-open-see-integrate-express sequence

GitHub 저장소

pjt222/agent-almanac
경로: i18n/caveman/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을 선택하십시오.

스킬 보기