Fortify Security
CheckedAutomatically identifies and remediates network vulnerabilities using Gravito's framework to strengthen system defenses.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add gravito-framework/gravito --skill fortify-security -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
gravito-framework
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned gravito-framework/gravito at ae0db3aa40.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- ae0db3aa40
- Scanned
- 1 file, 29 lines
About this skill
What it does
The Fortify Security skill enables an AI agent to automatically identify and remediate network vulnerabilities within applications, leveraging the Gravito ecosystem. It focuses on strengthening system defenses by assessing risks, implementing security measures like PlanetFortify and PlanetSentinel, and enforcing security standards. This process aims to protect sensitive endpoints (authentication, administration, payments) while maintaining a positive developer experience.
When to use it
- When you need to quickly identify and address potential vulnerabilities in your application's network defenses.
- To implement robust authentication methods like JWT, Session, or Passkey using PlanetSentinel.
- For configuring security headers with PlanetFortify to shield applications from threats.
- To ensure compliance with CSP (Content Security Policy) best practices.
Key capabilities
- Risk Assessment: Identifies sensitive endpoints and reviews existing CSP and CORS policies.
- Shielding: Configures PlanetFortify for robust security headers.
- Authentication: Implements PlanetSentinel for JWT, Session, or Passkey authentication.
- Middleware Implementation: Adds rate-limiting and validation filters to critical routes.
- CSP Enforcement: Promotes the use of Strict CSP policies.
- CSRF Protection: Implements CSRF protection for stateful endpoints.
- Dependency Vulnerability Auditing: Encourages regular audits of dependency vulnerabilities.
Example prompts
- "Assess the security risks associated with my authentication endpoint."
- "Implement JWT authentication using PlanetSentinel on this route: /api/users"
- "Configure PlanetFortify to apply a default security policy snippet."
Tips & gotchas
- This skill relies on components within the Gravito ecosystem (PlanetFortify, PlanetSentinel). Ensure these are available and configured correctly.
- Strict CSP policies should be implemented cautiously; avoid
unsafe-inlineunless absolutely necessary. - Refer to the
./references/csp-best-practices.mdfile for detailed guidance on Content Security Policy best practices.