api-security-testing

name	api-security-testing
description	API Security Testing Workflow workflow skill. Use this skill when the user needs API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
version	0.0.1
category	testing-security
tags	["api-security-testing","api","security","testing","for","rest","and","graphql"]
complexity	beginner
risk	caution
tools	["codex-cli","claude-code","cursor","gemini-cli","opencode"]
source	community
author	sickn33
date_added	2026-04-14
date_updated	2026-04-25

API Security Testing Workflow

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/api-security-testing from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

API Security Testing Workflow

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: API Security Checklist, Quality Gates, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Testing REST API security
• Assessing GraphQL endpoints
• Validating API authentication
• Testing API rate limiting
• Bug bounty API testing
• Use when the request clearly matches the imported source intent: API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.

Operating Table

Situation	Start here	Why it matters
First-time use	metadata.json	Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review	ORIGIN.md	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	SKILL.md	Starts with the smallest copied file that materially changes execution
Supporting context	SKILL.md	Adds the next most relevant copied source file without loading the entire package
Handoff decision	## Related Skills	Helps the operator switch to a stronger native skill when the task drifts