problem-details-rfc9457
Use when implementing exception mapping or RFC 9457 error responses in Spring Boot 3. Preserve an existing legacy error contract unless migration is requested.
Install / Use
npx skills add rrezartprebreza/spring-boot-skills --skill problem-details-rfc9457Installs into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of problem-details-rfc9457
problem-details-rfc9457 scores 83/100 on our quality scale, 940th of 1,098 Security skills we index.
Its SKILL.md is 4.0 KB long, split into 7 sections with 2 code examples: a solid amount of guidance for an agent.
It has 334 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 24 days ago, so problem-details-rfc9457 is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-11-22. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
problem-details-rfc9457 compared with similar skills
All 4 of these similar skills score higher than problem-details-rfc9457; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| problem-details-rfc9457 (this skill)by rrezartprebreza | 83 | 334 | 24d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 114.0k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 80.5k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 104.9k | 5d ago | MCP Server |
| crawl4aiby unclecode | 100 | 87.7k | 2d ago | MCP Server |
Frequently asked questions
- How do I install problem-details-rfc9457?
- Run
npx skills add rrezartprebreza/spring-boot-skills --skill problem-details-rfc9457. The install tabs above show the steps for each supported agent. - Which AI agents does problem-details-rfc9457 work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is problem-details-rfc9457 safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is problem-details-rfc9457 still maintained?
- The repository was last updated 24 days ago, so problem-details-rfc9457 is actively maintained.
Skill content
View source on GitHubname: problem-details-rfc9457 description: > Use when implementing exception mapping or RFC 9457 error responses in Spring Boot 3. Preserve an existing legacy error contract unless migration is requested.
Problem Details - RFC 9457
Choose the error contract
Inspect existing advice, security entry points and API tests first. Keep one error policy per API. Success DTOs or success envelopes can coexist with Problem Details errors: RFC 9457 specifies errors, not success representations.
For an API using Problem Details, enable Spring's built-in MVC exception handling:
spring:
mvc:
problemdetails:
enabled: true
For WebFlux use spring.webflux.problemdetails.enabled and reactive exception handling;
the servlet templates below are not WebFlux handlers.
Domain errors
Use the compiled DomainException together with ProblemDetailExceptionHandler. The handler maps all subclasses using their declared status and stable error code:
- OrderNotFoundException: 404.
- InsufficientInventoryException: 422.
- BusinessRuleViolationException: 422.
Each public class has its own file. These are API-facing exceptions with HTTP status metadata; for a framework-free domain, keep domain exceptions independent and map them in the web adapter. Do not expose arbitrary persistence or infrastructure exception messages.
The advice extends ResponseEntityExceptionHandler to preserve Spring's handling of framework
exceptions. Validation returns 400 with field violations; unexpected failures return a generic
500 while retaining the full exception only in server logs. Keep nullable validation messages safe.
Filter-level authentication failures need an AuthenticationEntryPoint; authorization failures
need an AccessDeniedHandler. Controller advice does not cover the security filter chain.
Method-security (@PreAuthorize) denials are the opposite case: AccessDeniedException is thrown
inside the dispatcher, so the advice must map it to 403 or the Exception catch-all returns 500.
Response fields
{
"type": "https://api.example.com/errors/order_not_found",
"title": "Not Found",
"status": 404,
"detail": "Order not found",
"instance": "/api/orders/123",
"errorCode": "ORDER_NOT_FOUND"
}
Use project-owned, stable URIs for custom problem types. An explicit type is optional;
when omitted it defaults to about:blank. Its title should then match the HTTP status phrase.
The HTTP status and the body status must agree. Use application/problem+json for JSON problems.
Use extensions such as errorCode or violations for machine-readable details instead of
requiring clients to parse human-readable messages.
Verification
Test actual HTTP responses for domain 404/422, validation 400, unexpected 500, and framework errors such as malformed JSON and unsupported methods. Assert content type, status, stable error codes and absence of stack traces or internal messages. Separately test filter 401/403. The repository verification fixture imports these exact templates for both Boot versions.
Official sources
Gotchas
- Agent handles a different exception class than the domain throws - test the concrete exceptions.
- Agent forces Problem Details into an existing legacy API - preserve its contract unless asked to migrate.
- Agent requires an explicit type for every error - about:blank is the default.
- Agent treats success envelopes and Problem Details as incompatible - only error policy must be consistent.
- Agent relies on advice for filter exceptions - configure the security handlers separately.
- Agent returns internal exception messages in 500 responses - log privately and return generic detail.
Related Skills
Agent-Reach
114.0kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
80.5kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Scrapling
104.9k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
crawl4ai
87.7kOfficial Crawl4AI Cloud: a hosted web scraping, extraction, and search API for AI agents. Free API key, 1,000 credits a month, no card. Fully open source: this repo is the Apache-2.0 crawler that powers it, and you can self-host it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
