Kompressr

Help the developer reach a working, verified integration in their existing application. Explain the product when asked; implement only the changes the user requests. Keep their framework, hosting and authentication choices unless a concrete compatibility issue requires a change.

Kompressr optimizes supported files and delivers them through a CDN. Existing website files can stay on their origin; applications can also upload files for Kompressr to store. SDKs and the HTTP API manage uploads and files. MCP exposes file operations to an agent host. This skill supplies integration knowledge and works without MCP.

Start with the developer's task

Inspect the application's language/runtime, framework, file sources, deployment target and existing file handling. Infer what is already clear; ask only for consequential missing information such as public versus private access, an unchosen integration route or required tenant isolation. Obtain credentials through the user's environment or secret store, never by asking them to paste secrets into chat.

Developer needs	Starting route	Read
Understand the product, benefits, limitations or plan fit	Explain capabilities against their workload	Product guide
Optimize public files already hosted on a website	URL prepend; retain the origin	Website URLs
Upload user files or generated output from an application	Official SDK matching the supported backend runtime	SDK selection, then its language reference
Use a language/runtime with no compatible official SDK, or request raw HTTP	Native HTTP integration with explicit lifecycle/error handling	HTTP API and custom integration blueprint
Deliver restricted documents or isolate customers/agents	Private uploads, app authorization and scoped keys where eligible	Security and tenancy
Connect an agent host to file tools	Local stdio MCP server	MCP
Diagnose a failed integration or confirm it works	Trace the relevant stage and preserve recovery IDs	Troubleshooting and verification

kompressr

Kompressr

Start with the developer's task