Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mwd1234/ios-agentic-skills --skill error-messaging-and-empty-statesgit clone --depth 1 https://github.com/mwd1234/ios-agentic-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mwd1234/ios-agentic-skills/error-messaging-and-empty-states)<a href="https://agentmods.dev/skills/mwd1234/ios-agentic-skills/error-messaging-and-empty-states"><img src="https://agentmods.dev/badge/skills/mwd1234/ios-agentic-skills/error-messaging-and-empty-states/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mwd1234/ios-agentic-skills/error-messaging-and-empty-states"><img src="https://agentmods.dev/badge/skills/mwd1234/ios-agentic-skills/error-messaging-and-empty-states.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00040 | $0.00509 |
| Opus 5 | $0.00020 | $0.00254 |
| Sonnet 5 | $0.00008 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
error-messaging-and-empty-states scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Error Messaging & Empty States
Design and audit user-visible errors and empty states so they are clear, actionable, and respectful of user intent.
When to use this skill
- When adding new flows with failure modes
- Before App Store submission
- After user reports confusion or churn
- When adding sync, network, or permission features
Core Principles (HIG-aligned)
- Be specific: explain what failed
- Offer a next action: retry, adjust, learn more
- Avoid blame: no “you did X wrong”
- Keep it short and human
Step 1: Inventory User-Facing Errors
Search for alerts and error views:
rg --type swift -g '!*Tests*' '\.alert\(' YourApp/Views/
rg --type swift -g '!*Tests*' 'ContentUnavailableView' YourApp/Views/
Check:
- Title + message are both present
- Primary action is clear
- Secondary action cancels or dismisses
Step 2: Empty State Coverage
Empty states should explain:
- Why it’s empty
- What the user can do next
Examples:
- “No patterns yet” + “Create your first pattern” button
- “Nothing synced” + “Open on iPhone to sync”
Step 3: Permissions & Settings Errors
If a permission is denied:
- Explain why it’s needed
- Offer a path to Settings
Checklist:
- Only request permissions on user action
- Provide a Settings CTA after denial
Step 4: Network & Sync Failures
- Use retry actions for transient failures
- Surface offline state explicitly
- Avoid repeated blocking alerts
Step 5: Error Copy Style Guide
- Short, human, and actionable
- Avoid technical jargon
- Use the user’s language (localized)
Output Format
| Category | Issues | Status |
|---|---|---|
| Alerts reviewed | X | ✅/❌ |
| Empty states present | X | ✅/❌ |
| Permission guidance | X | ✅/❌ |
| Retry paths | X | ✅/❌ |
| Localized error copy | X | ✅/❌ |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 93 lines · 40 tokens per session scan A c05874df9fac
error-messaging-and-empty-states is a skill published in the GitHub repository mwd1234/ios-agentic-skills (50 stars, last pushed 7mo ago), licensed MIT. It adds 40 tokens to every session and 509 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
expo-design-system
Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…
flutter-build-responsive-layout
Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…
omh-apple-design
This is a Hermes-native apple-design workflow skill.
axiom-audit-liquid-glass
Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.
axiom-audit-ux-flow
Use when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.