Lap Abuse Api

Abuse API skill. Use when working with Abuse for abuse. Covers 6 endpoints.

Security Scan

The skill is an instruction-only wrapper around an Abuse API (hosted at api.ote-godaddy.com); it asks for no credentials, has no install steps, and its instructions are limited to calling listed endpoints.

Purpose & Capability

The name/description match the SKILL.md: it documents GET/POST endpoints for abuse tickets and a base URL. There are no unrelated binaries, env vars, or config paths requested that would be inconsistent with an API client.

Instruction Scope

Instructions are limited to calling the API endpoints and checking responses. They reference a local spec file (references/api-spec.lap) which is not included in the package — this is a missing artifact but not a direct security risk. The SKILL.md instructs creating tickets (POST) which is expected behavior; agents could perform writes if invoked.

Install Mechanism

No install spec and no code files — instruction-only skill. Nothing is downloaded or written to disk by an installer.

Credentials

The skill declares no required environment variables, credentials, or config paths. SKILL.md also states 'No authentication required.' There are no disproportionate credential requests.

Persistence & Privilege

always is false and the skill does not request persistent system presence or modify other skills/config. Model invocation is allowed (the platform default), which means the agent could call the API autonomously unless the user or platform restricts it.

Assessment

This is an instruction-only API wrapper that lists and calls abuse-ticket endpoints on api.ote-godaddy.com (an OTE/test GoDaddy host). It requires no credentials and does not install anything. Things to consider before installing: (1) the SKILL.md references a local spec file that is not included — behavior/details may be incomplete; (2) the skill can create tickets (POST) — if you allow the agent to call it autonomously it could open tickets on your behalf, so prefer user confirmation for write actions or disable autonomous invocation for safety; (3) confirm the base URL is the intended environment (OTE/test vs production) before using in production workflows. Otherwise the skill is internally consistent with its stated purpose.

Abuse API

API version: 2.0.0

Auth

No authentication required.

Base URL

https://api.ote-godaddy.com

Setup

1. No auth setup needed
2. GET /v1/abuse/tickets -- verify access
3. POST /v1/abuse/tickets -- create first tickets

Endpoints

6 endpoints across 1 groups. See references/api-spec.lap for full details.

abuse

Method	Path	Description
GET	/v1/abuse/tickets	List all abuse tickets ids that match user provided filters
POST	/v1/abuse/tickets	Create a new abuse ticket
GET	/v1/abuse/tickets/{ticketId}	Return the abuse ticket data for a given ticket id
GET	/v2/abuse/tickets	List all abuse tickets ids that match user provided filters
POST	/v2/abuse/tickets	Create a new abuse ticket
GET	/v2/abuse/tickets/{ticketId}	Return the abuse ticket data for a given ticket id

Common Questions

Match user requests to endpoints in references/api-spec.lap. Key patterns:

• "List all tickets?" -> GET /v1/abuse/tickets
• "Create a ticket?" -> POST /v1/abuse/tickets
• "Get ticket details?" -> GET /v1/abuse/tickets/{ticketId}
• "List all tickets?" -> GET /v2/abuse/tickets
• "Create a ticket?" -> POST /v2/abuse/tickets
• "Get ticket details?" -> GET /v2/abuse/tickets/{ticketId}

Response Tips

• Check response schemas in references/api-spec.lap for field details
• List endpoints may support pagination; check for limit, offset, or cursor params
• Create/update endpoints typically return the created/updated object

References

• Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas

Generated from the official API spec by LAP