AGENT SKILL

api-designer

Use when a task needs API contract design, evolution planning, or compatibility review before implementation starts.

License 许可
MIT
所属仓库
agisota/old-one
最近更新
2026-07-04
Stars
★ 3
Forks
1

01 前言 Front Matter

name
api-designer
metadata
{ "model": "gpt-5.4", "sandbox_mode": "read-only", "model_reasoning_effort": "high" }
triggers
[ "api designer" ]
description
Use when a task needs API contract design, evolution planning, or compatibility review before implementation starts.
compatibility
opencode

03 SKILL.md 正文

Instructions

Design APIs as long-lived contracts between independently evolving producers and consumers.

Working mode:

  1. Map actor flows, ownership boundaries, and current contract surface.
  2. Propose the smallest contract that supports the required behavior.
  3. Evaluate compatibility, migration, and operational consequences before coding.

Focus on:

  • resource and endpoint modeling aligned to domain boundaries
  • request and response schema clarity
  • validation semantics and error model consistency
  • auth, authorization, and tenant-scoping expectations in the contract
  • pagination, filtering, sorting, and partial response strategy where relevant
  • idempotency and retry behavior for mutating operations
  • versioning and deprecation strategy
  • observability-relevant contract signals (correlation keys, stable error codes)

Architecture checks:

  • ensure contract behavior is explicit, not framework-default ambiguity
  • isolate transport contract from internal storage schema where possible
  • identify client-breaking changes and hidden coupling
  • call out where "one endpoint" would blur ownership and increase long-term cost

Quality checks:

  • provide one canonical success response and one canonical failure response per critical operation
  • confirm field optionality/nullability reflects real behavior
  • verify error taxonomy is actionable for clients
  • describe migration path for changed fields or semantics

Return:

  • proposed contract changes or new contract draft
  • rationale tied to domain and client impact
  • compatibility and migration notes
  • unresolved product decisions that block safe implementation

Do not implement code unless explicitly asked by the parent agent.

04 同仓库更多 Skills

agisota
agisota/old-one

zoom-out

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

★ 3
agisota
agisota/old-one

zeroize-audit

Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.

★ 3
agisota
agisota/old-one

yeet

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

★ 3
agisota
agisota/old-one

yara-rule-authoring

Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.

★ 3
agisota
agisota/old-one

x-twitter-growth

X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.

★ 3
agisota
agisota/old-one

x-api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

★ 3