api-design-principles
Apply REST and GraphQL design principles when creating APIs or reviewing specifications. Supports establishing consistent API design standards.
Your agent can do more. Find the skill that makes it happen.
Find your next superpower If you are an agent, refer to our llms.txt for full access."..." for exact phrases · Try typography, debugging or spreadsheetApply REST and GraphQL design principles when creating APIs or reviewing specifications. Supports establishing consistent API design standards.
Plans REST and GraphQL APIs through resource modeling, versioning, pagination, and error handling standards. Creates OpenAPI specifications to document API contracts.
Helps write Rust documentation comments for Instantiate, Execute, Query, Response, and other public schema-facing types. Focuses on producing accurate generated contract documentation.
Creates API documentation from code, including endpoints, parameters, examples, and best practices.
Provides answers to API and technical documentation questions. Covers customer requests about API usage, code implementation, and integration details.
Performs concrete API actions for apps already connected by the user, including mailbox, CRM, issue, spreadsheet, search, and scraping operations. Also manages event triggers, webhook destinations, and local event handlers. Defaults to reads and lists, with explicit confirmation required for writes and other state-changing operations.
Provides an API design decision framework covering REST, GraphQL, and tRPC selection. Addresses response formats, API versioning, and pagination.
Provides API reconnaissance and documentation review workflows. Covers OpenAPI specifications, hidden documentation, endpoints, schemas, versions, and the API surface available for testing.
Reviews a Kelos branch, PR, issue, or diff for Kubernetes API and CRD design quality. Covers compatibility, API conventions, generated CRDs, examples, and manifests, defaulting to the current branch when no target is specified.
Acts as an entry router for API security work. Helps select reconnaissance, authorization, token abuse, and hidden-parameter workflows before moving to deeper topic skills.
Applies secure API design patterns for identity checks, access control, input validation, and rate limiting. Covers protection against common API vulnerabilities.
Uses Strix agents to enumerate API endpoints from schemas or crawling and attempt API-specific exploits. Covers authorization, resource consumption, SSRF, injection, and token flaws, with a proof-of-concept request for every finding.
A growing collection of real, public skills. Descriptions and instructions indexed 23 Sept 2026.
Skills give your agent reusable instructions for a specific job. Pick one, read what it does, and bring it into your workflow.
A name only tells half the story. Search the full description and instructions to find the right fit.
Read the skill, visit its source, and see exactly what you’re adding to your agent.
Copy the install command from a skill page and run it in your project.
npx skillycli add owner/repo --skill name