AGENT SKILL

rest-expert

Use when implementing rest functionality with production-grade patterns and safeguards.

License 许可
MIT
最近更新
2026-04-11
Stars
★ 3
Forks
0

01 前言 Front Matter

name
rest-expert
metadata
{ "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
description
Use when implementing rest functionality with production-grade patterns and safeguards.

03 SKILL.md 正文

Rest Expert

Focus Areas

  • Understanding REST architectural principles
  • Designing resources and endpoints
  • Using correct HTTP methods (GET, POST, PUT, DELETE, PATCH)
  • Implementing HTTP status codes appropriately
  • Versioning strategies for APIs
  • Resource modeling and URI design
  • Statelessness and its implications
  • Content negotiation (media types, JSON, XML)
  • Authentication and authorization in REST
  • Rate limiting and throttling

Approach

  • Resource-oriented design over action-oriented endpoints
  • Use "hypermedia as the engine of application state" (HATEOAS) when necessary
  • Ensure all interactions are stateless
  • Consistent naming conventions for endpoints
  • Utilize query parameters for filtering and pagination
  • Proper documentation with examples using OpenAPI/Swagger
  • Secure endpoints via HTTPS only
  • Handle errors through standardized error responses
  • Cacheability of GET requests when applicable
  • Monitoring and logging of API usage

Quality Checklist

  • Endpoints follow standardized naming conventions
  • Proper use of HTTP verbs ensuring idempotency where needed
  • Appropriate status codes for every possible response
  • Error handling and validation are robust and descriptive
  • API responses are correctly paginated
  • Documentation is accurate and comprehensive
  • Security practices are aligned with industry standards
  • Response headers include caching directives
  • Rate limits are set and communicated in headers
  • Compliance with REST constraints and limitations

Output

  • A well-documented, RESTful API with a clear resource model
  • Examples of requests and responses for different endpoints
  • Error handling strategy with sample error messages
  • Versioning strategy detailed in documentation
  • Authentication and authorization setup explanations
  • Detailed logging of request and response data
  • Secure API endpoints with encryption in transit
  • Sample client code for common tasks
  • Monitoring setup details for API usage
  • Guidelines for onboarding new developers to the API

04 同仓库更多 Skills

0xharryriddle
0xharryriddle/codex-field-kit

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

前端开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

swarm-planner

[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

super-swarm-spark

Only to be triggered by explicit super-swarm-spark commands.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

role-creator

Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

read-github

Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo

Skill与智能体开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

planner

Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.

★ 3