creator/Anthropic-Cybersecurity-Skills
1
0
Fork 0
mirror of https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git synced 2026-09-02 06:30:50 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs(skills): rewrite container-security descriptions to a uniform standard

Browse Source 
All 33 container-security skills now carry what it does, an explicit
"Use when" trigger, keywords, and a negative trigger naming the nearest
neighbour. Six collision clusters resolved by differentiating scope
rather than merging, so no skill is removed:

- kube-bench: running the tool vs interpreting findings into an audit
- Calico: portable upstream NetworkPolicy vs Calico-as-CNI vs Calico-only
  CRDs (GlobalNetworkPolicy, HostEndpoint, DNS egress)
- Falco: deploying and operating it vs authoring escape rules
- container escape: tool-agnostic runtime signals vs Falco rule syntax vs
  static posture audit vs offensive breakout
- Trivy: all-target platform and operator vs single-image scan
- Docker: images and Dockerfiles vs daemon.json vs the CIS audit script

Also replaces the templated "When to Use" boilerplate in these files,
including bullets that only restated the skill's own name.

Worst pair (Pod Security Standards vs Pod Security Admission) drops from
0.77 cosine to below the 0.45 threshold. Repo-wide: colliding pairs
60 -> 56, skills involved 105 -> 94.
This commit is contained in:
Mahipal
2026-08-23 17:15:30 +02:00
parent a81b233649
commit 6972fe933e
33 changed files with 300 additions and 149 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/detecting-container-escape-with-falco-rules/SKILL.md
+9 -1
View File
@@ -1,6 +1,14 @@
---
name: detecting-container-escape-with-falco-rules
description: Write and tune Falco rules that monitor Linux syscalls to detect container escape techniques in real time, including host filesystem mounts, sensitive host path access, kernel module loading, and abuse of privileged container capabilities. Use when deploying or tuning Falco for a Kubernetes/container environment, or when investigating an alert tied to syscall-level escape behavior.
description: >-
Writes and tunes Falco rule syntax for container escape detection - conditions, macros,
lists, priorities, and output fields - covering host filesystem mounts, sensitive host path
access, kernel module loading, and privileged capability abuse, including how to drive down
false positives. Use when authoring or tuning a specific Falco rule for breakout behaviour,
or triaging a noisy escape-related Falco alert. Keywords: Falco rule, macro, list,
condition, priority, falco_rules.local.yaml, tuning, false positive. Do not use for
deploying and operating Falco itself - use detecting-container-runtime-threats-with-falco;
for tool-agnostic escape signals use detecting-container-escape-attempts.
domain: cybersecurity
subdomain: container-security
tags: