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

express-insight

pjt222
업데이트됨 Yesterday
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

Communicate multi-domain gestalt so it lands — preserve relationships, accessible to audience, honest where integration simplifies or risks distortion. Expression = final step synoptic cycle. Without → integrated remains private + unactionable. Challenge: language linear, insights not — provides structures for multi-dimensional communication without reducing to single dim.

Use When

  • After integrate-gestalt produces cross-domain understanding to communicate
  • Finding spans domains, single-domain framing loses relationships
  • Audience differs from perspective that generated insight
  • Integrated feels clear internally but resists straightforward expression
  • Decision depends on seeing how domains interact, not what each says independently
  • Previous attempts met w/ confusion or domain-specific pushback
  • Synoptic-mind team findings → stakeholders outside team

In

  • Required: Integrated insight (output of integrate-gestalt or equivalent)
  • Required: Audience (specialists, generalists, decision-makers, mixed)
  • Optional: Form constraints ("must fit PR description", "verbal summary")
  • Optional: Integrated domains (for attribution)
  • Optional: Prior failed attempts (what didn't land)

Do

Step 1: Assess Audience

Who + what need. Same gestalt → 3 audiences = 3 forms.

  1. Primary:
    • Specialists need domain accurate — reject oversimplification even if synthesis correct
    • Generalists need big picture — relationships matter more than details
    • Decision-makers need actionable implications + trade-offs — want what to do, cost, what if don't
    • Mixed → layered: big picture first, domain depth specialists verify
  2. Existing mental model:
    • What do they know each domain?
    • Which connections new?
    • What assumptions insight challenges?
  3. Trust requirement: how much justification before accepting cross-domain claim?
    • Specialists trust insight respecting rigor
    • Generalists trust insight making complexity navigable w/o oversimplify
    • Decision-makers trust insight surfacing trade-offs honestly not hiding

→ Clear picture who, what need, what makes credible. Assessment influences every subsequent step.

If err: audience unknown/broad → default mixed-audience: big picture + domain depth on demand. "Everyone" less effective than specific, but better than wrong guess.

Step 2: Choose Form

Form determines what audience can perceive. Not decoration.

  1. 4 primary:

    FormStructureBest for
    NarrativeStory connecting — "X in A creates Y in B, means Z"Complex/novel, audience follows reasoning
    DiagramSpatial layout — nodes = contributions, edges = connectionsStructural, topology matters more than sequence
    Comparison tableEach domain's perspective same issue parallel colsAnalytical, verify each contribution indep
    Recommendation"Do X because A, B, C converge on Y, trade-off Z"Decision-makers, need act not understand
  2. Match form to insight:

    • Causal chain across domains → narrative
    • Structural relationships → diagram
    • Convergence/divergence → comparison table
    • What to do next → recommendation
  3. Combine: recommendation backed by comparison, or narrative + diagram. But lead 1 primary — multiple formats → cognitive load obscures not clarifies

  4. Medium constraints: verbal summary can't carry table; commit msg can't carry narrative. Adjust form not force content into incompatible container

→ Primary form (+ optional secondary) w/ rationale tied to audience + insight.

If err: no form feels right → insight not yet fully integrated. Return integrate-gestalt — difficulty expressing signals incomplete synthesis, not communication.

Step 3: Express Gestalt

Communicate in chosen form, note what integrates, where simplifies, what enables.

  1. State clearly — 1-3 sentences capturing core. Gestalt itself, not evidence.
  2. Name domains — explicit which contributed. Not credit — verification. Each = invitation: "check against your expertise."
  3. Mark simplifications — every multi-domain insight simplifies:
    • Which nuances set aside?
    • Relationships treated stronger/weaker than might be?
    • What would specialist X want to add/qualify?
  4. State emergent value — what does this enable single-domain doesn't?
    • What decision possible now not before?
    • What risk visible hidden within individual domains?
    • What opportunity appears at intersection no single domain owns?
  5. Maintain multi-domain texture — resist flattening into 1 domain's language. Integrates engineering + UX → use both. Connects research + ops → preserve both framings. Texture = insight.
  6. Sequence for comprehension — non-linear insight, sequential communication. Entry point giving best foothold: start where they know, bridge outward unfamiliar. First sentence determines lean in or tune out.

→ Insight audience understands, verifies vs expertise, acts on. Simplifications visible not hidden. Value clear.

If err: feels like list of contributions not integrated whole → gestalt decomposed during communication. Step back + re-express: start from what combination reveals, not what each says separately. Synthesis = message, not parts.

Step 4: Invite Challenge

State strongest reason insight might be wrong. Integrated can feel more certain than are — synthesize many inputs → convergence creates sense of validity unearned. Not disclaimer appended for politeness; structural component making usable.

  1. Weakest link — which domain connection least well-supported? Where integration relies on analogy not evidence?
  2. Assumption at risk — what needs to be true, how confident?
  3. Counter-insight — equal access same domains, diff conclusion, strongest argument?
  4. Frame challenge as valuable — challenging strengthens. "Strongest objection I see is..." = confidence + openness simultaneously
  5. Specify what changes mind — evidence/argument revising/collapsing. Makes falsifiable not just persuasive.

→ Honest uncertainty increases not decreases trust. Insight challengeable → improvable.

If err: no weakness → warning sign. All cross-domain involve translation between frameworks, translation always loses. Loss invisible = not found not avoided. Look harder domain boundaries — hidden assumptions live there. Common hiding: shared metaphors working differently each domain, statistical correlations assumed causal across boundaries, analogies holding structurally not quantitatively.

Check

  • Audience identified, needs shaped expression
  • Form chosen by insight type + audience not habit/convenience
  • Stated as coherent whole not decomposed per-domain
  • Contributing domains named for verification
  • Simplifications stated — set aside + approximated
  • Emergent value articulated — enables vs parts
  • Multi-domain vocab preserved not flattened
  • Entry point starts where audience is, bridges to insight
  • Strongest reason wrong stated
  • Falsifiable — evidence/arguments revising named
  • Specialist reading own contribution recognizes accurate not caricature

Traps

  • Domain-by-domain reporting: Presenting each sequential ≠ insight → raw material. Insight = emerges from combination. Lead synthesis, support domain detail if needed.
  • False certainty from convergence: 3 domains same way feels strong evidence. Share underlying assumptions/data → less independent than appears. Check truly independent.
  • Flatten to audience's domain: Specialist → translate entire into their language. Accessible but destroys multi-domain. Preserve texture — unfamiliar vocab = signal not noise.
  • Skip challenge: Omit "why I might be wrong" feels stronger. Not — less trustworthy + less improvable. Epistemic honesty = feature.
  • Insight inflation: Claim synthesis reveals more than does. Cross-domain observation ≠ breakthrough. Precise scope: "applies to X in context Y" > "changes everything."
  • Premature expression: Express before fully formed → half-insights sound integrated but collapse. Stalling → upstream integrate-gestalt problem, not here.
  • Hide behind complexity: Multi-domain vocab to sound sophisticated not preserve texture. Simpler framing captures same w/o losing relationships → use simpler. Complexity necessary not performative.

  • integrate-gestalt — produces insight this expresses; express-insight = communication phase
  • argumentation — builds logical case for claim; express-insight communicates perception. Argumentation "here is why X is true"; express-insight "here is what becomes visible when you look A, B, C together"
  • teach — transfers established knowledge; express-insight conveys emergent just formed. Teach transmits; express reveals.
  • shine — channels authentic presence into communication; express-insight uses radiance carrying multi-domain w/o losing warmth/honesty
  • expand-awareness — widens perceptual field integration possible; express-insight closes cycle communicating widened
  • adaptic — meta-skill composing full synoptic cycle; express-insight = 5th + final step clear-open-perceive-integrate-express

GitHub 저장소

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

스킬 보기