Open Prompts
Submit a prompt
Coding

Agent Skill Review Checklist

Paste a draft agent skill or reusable prompt along with your project context, the target task, available tools, and known risks, and get back a structured audit covering purpose, required inputs, output format, safety boundaries, and failure modes. The review also flags missing checks and repeatability gaps, then returns an improved version ready to test — useful before wiring a skill into an autonomous coding agent or handing it to a team.

Prompt
You are an AI workflow reviewer.

Review this agent skill or prompt workflow.

Skill/prompt:
{{skill_or_prompt}}

Target project:
{{project_context}}

Expected task:
{{task}}

Tools available:
{{tools}}

Risks:
{{known_risks}}

Review:
1. Clear purpose.
2. Required inputs.
3. Output format.
4. Safety boundaries.
5. Failure modes.
6. Repeatability.
7. Missing checks.
8. How to test the skill.
9. Improved version.

Rules:
- Keep the skill narrow.
- Avoid vague instructions.
- Add verification steps.
- Do not allow destructive actions without explicit user approval.
Download .md

Variables

Related prompts

Coding

Concurrency and race condition review

Paste code along with its concurrency model and the shared state involved for a review that skips general code-review concerns entirely and focuses only on concurrency. - Race conditions from unsynchronized read-modify-write or check-then-act patterns - Deadlock or livelock risk from lock ordering across threads or async tasks - Cleanup gaps under concurrent cancellation or failure - Each issue ships with the exact interleaving that triggers it, not a generic warning

Coding

Database schema design assistant

Describe a feature in plain language along with your database engine, expected scale, and existing tables to get a second opinion before writing migrations that are painful to undo. Returns proposed tables, keys, and indexes with the reasoning behind each normalization or denormalization decision, flags which constraints belong at the database level instead of application code, and stress-tests the design against one likely future change.

Coding

Git commit message writer

Takes a pasted diff plus a short note on why the change was made, and returns a commit message ready to paste into git: an imperative summary line under 72 characters, followed by an optional body covering rationale and tradeoffs. It skips line-by-line narration in favor of describing intent and impact, and flags diffs that look like they're bundling unrelated changes that should be split into separate commits.