More screenshots
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+21 moreClaude CodeCursorCodex CLIMuseDots
Manus
Grok
Grok Bot+18 agentsForm Error & Recovery Copy
Draft clear form errors and recovery messages grounded in your actual rules and product behavior.
Free
Form Error & Recovery Copy
Example session with this skill installed
Draft professional, concise form error and recovery messages for this client-intake form. Supply a message inventory and proposed acceptance checks. Review only this specification; do not change any files in the product.
Product: Briefdesk. Form action: Send request. Source A, approved form rules v1:
- A1. Project title is required. Visible field label: Project title.
- A2. Contact email must be a valid email address. Visible field label: Contact email.
- A3. Project notes allow at most 500 characters. Visible field label: Project notes.
Source B, approved submission behavior v1:
- B1. A validation error appears beside the relevant field. After correction, the same field rule is reevaluated. No additional copy limit is specified.
- B2. On a definite server rejection, no request is created. Entered values stay in the form. A Retry action reattempts the same request; engineering has approved it as safe for this confirmed-rejection scenario.
- B3. After a network timeout, the server outcome is unknown. No outcome-checking route or safe reattempt behavior has been approved. Do not claim the request failed or that another send is safe.
Prepare five rows: missing title, invalid contact email, notes over the maximum, definite rejection, and timeout with unknown outcome. No screenshot or implementation was supplied.
- Read your context and instructions
- Compiled the form error
| ID | Scenario | Message | Action | Copy status |
|---|---|---|---|---|
| BD-001 | Project title missing | Enter a project title. | — | DRAFT FOR REVIEW |
| BD-002 | Invalid Contact email | Enter a valid email address. | — | DRAFT FOR REVIEW |
| BD-003 | Project notes over 500 characters | Keep Project notes to 500 characters or fewer. | — | DRAFT FOR REVIEW |
| BD-004 | Confirmed server rejection | Request not sent — Your entered values are still in the form. Retry to send your request. | Retry | DRAFT FOR REVIEW |
| BD-005 | Timeout; outcome unknown | We couldn't confirm whether your request was sent. | — | BLOCKED — BEHAVIOR UNKNOWN |
Why the last two rows differ
Source B2 explicitly establishes that a rejected request was not created, entered values remain and Retry is safe for that scenario. Source B3 supplies none of those guarantees after timeout. The timeout row therefore offers neutral wording while leaving recovery unresolved.
Priority decisions
- Establish how the timeout outcome can be resolved and when another send is safe.
- Confirm whether entered values remain after timeout before adding reassurance.
- Confirm the product's character-counting convention for the 500-character notes rule.
Proposed acceptance check
For a timeout with unknown outcome, show the neutral message without claiming failure, recommending another send or promising retained input. Review recovery controls separately once their behavior is approved.
The full recorded output includes source references, placement recommendations and checks for each row.
Connects securely to your tools. The creator never sees your data.
About this skill
Write form errors that explain the problem and offer only the recovery actions your product actually supports.
Form Error & Recovery Copy turns supplied field rules and failure scenarios into a concise message inventory. It keeps validation errors, confirmed submission failures and unknown request outcomes separate.
What you get
- Field-specific validation messages grounded in your actual rules.
- Submission-error and recovery copy with clear action labels where supported.
- A message inventory with triggers, source references, placement recommendations and unresolved decisions.
- Proposed acceptance checks for your design or development handoff.
- Localization-ready JSON when requested.
Who it is for
Product designers, UX writers, frontend developers and small SaaS teams improving forms before implementation or release.
How it works
- Supply your field labels, validation rules, failure scenarios and known recovery behavior.
- The skill drafts concise copy and flags unsupported actions or conflicting requirements.
- Review the inventory and resolve blocked decisions before using the messages in your product.
Helpful without unsupported promises
A timeout does not prove a request failed. A friendly message should not promise saved input, safe resubmission or a recovery link unless those behaviors are established. The skill makes those boundaries explicit.
Requirements and limits
Use an AI agent that loads SKILL.md instructions and can read your supplied material. Pasted text is sufficient; image understanding is required for screenshot inputs. No external service, API key or additional runtime is required by the skill.
The output is copy for review. It does not implement validation, test your product, define security policy or certify accessibility. Task evaluations to date are in Codex; other agent hosts and automatic trigger behavior have not been verified.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 3 days ago
- Free with an Agensi account
Requires