MCP HubMCP Hub
Volver a habilidades

express-insight

pjt222
Actualizado Yesterday
2 vistas
17
2
17
Ver en GitHub
Metaai

Acerca de

Esta habilidad traduce una visión compleja y multidisciplinar en una comunicación clara y accionable para un público específico. Proporciona un método estructurado para elegir el formato adecuado, transmitir la comprensión integrada sin simplificar en exceso e invitar a una retroalimentación constructiva. Úsala después de `integrate-gestalt` para compartir efectivamente perspectivas interdisciplinarias con especialistas, generalistas o responsables de la toma de decisiones.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add pjt222/agent-almanac -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternativo
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/express-insight

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

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

Repositorio GitHub

pjt222/agent-almanac
Ruta: i18n/caveman-ultra/skills/express-insight
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Habilidades relacionadas

content-collections

Meta

Esta habilidad proporciona una configuración probada en producción para Content Collections, una herramienta centrada en TypeScript que transforma archivos Markdown/MDX en colecciones de datos con tipado seguro mediante validación Zod. Úsala al construir blogs, sitios de documentación o aplicaciones Vite + React con mucho contenido para garantizar seguridad de tipos y validación automática de contenido. Abarca todo, desde la configuración del plugin de Vite y compilación MDX hasta la optimización de despliegue y validación de esquemas.

Ver habilidad

polymarket

Meta

Esta habilidad permite a los desarrolladores crear aplicaciones con la plataforma de mercados de predicción Polymarket, incluyendo la integración de API para operaciones y datos de mercado. También proporciona transmisión de datos en tiempo real a través de WebSocket para monitorear operaciones en vivo y actividad del mercado. Úsela para implementar estrategias de trading o crear herramientas que procesen actualizaciones de mercado en tiempo real.

Ver habilidad

creating-opencode-plugins

Meta

Esta habilidad ayuda a los desarrolladores a crear complementos de OpenCode que se conectan a más de 25 tipos de eventos, como comandos, archivos y operaciones LSP. Proporciona la estructura del complemento, las especificaciones de la API de eventos y los patrones de implementación para módulos en JavaScript/TypeScript. Úsala cuando necesites interceptar, monitorear o extender el ciclo de vida del asistente de IA de OpenCode con lógica personalizada basada en eventos.

Ver habilidad

sglang

Meta

SGLang es un framework de alto rendimiento para el servicio de LLM que se especializa en generación rápida y estructurada para JSON, expresiones regulares y flujos de trabajo de agentes utilizando su caché de prefijos RadixAttention. Ofrece una inferencia significativamente más rápida, especialmente para tareas con prefijos repetidos, lo que lo hace ideal para salidas complejas y estructuradas, y conversaciones multiturno. Elige SGLang sobre alternativas como vLLM cuando necesites decodificación restringida o estés construyendo aplicaciones con uso extensivo de prefijos compartidos.

Ver habilidad