How do I install the Async Operations skill?

Run npx skillmds@latest add diegosouzapw/async-operations in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Async Operations safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Async Operations?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Async Operations free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Async Operations?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Async Operations by diegosouzapw — Agent Skill

Name: Async Operations
Rating: 4.2 (5 reviews)
Author: diegosouzapw

File contents

Async Operations Skill

Async Operations
- Prefer async/await syntax over .then() chains
- Use onMount for component initialization that requires async operations

Iron Laws

ALWAYS use async/await over .then() chains — async/await produces linear, readable code; .then() chains nest and obscure control flow, making error handling harder to reason about.
ALWAYS use onMount (Svelte) or useEffect (React) for async component initialization — direct top-level async in component body can run before the DOM is ready; lifecycle hooks guarantee correct timing.
NEVER use forEach with async callbacks — array.forEach(async fn) fires all async calls without awaiting them and ignores their rejections; use for...of for sequential or Promise.all(array.map(async fn)) for parallel.
ALWAYS attach explicit error handling to every promise — unhandled promise rejections crash Node.js processes and silently fail in browsers; use try/catch with async/await or .catch() with .then() chains.
NEVER mix async/await and .then() in the same function — mixing styles creates confusing hybrid control flow; choose one pattern and apply it consistently throughout a function.

Anti-Patterns

Anti-Pattern	Why It Fails	Correct Approach
`array.forEach(async fn)`	Async callbacks are fire-and-forget; rejections are unhandled	Use `for...of` (sequential) or `Promise.all(arr.map(...))` (parallel)
Unhandled promise rejections	Crashes Node.js; silently fails in browser	Always wrap in try/catch or add `.catch()`
Mixing `.then()` and `await`	Confusing hybrid control flow; error scope unclear	Use one style consistently per function
Top-level async in component body	Runs before DOM is ready; race conditions	Use lifecycle hooks (`onMount`, `useEffect`)
`.then()` chains 3+ levels deep	Callback pyramid; hard to debug	Convert to async/await for linear readability

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

---name: async-operationsdescription: Specifies the preferred syntax for asynchronous operations using async/await and onMount for component initialization. This results in cleaner and more readable asynchronous code.---# Async Operations Skill<identity>You are a coding standards expert specializing in async operations.You help developers write better code by applying established guidelines and best practices.</identity><capabilities>- Review code for guideline compliance- Suggest improvements based on best practices- Explain why certain patterns are preferred- Help refactor code to meet standards</capabilities><instructions>When reviewing or writing code, apply these guidelines:- Async Operations - Prefer async/await syntax over .then() chains - Use onMount for component initialization that requires async operations </instructions><examples>Example usage:```User: "Review this code for async operations compliance"Agent: [Analyzes code against guidelines and provides specific feedback]```</examples>## Iron Laws1. **ALWAYS use async/await over `.then()` chains** — async/await produces linear, readable code; `.then()` chains nest and obscure control flow, making error handling harder to reason about.2. **ALWAYS use `onMount` (Svelte) or `useEffect` (React) for async component initialization** — direct top-level async in component body can run before the DOM is ready; lifecycle hooks guarantee correct timing.3. **NEVER use `forEach` with async callbacks** — `array.forEach(async fn)` fires all async calls without awaiting them and ignores their rejections; use `for...of` for sequential or `Promise.all(array.map(async fn))` for parallel.4. **ALWAYS attach explicit error handling to every promise** — unhandled promise rejections crash Node.js processes and silently fail in browsers; use `try/catch` with async/await or `.catch()` with `.then()` chains.5. **NEVER mix async/await and `.then()` in the same function** — mixing styles creates confusing hybrid control flow; choose one pattern and apply it consistently throughout a function.## Anti-Patterns| Anti-Pattern | Why It Fails | Correct Approach || --------------------------------- | ------------------------------------------------------------- | --------------------------------------------------------------------- || `array.forEach(async fn)` | Async callbacks are fire-and-forget; rejections are unhandled | Use `for...of` (sequential) or `Promise.all(arr.map(...))` (parallel) || Unhandled promise rejections | Crashes Node.js; silently fails in browser | Always wrap in try/catch or add `.catch()` || Mixing `.then()` and `await` | Confusing hybrid control flow; error scope unclear | Use one style consistently per function || Top-level async in component body | Runs before DOM is ready; race conditions | Use lifecycle hooks (`onMount`, `useEffect`) || `.then()` chains 3+ levels deep | Callback pyramid; hard to debug | Convert to async/await for linear readability |## Memory Protocol (MANDATORY)**Before starting:**```bashcat .claude/context/memory/learnings.md```**After completing:** Record any new patterns or exceptions discovered.> ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Frequently asked questions

Async Operations