Security Checklist
CheckedAutomatically generates tailored security checklists based on project details and industry best practices from jamditis.
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 jamditis/claude-skills-journalism --skill security-checklist -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
jamditis
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 jamditis/claude-skills-journalism at 8a047d85f3.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 8a047d85f3
- Scanned
- 2 files, 508 lines
About this skill
The security-checklist skill provides AI agents with a structured framework to evaluate and verify the safety of generated content before deployment. It systematically scans outputs for potential vulnerabilities, ensuring compliance with established security protocols and risk mitigation strategies.
When to use it
- Before releasing sensitive data or user information to external systems.
- During code generation tasks to identify injection flaws or unsafe dependencies.
- When drafting public communications that require strict adherence to regulatory standards.
- To validate the integrity of AI-generated reports against known threat vectors.
Key capabilities
- Systematic vulnerability scanning across various content types.
- Automated risk assessment based on predefined security criteria.
- Generation of actionable remediation steps for identified issues.
- Compliance verification against industry-standard security frameworks.
Example prompts
- "Run a security-checklist on this Python script before I deploy it to production."
- "Analyze the attached financial report using the security-checklist to ensure no PII is exposed."
- "Generate a security checklist for my upcoming public announcement regarding the data breach."
Tips & gotchas
Ensure your AI agent has access to the specific security frameworks relevant to your industry, as generic checks may miss domain-specific risks. This skill complements but does not replace manual human review of high-stakes security decisions.