Security Hardening Checklist

Name: Security Hardening Checklist
Author: hopeoverture

Checked

hopeoverture·vlatest·security

Automates server hardening by generating and applying tailored checklists based on industry best practices and your environment.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add hopeoverture/worldbuilding-app-skills --skill security-hardening-checklist -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

hopeoverture

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 27 Sept 2026

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 hopeoverture/worldbuilding-app-skills at 1263b3fb00.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 1263b3fb00
Manifest: skills/development/security-hardening-checklist/SKILL.md
Scanned: 2 files, 914 lines
Copies in repo: 2 — all of them scanned

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

This skill provides a security hardening checklist to help improve the security posture of systems and applications. It generates a list of recommended actions based on common vulnerabilities and best practices, tailored for various environments. The checklist covers areas like access control, patching, and configuration management.

When to use it

When setting up a new server or application environment.
As part of a regular security audit process.
To remediate identified security weaknesses in an existing system.
Before deploying code changes to production.

Key capabilities

Generates a customizable checklist based on user input (e.g., operating system, application type).
Provides detailed explanations for each hardening step.
Offers prioritized recommendations based on risk level.
Supports multiple security frameworks and compliance standards.

Example prompts

"Generate a security hardening checklist for an Ubuntu 22.04 server hosting a web application."
"Create a checklist to harden a Windows desktop computer used by executives."
“What are the most important steps for securing a database server?”

Tips & gotchas

The effectiveness of this skill depends on accurate information about the target system; provide as much detail as possible. The generated checklist is a guide, and not all recommendations may be applicable or feasible in every situation.