Discogs overview
Model-agnostic Agent Skills covering the entire public Discogs API (api.discogs.com).
npx -y skills add Nikolasgrizli/discogs-api-skills --skill discogs-overviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Cross-cutting conventions for the Discogs API (api.discogs.com) that apply to every endpoint. Make sure to use this skill whenever a Discogs request touches general API behaviour rather than one specific resource — setting the mandatory User-Agent, handling rate limiting (X-Discogs-Ratelimit headers, 60/min authenticated vs 25/min unauthenticated), paginating list responses (page / per_page, Link header, pagination object), pinning an API version via the Accept header, returning JSONP, or interpreting HTTP status codes (200/201/204/401/403/404) and empty responses from Discogs.
SKILL.md
2.4 KB, 493 tokens by cl100k_base, as published. Nobody here has run it
Discogs API — Overview & Conventions
Base URL: https://api.discogs.com. RESTful, JSON, currently v2 only.
User-Agent (mandatory)
Every request must send a unique, descriptive User-Agent (RFC 1945 style),
e.g. MyDiscogsClient/1.0 +http://mydiscogsclient.org. Missing or generic
agents get an empty response or are silently blocked. Don't copy the docs'
examples verbatim.
Rate limiting
Throttled by source IP: 60 req/min authenticated, 25 req/min unauthenticated
(moving 60-second window). Track via response headers:
X-Discogs-Ratelimit, X-Discogs-Ratelimit-Used, X-Discogs-Ratelimit-Remaining.
A unique User-Agent is required to get the max rate. Throttle locally.
Pagination
List endpoints default to 50 items/page, max 100. Use ?page= and
?per_page=. Responses carry a Link header (rel=next/prev/first/last) and a
pagination object (page, pages, items, per_page, urls).
Versioning (Accept header)
Future-proof with Accept: application/vnd.discogs.v2.<format>+json where
<format> is discogs (default), html, or plaintext. Unknown/absent →
defaults to discogs.
JSONP
Add ?callback=name; status and headers are wrapped in the body
({"meta":{"status":200},"data":{…}}) since JSONP can't read real headers.
HTTP status codes
| Code | Meaning |
|---|---|
| 200 OK | Success, data in body |
| 201 Created | POST created a resource; new ID in body |
| 204 No Content | Success, empty body |
| 401 Unauthorized | Needs authentication (see discogs-authentication) |
| 403 Forbidden | Authenticated but not allowed (e.g. editing another user) |
| 404 Not Found | Often a modified/signed image URL or wrong ID |
Auth details live in [[discogs-authentication]]. Full text, FAQ, and client library links are in reference.md.
Gives 0 of the 12 instructions most apis services skills give in 493 tokens
Counted across 424 of the 426 authors here whose files we hold, read 2026-08-06
- use plural nouns for resource namesin 41 of 424, across 32 files
- use cursor-based pagination for large datasetsin 35 of 424, across 20 files
- include rate limit headers in responsesin 25 of 424, across 13 files
- Use kebab-case for multi-word resourcesin 23 of 424, across 13 files
- version APIs in the URL pathin 19 of 424, across 9 files
- use semantic HTTP status codesin 18 of 424, across 8 files
- verify webhook signaturesin 18 of 424, across 11 files
- use query parameters for filteringin 17 of 424, across 6 files
- use async database operationsin 14 of 424, across 7 files
- wrap successful responses in a data fieldin 13 of 424, across 3 files
- prefix sorting parameters with a hyphen for descending orderin 13 of 424, across 3 files
- set appropriate HTTP status codesin 13 of 424, across 6 files
Said here and by no other author read
- send a unique descriptive User-Agent on every request
- do not copy the docs' User-Agent examples verbatim
- track rate limits via the X-Discogs-Ratelimit response headers
- throttle requests locally
- use page and per_page query parameters for pagination
- use the pagination object or Link header to navigate pages
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.