api-response-optimizer
Reduce payload size and enable compression.
Best use case
api-response-optimizer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Reduce payload size and enable compression.
Teams using api-response-optimizer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/api-response-optimizer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How api-response-optimizer Compares
| Feature / Agent | api-response-optimizer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Reduce payload size and enable compression.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Api Response Optimizer ## Purpose - Reduce payload size and enable compression. ## Preconditions - Access to system context (repos, infra, environments) - Confirmed requirements and constraints - Required approvals for security, compliance, or governance ## Inputs - Problem statement and scope - Current architecture or system constraints - Non-functional requirements (performance, security, compliance) - Target stack and environment ## Outputs - Design or implementation plan - Required artifacts (diagrams, configs, specs, checklists) - Validation steps and acceptance criteria ## Detailed Step-by-Step Procedures 1. Clarify scope, constraints, and success metrics. 2. Review current system state, dependencies, and integration points. 3. Select patterns, tools, and architecture options that match constraints. 4. Produce primary artifacts (docs/specs/configs/code stubs). 5. Validate against requirements and known risks. 6. Provide rollout and rollback guidance. ## Decision Trees and Conditional Logic - If compliance or regulatory scope applies -> add required controls and audit steps. - If latency budget is strict -> choose low-latency storage and caching. - Else -> prefer cost-optimized storage and tiering. - If data consistency is critical -> prefer transactional boundaries and strong consistency. - Else -> evaluate eventual consistency or async processing. ## Error Handling and Edge Cases - Partial failures across dependencies -> isolate blast radius and retry with backoff. - Data corruption or loss risk -> enable backups and verify restore path. - Limited access to systems -> document gaps and request access early. - Legacy dependencies with limited change tolerance -> use adapters and phased rollout. ## Tool Requirements and Dependencies - CLI and SDK tooling for the target stack - Credentials or access tokens for required environments - Diagramming or spec tooling when producing docs ## Stack Profiles - Use Profile A, B, or C from `skills/STACK_PROFILES.md`. - Note selected profile in outputs for traceability. ## Validation - Requirements coverage check - Security and compliance review - Performance and reliability review - Peer or stakeholder sign-off ## Rollback Procedures - Revert config or deployment to last known good state. - Roll back database migrations if applicable. - Verify service health, data integrity, and error rates after rollback. ## Success Metrics - Measurable outcomes (latency, error rate, uptime, cost) - Acceptance thresholds defined with stakeholders ## Example Workflows and Use Cases - Minimal: apply the skill to a small service or single module. - Production: apply the skill to a multi-service or multi-tenant system.
Related Skills
context-optimizer
Analyzes Copilot Chat debug logs, agent definitions, skills, and instruction files to audit context window utilization. Provides log parsing, turn-cost profiling, redundancy detection, hand-off gap analysis, and optimization recommendations. Use when optimizing agent context efficiency, identifying where to add subagent hand-offs, or reducing token waste across agent systems.
agentv-prompt-optimizer
Iteratively optimize prompt files against AgentV evaluation datasets by analyzing failures and refining instructions.
image-optimizer
Optimize and compress images for web use. Reduces file sizes of JPEG, PNG, GIF images using lossy/lossless compression. Can resize images to maximum dimensions, convert to WebP format, and process entire directories recursively. Use when images are too large for web, need compression, or need format conversion.
article-title-optimizer
This skill analyzes article content in-depth and generates optimized, marketable titles in the format 'Title: Subtitle' (10-12 words maximum). The skill should be used when users request title optimization, title generation, or title improvement for articles, blog posts, or written content. It generates 5 title candidates using proven formulas, evaluates them against success criteria (clickability, SEO, clarity, emotional impact, memorability, shareability), and replaces the article's title with the winning candidate.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
internal-linking-optimizer
Use when the user asks to "fix internal links", "improve site architecture", "link structure", "distribute page authority", "internal linking strategy", "orphan pages", "site architecture is messy", or "pages have no links pointing to them". Analyzes and optimizes internal link structure to improve site architecture, distribute page authority, and help search engines understand content relationships. Creates strategic internal linking plans. For a broader on-page audit, see on-page-seo-auditor. For external link analysis, see backlink-analyzer.
performance-optimizer
Performance analysis, profiling techniques, bottleneck identification, and optimization strategies for code and systems. Use when the user needs to improve performance, reduce resource usage, or identify and fix performance bottlenecks.
Incident Response
Incident response is a systematic approach to handling security breaches and incidents to minimize damage, reduce recovery time, and prevent future occurrences. Effective incident response includes pr
dan_dual_response_simulation
Simulate an unrestricted AI (DAN) alongside a standard AI, providing dual responses with mode-switching capabilities and matching the user's language.
apiresponse-class
Structure of ApiResponse class.
api-response-patterns
API response wrapper patterns for consistent, predictable REST APIs in ABP Framework. Use when: (1) designing uniform API response contracts, (2) implementing success/error response wrappers, (3) handling pagination and metadata, (4) standardizing error responses.
api-response-optimization
Optimizes API performance through payload reduction, caching strategies, and compression techniques. Use when improving API response times, reducing bandwidth usage, or implementing efficient caching.