skills.rest
Lbstrydom
LbstrydomCOMMUNITY
Explore all skills by this author →
GitHub

security-strategy

Maintain per-repo security memory as a threat model and incident log.

Updated Mar 25, 2026
Search Tags:#automation#security#docs#threat-model#memory-management#incident-management
One-click install
npx skills add https://github.com/Lbstrydom/claude-engineering-skills --skill security-strategy-lbstrydom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-strategy
Source: https://github.com/Lbstrydom/claude-engineering-skills/tree/main/.claude/skills/security-strategy
Command: npx skills add https://github.com/Lbstrydom/claude-engineering-skills --skill security-strategy-lbstrydom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

On-demand maintenance of the per-repo security memory by bootstrapping an initial threat model and appending incidents to docs/security-strategy.md, ensuring a single source of truth that stays in sync with an embedding index.

Core Features & Use Cases

  • On-demand bootstrap of the threat model and initial incident
  • Interactive addition of new incidents
  • Pre-fill incident data from commits to speed up drafting
  • After edits, trigger npm run security:refresh to refresh the embedding index
  • Uses a strict parse/replace routine to keep docs/security-strategy.md in sync and surface parse warnings to avoid malformed memory blocks

Quick Start

Initiate bootstrap to seed the initial threat model and first incident

Frequently Asked Questions about security-strategy

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

FAQPage Schema
How do I maintain a living threat model and incident log for my repository?▼

A living threat model is maintained by bootstrapping an initial security memory file and interactively appending new incidents to a single source of truth. This keeps the repository security strategy updated and synchronized with an embedding index.

Can I pre-fill incident data from git commits to speed up security drafting?▼

Yes, you can pre-fill incident data from commits to speed up drafting. This automation accelerates the documentation process by pulling relevant commit context directly into the incident log before you finalize the record.

How does the security memory sync with the embedding index after adding an incident?▼

Security memory syncs with the embedding index by running a refresh command after edits are written atomically. This routine updates the index to ensure the latest threat model and incident log changes are accurately reflected.

How to prevent malformed memory blocks when updating repository security docs?▼

To prevent malformed memory blocks when updating security docs, a strict parser validates edits and surfaces parse warnings before writing atomically. This routine ensures the markdown memory blocks remain structurally valid and synchronized.

Does this threat model automation require external dependencies to manage security docs?▼

No external dependencies are required to manage security docs with this threat model automation. The routine operates independently to parse, write, and refresh the repository security memory without additional package installations.

Related Skills

Explore More Software Engineering Skills→
u9401066u9401066

project-init

Initialize a new project from a template with Git reset and configuration.

Community
Basic
dapperdiversdapperdivers
1

threat-intel-aggregator

Aggregate threat intelligence feeds and vulnerability data into daily security briefings.

Community
Advanced
luansilvadbluansilvadb

resilient-build

Orchestrate resilient build pipelines with per-step checkpoints and atomic delivery.

Community
Advanced
statick88statick88
1

security-compliance

Guide security professionals in implementing defense-in-depth architectures and achieving SOC2, ISO27001, GDPR, and HIPAA compliance.

Community
Advanced