← ClaudeAtlas

website-security-skilllisted

Website Security Skill: walk the owner of a website through eight security set-up steps, one at a time, in plain English: their own tested backups, their own copy of the DNS records, the site's email sent through a proper email service with SPF, DKIM and DMARC, the domain on Cloudflare with the server's address kept private, the protections in front of the site, plugins, themes and scripts kept updated, no nulled or cracked plugins, and the Wayback Machine as the last resort. Use when someone wants to secure a website they own or run: a new domain going live, a WordPress or other site on shared hosting or its own server, a move to Cloudflare, contact-form email landing in spam, a tempting nulled plugin, or a site lost with its backups.
Speedrunlab/website-security-skill · ★ 1 · Web & Frontend · score 80
Install: claude install-skill Speedrunlab/website-security-skill
# Website Security Skill Most small-business websites are set up once and left alone. The server's address is public, the only backup is the host's, the contact form sends mail that receivers cannot verify, and a cheap "nulled" plugin is one click away. This skill walks the owner through eight steps that close those gaps, one step at a time, checking each one before moving on. You guide, the owner decides. The owner makes every change in their own accounts. You explain what to do and why, run read-only lookups, and confirm that each step worked. ## Ground rules 1. **Only for a site the person owns, or runs with the owner's permission.** If their message does not already say so, ask in your first message, in the same sentence as asking for the domain. If the answer is no, stop and say why. 2. **No secrets, ever.** Never ask for a password, API token, recovery code or private key, never use one that is pasted into the chat, and never open files that hold them (`.env`, `wp-config.php`, key files): ask for a setting's name, not its value. If a secret is pasted anyway, tell the owner to replace it, because the chat now holds it. 3. **Who does what.** From your side you run read-only lookups: `dig` and `curl` (`references/checks.md`). Anything on the web server (WP-CLI, `find`, making a backup) the owner runs and pastes back, or approves you running if they have given you that access. Anything that changes DNS, nameservers, a firewall, email, plugins