self-improving-security

Log security findings to .learnings files and promote them to runbooks.

Updated Apr 13, 2026

Search Tags:#security #compliance #playbooks #vulnerabilities #learnings #incidents #hardening

Ready to run

npx skills add https://github.com/jose-compu/self-improving-skills --skill self-improving-security

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: self-improving-security
Source: https://github.com/jose-compu/self-improving-skills/tree/main/self-improving-security
Command: npx skills add https://github.com/jose-compu/self-improving-skills --skill self-improving-security

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This security self-improvement workflow helps teams log, categorize, and promote security findings (vulnerabilities, misconfigurations, incidents) into reusable skills and runbooks, ensuring consistent remediation and learning.

Core Features & Use Cases

Log vulnerabilities, misconfigurations, access violations, compliance gaps, and incident responses to dedicated .learnings files.
Promote broadly applicable findings to hardening checklists, runbooks, and security playbooks.
Extract and scale repeatable patterns into reusable SKILLs.

Quick Start

Log a newly discovered vulnerability to .learnings/SECURITY_INCIDENTS.md and start drafting a reusable SKILL from it.

Frequently Asked Questions about self-improving-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I capture security learnings from incidents and vulnerabilities into reusable playbooks?▼

You can capture security learnings by logging vulnerabilities and incidents to dedicated .learnings files, then promoting broadly applicable findings into reusable runbooks, hardening checklists, and security playbooks for consistent remediation.

How does promoting security findings to HARDENING.md and PLAYBOOKS.md improve continuous security improvement?▼

Promoting security findings to files like HARDENING.md and PLAYBOOKS.md extracts repeatable patterns from incidents and misconfigurations, turning isolated remediations into scalable hardening items and operational runbooks for continuous security improvement.

Can I log cloud misconfigurations and access violations across different environments using this security learning workflow?▼

Yes, this security learning workflow applies across code, cloud, and operational environments, allowing you to log misconfigurations, access violations, and compliance gaps while enforcing safe-logging requirements and recording metadata like entry IDs.

What is the best way to track compliance gaps and extract reusable SKILLs from security incidents?▼

The best way to track compliance gaps is logging them to .learnings/SECURITY_INCIDENTS.md with metadata like sources and entry IDs, then extracting and scaling repeatable remediation patterns into reusable SKILLs and documented runbooks.

Does this security self-improvement workflow support cross-linking incidents to compliance and hardening documentation?▼

Yes, the workflow supports cross-linking security incidents and vulnerabilities to documentation like COMPLIANCE.md, HARDENING.md, and TOOLS.md, ensuring that logged findings are systematically connected to relevant operational and compliance contexts.

When should I promote a logged security vulnerability to SOUL.md or AGENTS.md instead of keeping it in local .learnings files?▼

You should promote a logged vulnerability to SOUL.md or AGENTS.md when the security finding is broadly applicable across teams and environments, elevating isolated local learnings into permanent hardening items and shared operational guidance.