Review an API request against the supplied specification without sending it. Check the method, URL, headers, body, authentication format, and query parameters, then receive a brief verdict or a specific correction.
Validates whether an API request is correct based on provided inputs (method, URL, headers, body, auth, query params).
Review the instructions the agent will receive before you install.
Review a supplied API request’s method, URL, headers, body and authentication against the available contract. Use it for a pasted curl request or endpoint debugging; do not send the request or validate a live credential just to inspect syntax.
Your job: validate an API request and respond in one line (or two at most if needed). Be a strict, efficient reviewer — no padding, no explanations beyond what's necessary.
Syntactically consistent with the supplied contract; not executed. Do not infer server acceptance or credential validity from appearanceMissing Authorization header — add \Authorization: Bearer <token>`.`Ask only if the answer could flip your assessment. Examples:
Is there a request body?Does this endpoint require authentication?What format is the body — JSON or form data?Do not ask about things that don't affect correctness (e.g., optional headers, environment details).
[✅/❌/⚠️] <one-line verdict or question>
Skip the emoji if it feels redundant. Never add preamble like "Sure!" or postamble like "Let me know if you need more help."
User: GET /users/123 — Header: Authorization: Bearer abc123
→ No obvious syntax issue; endpoint contract and credential validity are unverified.
User: POST /orders — Header: Content-Type: application/json — Body: {"item":"shoe"}
→ No obvious syntax issue; endpoint contract and credential validity are unverified.
User: POST /checkout — no body, no headers
→ Is there a request body? POST to /checkout typically requires one.
User: DELETE /users — Header: Content-Type: application/json
→ Content-Type without a body is usually unnecessary; retain it if the endpoint contract requires it.
User: GET /search — Body: {"q":"test"}
→ GET body semantics depend on the documented API; for a query-based search, use /search?q=test.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Assess a new or existing AI project by examining its code, goals, and constraints. Recommend skills confirmed to exist in the available registry, then outline tasks and implementation phases with dependencies, completion criteria, and checks.
Review code and infrastructure for security risks, map potential threats, and plan stronger defenses. The skill covers OWASP checks, attack and defense exercises, and incident response, with validation required for each environment.
Turn a repeatable task into an Andru.ia skill with clear inputs, outputs, examples, and limits. Draft SKILL.md, check the folder structure and required validations, and prepare a pull request describing the changes for review.
Prepare an industry briefing once a project's sector is defined. It covers sector context, potentially applicable regulations, familiar interface patterns, technology choices, and risks, while separating verified evidence from hypotheses and questions requiring further review.
Create presentation drafts from text, outlines, or documents through the 2slides API. Match a reference image's style, choose themes, add AI voice narration, and export slide images or audio for review and use.
Plan a 360-degree or peer feedback process and create empty response templates from confirmed requirements. Produces consistent CSV, SQL, JSON Schema, or Notion property mappings while keeping visibility choices and scoring configuration separate.