New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Feedback Loop States And Latency

by hashgraph-online in hashgraph-online/awesome-codex-plugins

A skill your agent uses when designing the visible states an interactive element passes through (idle / pending / success / error) and matching feedback timing to the user's perceptual thresholds.

Apache-2.0Auto-check passedBackend & APIs

Install Feedback Loop States And Latency

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill feedback-loop-states-and-latency -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins feedback-loop-states-and-latency --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/feedback-loop-states-and-latency .claude/skills/feedback-loop-states-and-latency && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
feedback-loop-states-and-latency
GitHub stars
1.3k
Token cost
~1.4k tokens
SKILL.md length
512 words
Files
2 (incl. references)
Skills in repo
714
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when designing the visible states an interactive element passes through (idle / pending / success / error) and matching feedback timing to the user's perceptual thresholds.

  • Works in 3 steps: The "what state am I in?" check. At any… → The latency-stopwatch. Time each major… → The error-recovery audit. For each error…
  • Designing button states
  • SKILL.md covers The four states, Latency thresholds (Miller,…, Optimistic UI and Skeleton screens vs. spinners, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Feedback Loop States And Latency is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill when designing the visible states an interactive element passes through (idle / pending / success / error) and matching feedback timing to the user's perceptual thresholds. Trigger when designing button states, form-submit flows, file-upload progress, loading screens, or any interaction whose response time is variable. Sub-aspect of feedback-loop; read that first.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/latency-thresholds-and-patterns.md`).

It sits in Backend & APIs, covering File uploads and storage. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

  • Designing button states
  • Form-submit flows
  • File-upload progress
  • Loading screens

Example prompts

  • “/feedback-loop-states-and-latency”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. The "what state am I in?" check. At any moment during an action, can the user tell which of the four states they're in? If not, feedback…
  2. The latency-stopwatch. Time each major action. Match feedback to the threshold the action falls into.
  3. The error-recovery audit. For each error feedback, can the user tell what to do next? If "no idea," rewrite the message.

What it can do on your machine

Read from SKILL.md and the folder at commit 9e7b281. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are html and javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Feedback Loop States And Latency loads about 1.4k tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 512 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 9e7b281, republished under its Apache-2.0 licence (© hashgraph-online). 512 words, ~1,439 tokens.

Download SKILL.mdSave it as .claude/skills/feedback-loop-states-and-latency/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
feedback-loop-states-and-latency
description
Use this skill when designing the visible states an interactive element passes through (idle / pending / success / error) and matching feedback timing to the user's perceptual thresholds. Trigger when designing button states, form-submit flows, file-upload progress, loading screens, or any interaction whose response time is variable. Sub-aspect of `feedback-loop`; read that first.

Feedback states and latency thresholds

Most interactive actions pass through a small set of visible states; the system must communicate each. The latency of each state determines what feedback is appropriate — a 50ms response needs no spinner, a 5s response needs progress info, a 50s response needs estimated time remaining.

The four states

Idle

The element is interactive and waiting. Affordance signals "you can do this." Static styling.

Pending

Action triggered; system working. Disable trigger to prevent re-submit; show indicator if wait > ~500ms.

Success

Action succeeded. Show the result in-place where possible; toast/banner if the result is on another surface.

Error

Action failed. In-context, specific, actionable error message.

html
<button id="action" data-state="idle">
  <span class="label">Save</span>
  <span class="spinner" hidden></span>
</button>

<style>
  button[data-state="pending"] { cursor: wait; opacity: 0.7; }
  button[data-state="pending"] .spinner { display: inline-block; }
  button[data-state="success"] { background: var(--success); }
  button[data-state="error"] { background: var(--destructive); }
</style>

Latency thresholds (Miller, Card et al., Doherty)

LatencyThresholdPattern
< 100ms"Instant"No indicator. Just respond.
100–400ms"Responsive"Light state change (button briefly disabled).
400ms–1s"Noticeable"Spinner or progress micro-animation.
1–10s"Waiting"Spinner with status text.
> 10s"Long"Progress bar with estimated time remaining; cancel option.

Doherty Threshold (~400ms): response times under this keep users in flow. Above this, attention drifts and engagement drops.

Optimistic UI

For actions where the success rate is high and the action is reversible, update the UI as if the action succeeded immediately, then commit in the background. If the action fails, roll back visibly with an error message.

js
async function toggleStar(item) {
  // Optimistic
  item.starred = !item.starred;
  render();

  try {
    await api.updateStar(item.id, item.starred);
  } catch (err) {
    // Rollback with feedback
    item.starred = !item.starred;
    render();
    showToast(`Couldn't update: ${err.message}`);
  }
}

The user gets instant feedback; failure is the exception, handled with explicit feedback.

Skeleton screens vs. spinners

For loading content (not actions), prefer skeleton screens to spinners:

html
<!-- While data loads -->
<article class="post-skeleton">
  <div class="title-skel"></div>
  <div class="meta-skel"></div>
  <div class="body-skel"></div>
  <div class="body-skel"></div>
</article>

Skeletons:

  • Show the page's structure immediately.
  • Reduce perceived load time.
  • Reduce visual disruption when real content arrives.

Spinners are better when the wait isn't structural (a single action's pending state) or when the location of the result isn't predictable.

Progress indicators for long operations

For operations > 10s:

  • Determinate progress bar (when % complete is known) with status text.
  • Time-remaining estimate (after enough data to estimate accurately).
  • Cancel option (don't trap the user in a stuck operation).
  • Background continuation option for very long ops (let them work elsewhere).
html
<div class="upload">
  <p>Uploading <strong>file.zip</strong></p>
  <progress max="100" value="42">42%</progress>
  <p class="status">42% — about 2 minutes remaining</p>
  <button>Cancel</button>
</div>
Show full SKILL.md (187 more words)Show less

Error feedback: in-context

Errors should appear with the element that caused them, not in a generic page banner.

html
<div class="field" data-state="error">
  <label for="email">Email</label>
  <input id="email" type="email" aria-invalid="true" aria-describedby="email-error" />
  <p id="email-error" class="error">
    We couldn't find an account with this email.
    <a href="/signup">Sign up?</a>
  </p>
</div>

aria-invalid and aria-describedby make the error programmatically associated; screen readers announce both together.

Anti-patterns

  • Silent commits. Button submits with no visible response.
  • Blink-and-miss success. Confirmation appears for 100ms.
  • Generic errors. "Something went wrong" with no specific or actionable info.
  • Spam confirmations. Every save shows a "Saved!" toast users dismiss on autopilot.
  • Wrong state colors. Pending state same color as success.
  • Spinners over content the user is reading. Distracting; use skeleton or peripheral indicator.

Heuristics

  1. The "what state am I in?" check. At any moment during an action, can the user tell which of the four states they're in? If not, feedback is missing.
  2. The latency-stopwatch. Time each major action. Match feedback to the threshold the action falls into.
  3. The error-recovery audit. For each error feedback, can the user tell what to do next? If "no idea," rewrite the message.
  • feedback-loop (parent).
  • feedback-loop-positive-vs-negative — loop architecture; this skill is loop implementation.
  • accessibility-operable — aria-live regions communicate states to screen readers.
  • forgiveness — error feedback is recovery's first step.

© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/feedback-loop-states-and-latency of hashgraph-online/awesome-codex-plugins.

  • SKILL.md
  • references/latency-thresholds-and-patterns.md

Open the folder on GitHubat commit 9e7b281

Compare with similar skills

Feedback Loop States And Latency next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Feedback Loop States And Latency compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Feedback Loop States And Latency this skillhashgraph-online/awesome-codex-plugins1.3k—~1.4kAutomated safety check: PassApache-2.0
Stripe Projectsfossasia/eventyay1.7k5 repos~2kAutomated safety check: NotesApache-2.0
FoundatioFoundatioFx/Foundatio2.1k—~3.9kAutomated safety check: PassApache-2.0
Spatialduckdb/duckdb-skills6041 repos~1kAutomated safety check: NotesMIT
R Oopab604/claude-code-r-skills2062 repos~1.9kAutomated safety check: PassMIT
Edgestore Setupedgestorejs/edgestore454—~1.8kAutomated safety check: PassMIT

Similar skills

  • Stripe Projects

    fossasia/eventyay

    A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.

    1.7k GitHub starsUsed in 5 repos~2k tokens
    Backend & APIsAuto-check: notes

  • Foundatio

    FoundatioFx/Foundatio

    A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.

    2.1k GitHub stars~3.9k tokensUpdated today
    Backend & APIsAuto-check passed

  • Spatial

    duckdb/duckdb-skills

    Official

    Answer questions about spatial data using DuckDB. An agent skill from duckdb/duckdb-skills.

    604 GitHub starsUsed in 1 repo~1k tokens
    Backend & APIsAuto-check: notes

  • R Oop

    ab604/claude-code-r-skills

    R object-oriented programming guide for S7, S3, S4, and vctrs.

    206 GitHub starsUsed in 2 repos~1.9k tokens
    Backend & APIsAuto-check passed

  • Edgestore Setup

    edgestorejs/edgestore

    A skill your agent uses when adding, extending, or troubleshooting EdgeStore file uploads, upload UI, or bucket access policies in a TypeScript/React application.

    454 GitHub stars~1.8k tokensUpdated 3 days ago
    Backend & APIsAuto-check passed

  • S3 Explore

    duckdb/duckdb-skills

    Official

    Explore and query data on S3, Cloudflare R2, GCS, MinIO, or any S3-compatible storage.

    604 GitHub starsUsed in 1 repo~848 tokens
    Backend & APIsAuto-check: notes

More from hashgraph-online/awesome-codex-plugins

All 714 skills in this repo

  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.3k GitHub stars~922 tokensUpdated today
    Auto-check passed

  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.3k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.3k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Calle

    hashgraph-online/awesome-codex-plugins

    Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.3k GitHub stars~618 tokensUpdated today
    Auto-check passed

Categories

Questions about Feedback Loop States And Latency

What does Feedback Loop States And Latency do?

A skill your agent uses when designing the visible states an interactive element passes through (idle / pending / success / error) and matching feedback timing to the user's perceptual thresholds. Feedback Loop States And Latency is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill when designing the visible states an interactive element passes through (idle / pending / success / error) and matching feedback timing to the user's perceptual thresholds.

When should I use Feedback Loop States And Latency?

Feedback Loop States And Latency fits situations like: designing button states; form-submit flows; file-upload progress; loading screens.

How do I install Feedback Loop States And Latency in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill feedback-loop-states-and-latency -a claude-code`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/feedback-loop-states-and-latency in hashgraph-online/awesome-codex-plugins) into .claude/skills/feedback-loop-states-and-latency in your project. Claude Code loads it when a task matches its description.

How do I install Feedback Loop States And Latency in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill feedback-loop-states-and-latency -a codex`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/feedback-loop-states-and-latency in hashgraph-online/awesome-codex-plugins) into .agents/skills/feedback-loop-states-and-latency in your project. Codex loads it when a task matches its description.

Can I use Feedback Loop States And Latency in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill feedback-loop-states-and-latency -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feedback-loop-states-and-latency, .gemini/skills/feedback-loop-states-and-latency, .github/skills/feedback-loop-states-and-latency and .opencode/skills/feedback-loop-states-and-latency in your project.

What does Feedback Loop States And Latency need to run?

SKILL.md names no scripts, command-line tools or credentials: Feedback Loop States And Latency is instructions for the agent only.

Does Feedback Loop States And Latency access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Feedback Loop States And Latency safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Feedback Loop States And Latency use?

Feedback Loop States And Latency is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Feedback Loop States And Latency use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Feedback Loop States And Latency?

Skills that share tags, products or a category with Feedback Loop States And Latency: Stripe Projects (fossasia/eventyay, 1.7k stars), Foundatio (FoundatioFx/Foundatio, 2.1k stars), Spatial (duckdb/duckdb-skills, 604 stars) and R Oop (ab604/claude-code-r-skills, 206 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Feedback Loop States And Latency?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,255 GitHub stars. The repository holds 714 skills in this directory. The repository was last updated on October 9, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.