504-frameworks-micronaut-security — Claude Code skill
The 504-frameworks-micronaut-security skill reviews and improves Micronaut application security, covering authentication, route authorization, JWT, CORS, and safe handling of sensitive data.
Apache-2.0 282 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 504-frameworks-micronaut-security -a claude-codeWhat 504-frameworks-micronaut-security does
The skill covers micronaut-security setup, authentication, @Secured annotations, intercept-url-map rules, role policies, JWT and session strategies, SecurityService checks, CORS, browser-focused CSRF awareness, and rejection handlers. It also addresses sensitive information in logs and responses.
Its workflow uses references/504-frameworks-micronaut-security.md as the detailed guide. The agent inspects the project, defines the smallest safe change set, updates security configuration or code, then reports verification results. It must run ./mvnw compile or mvn compile before editing and stop when compilation fails. After the changes, it runs ./mvnw clean verify or mvn clean verify.
What it helps with
- configure authentication for a Micronaut app
- protect routes with role-based rules
- add JWT security to an API
- review
@Securedpolicies - keep sensitive values out of logs
Example prompts for the agent
- Review this Micronaut project's security configuration and suggest the smallest safe set of fixes.
- Add JWT protection to the API and check authorization for its routes.
- Review
@Securedandintercept-url-map, then run the full verification.
How to install 504-frameworks-micronaut-security
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 504-frameworks-micronaut-security -a claude-code2Manually: put the files in place
~/.claude/skills/504-frameworks-micronaut-security/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/504-frameworks-micronaut-security/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 504-frameworks-micronaut-security -a codex2Manually: put the files in place
.agents/skills/504-frameworks-micronaut-security/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 504-frameworks-micronaut-security -a cursor2Manually: put the files in place
.cursor/skills/504-frameworks-micronaut-security/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/504-frameworks-micronaut-security2Manually: put the files in place
.github/skills/504-frameworks-micronaut-security/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 504-frameworks-micronaut-security -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/504-frameworks-micronaut-securityManually: put the files in place
.devin/skills/504-frameworks-micronaut-security/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 504-frameworks-micronaut-security -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 504-frameworks-micronaut-security
How do I install 504-frameworks-micronaut-security in Claude Code?
Run npx skills add jabrena/plinth --skill 504-frameworks-micronaut-security -a claude-code. The skill will be available at ~/.claude/skills/504-frameworks-micronaut-security/SKILL.md.
What does 504-frameworks-micronaut-security do?
It guides security work in Micronaut applications, including authentication, route authorization, JWT and session strategies, CORS, CSRF awareness, denial handling, and sensitive-data-safe logging.
What must happen before security changes are applied?
The agent reads references/504-frameworks-micronaut-security.md and runs ./mvnw compile or mvn compile first. If compilation fails, it stops before making changes.
Source text
SKILL.md · Apache-2.0
--- name: 504-frameworks-micronaut-security description: Use when you need to design, review, or improve security in Micronaut applications — including micronaut-security authentication, @Secured and intercept-url-map rules, JWT/session strategies, SecurityService checks, CORS, CSRF awareness for browser apps, rejection handlers, and sensitive-data-safe logging. This should trigger for requests such as Add Micronaut security support; Review Micronaut security configuration; Improve API authorization in Micronaut; Add JWT security in Micronaut; Harden Micronaut route authorization rules. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # Micronaut Security Guidelines Apply Micronaut security best practices with secure-by-default API boundaries. **What is covered in this Skill?** - Micronaut security configuration and authentication setup - Authorization with @Secured and role-based policies - Endpoint and route protection strategy - Least-privilege design and policy boundaries - Secure error/denial behavior - Sensitive data handling in logs and responses **Scope:** Apply recommendations based on the reference rules and good/bad examples. ## Constraints Before applying security changes, ensure the project compiles. After improvements, run full verification. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change - **SAFETY**: If compilation fails, stop immediately - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **BEFORE APPLYING**: Read the reference for detailed rules and examples ## When to use this skill - Add Micronaut security support - Review Micronaut security configuration - Improve API authorization in Micronaut - Add JWT security in Micronaut - Harden Micronaut route authorization rules - Implement @Secured policies in Micronaut controllers ## Workflow 1. **Read reference and assess project context** Read `references/504-frameworks-micronaut-security.md` and inspect the current project setup before proposing changes. 2. **Gather scope and decide target improvements** Identify requested outcomes, constraints, and the minimum safe set of changes to apply. 3. **Apply framework-aligned changes** Implement or refactor security-related configuration/code following the reference patterns and project conventions. 4. **Run verification and report results** Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions. ## Reference For detailed guidance, examples, and constraints, see [references/504-frameworks-micronaut-security.md](references/504-frameworks-micronaut-security.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth