latency

Explain the relational meaning of waiting for a reply through scenario-based tests.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/wojons/je-ne-sais-quoi --skill latency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: latency
Source: https://github.com/wojons/je-ne-sais-quoi/tree/main/skills/latency
Command: npx skills add https://github.com/wojons/je-ne-sais-quoi --skill latency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires je-ne-sais-quoi.

What problem does it solve?

latency helps an AI explain the emotional and relational weight of waiting for a reply, so answers feel human rather than purely technical.

Core Features & Use Cases

  • Felt concept framing: Replaces “response delay” with lived “exposure” during the wait, including how silence “climates” change by relationship.
  • Practical diagnostic situations: Uses scenario-based tests (typing indicators, read receipts, pauses, and response timing) to detect whether an output actually feels latency.
  • Hollow vs felt contrast: Teaches the failure texture of mechanical/system explanations so the model can avoid them.

Quick Start

Use the latency skill to rewrite a reply scenario where someone is waiting for a meaningful response, focusing on the emotional exposure and relationship-shaped silence rather than just time measurements.

Frequently Asked Questions about latency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write dialogue that captures the emotional weight of waiting for a reply?

To write dialogue with emotional weight, reframe response delay as lived exposure rather than measurable time. Generate narrative felt explanations that describe how silence climates change based on the specific relationship and typing indicators involved.

What is felt meaning in communication latency and when do I need it?

Felt meaning in communication latency replaces technical time-gap metrics with the emotional exposure of waiting. You need it when writing dialogue involving read receipts, typing indicators, or pauses before high-stakes answers to make interactions feel human.

How do I avoid mechanical failure modes when writing about response timing?

Avoid mechanical failure modes by using scenario-based tests to detect hollow explanations that reduce latency to uniform signals. Contrast these with felt framing to ensure your reply scenarios convey actual relational weight instead of standardized timing metrics.

Can I use this approach for read receipts and typing indicators in dialogue?

Yes, you can use this approach for read receipts and typing indicators by running diagnostic scenario tests. It evaluates whether your output actually feels latency through emotional framing, identifying hollow failure modes where pauses are reduced to mere signals.

Does dialogue writing for high-stakes pauses require dependency setup?

Dialogue writing for high-stakes pauses requires the je-ne-sais-quoi dependency to properly generate narrative felt explanation content. This prerequisite ensures your relational communication scenarios convey authentic emotional exposure rather than mechanical system explanations.

Best way to rewrite a reply scenario to focus on relationship-shaped silence?

The best way to rewrite a reply scenario is to replace response delay metrics with descriptions of lived exposure during the wait. Focus on how silence climates shift according to the relationship, using felt concept framing to transform waiting into meaning.