[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P6SXSQPJRES78YF4S4MYQZ":3,"skill-same:01M6P6SXSQPJRES78YF4S4MYQZ":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":29,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6P6SXSQPJRES78YF4S4MYQZ","incident-response",null,"Handle security incidents with IR playbooks and procedures.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fincident-response\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"incident response","incident","for","github","incidents","with","relevant","helper","scope","critical","active","main","community","agent-skills","only","devops","vault","devops-security","license","assessment","2026-11-10 10:12:30",false,"---\nname: incident-response\ndescription: Handle security incidents with IR playbooks and procedures.\ncategory: security\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills\nsource_repo: BagelHole\u002FDevOps-Security-Agent-Skills\nsource_type: community\ndate_added: '2026-09-20'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills\u002Fblob\u002Fmain\u002FLICENSE\ncompatibility: Requires the relevant security tooling (scanners, vault CLIs) and an\n  authorized scope for any active assessment. Docs-only; helper scripts and templates\n  not bundled.\nmetadata:\n  author: devops-skills\n  version: '1.0'\n---\n\n# Incident Response\n\nHandle security incidents effectively with structured response procedures.\n\n## Prerequisites\n\n- IR team roster with on-call rotation and escalation paths\n- Secure communication channel (separate from production systems)\n- Forensic workstation with analysis tools installed\n- Evidence storage with chain-of-custody controls\n- Legal counsel contact information\n- Pre-authorized incident response actions documented\n\n## Incident Response Phases\n\n```yaml\nphases:\n  1_preparation:\n    - IR team roster and 24\u002F7 contact info\n    - Tools and privileged access ready\n    - Playbooks documented and tested\n    - Evidence collection kit prepared\n    - Communication templates drafted\n\n  2_detection:\n    - Alert triage and validation\n    - Initial assessment and scoping\n    - Severity classification\n    - Incident ticket creation\n\n  3_containment:\n    - Short-term containment (stop bleeding)\n    - Evidence preservation (before changes)\n    - System isolation (network\u002Fhost level)\n    - Credential rotation if needed\n\n  4_eradication:\n    - Root cause analysis\n    - Remove threat actor access\n    - Patch exploited vulnerabilities\n    - Clean compromised systems\n\n  5_recovery:\n    - System restoration from clean backups\n    - Enhanced monitoring deployment\n    - Phased return to production\n    - Business continuity verification\n\n  6_lessons_learned:\n    - Post-incident review (within 72 hours)\n    - Timeline reconstruction\n    - Documentation update\n    - Process and detection improvements\n```\n\n## Severity Classification\n\n| Level | Impact | Response Time | Examples |\n|-------|--------|---------------|----------|\n| Critical (P1) | Active data breach, full outage, ransomware | Immediate (\u003C 15 min) | Data exfiltration in progress, ransomware spreading |\n| High (P2) | Service degraded, potential breach | \u003C 1 hour | Unauthorized admin access, malware detected |\n| Medium (P3) | Limited impact, contained | \u003C 4 hours | Phishing compromise (single user), policy violation |\n| Low (P4) | Minimal impact | Next business day | Failed brute force, blocked scanning activity |\n\n## Evidence Collection Scripts\n\n### Linux Evidence Collection\n\n```bash\n#!\u002Fbin\u002Fbash\n# linux-evidence-collect.sh - Collect forensic evidence from a Linux host\n# Run with sudo. Preserves evidence with timestamps and hashes.\n\nset -euo pipefail\n\nEVIDENCE_DIR=\"\u002Fevidence\u002F$(hostname)-$(date +%Y%m%d-%H%M%S)\"\nmkdir -p \"$EVIDENCE_DIR\"\nLOGFILE=\"$EVIDENCE_DIR\u002Fcollection.log\"\n\nlog() { echo \"[$(date -u +%Y-%m-%dT%H:%M:%SZ)] $*\" | tee -a \"$LOGFILE\"; }\n\nlog \"Starting evidence collection on $(hostname)\"\nlog \"Collector: $(whoami)\"\nlog \"System time: $(date -u)\"\n\n# System information\nlog \"Collecting system information...\"\nuname -a > \"$EVIDENCE_DIR\u002Funame.txt\"\ncat \u002Fetc\u002Fos-release > \"$EVIDENCE_DIR\u002Fos-release.txt\"\nuptime > \"$EVIDENCE_DIR\u002Fuptime.txt\"\ndate -u > \"$EVIDENCE_DIR\u002Fsystem-time.txt\"\n\n# Running processes (full command line)\nlog \"Collecting process list...\"\nps auxwwf > \"$EVIDENCE_DIR\u002Fprocesses.txt\"\nps -eo pid,ppid,user,args --sort=-pcpu > \"$EVIDENCE_DIR\u002Fprocesses-by-cpu.txt\"\n\n# Network connections\nlog \"Collecting network state...\"\nss -tulnp > \"$EVIDENCE_DIR\u002Flistening-ports.txt\"\nss -anp > \"$EVIDENCE_DIR\u002Fall-connections.txt\"\nip addr show > \"$EVIDENCE_DIR\u002Fip-addresses.txt\"\nip route show > \"$EVIDENCE_DIR\u002Froutes.txt\"\niptables -L -n -v > \"$EVIDENCE_DIR\u002Fiptables.txt\" 2>&1 || true\ncat \u002Fetc\u002Fresolv.conf > \"$EVIDENCE_DIR\u002Fdns-config.txt\"\n\n# User activity\nlog \"Collecting user activity...\"\nlast -a > \"$EVIDENCE_DIR\u002Flogin-history.txt\"\nlastb > \"$EVIDENCE_DIR\u002Ffailed-logins.txt\" 2>&1 || true\nwho > \"$EVIDENCE_DIR\u002Fcurrently-logged-in.txt\"\nw > \"$EVIDENCE_DIR\u002Fuser-activity.txt\"\ncat \u002Fetc\u002Fpasswd > \"$EVIDENCE_DIR\u002Fpasswd.txt\"\ncat \u002Fetc\u002Fshadow > \"$EVIDENCE_DIR\u002Fshadow.txt\" 2>\u002Fdev\u002Fnull || true\ncat \u002Fetc\u002Fgroup > \"$EVIDENCE_DIR\u002Fgroup.txt\"\n\n# Scheduled tasks\nlog \"Collecting scheduled tasks...\"\nfor user in $(cut -f1 -d: \u002Fetc\u002Fpasswd); do\n  crontab -u \"$user\" -l 2>\u002Fdev\u002Fnull >> \"$EVIDENCE_DIR\u002Fcrontabs.txt\" && \\\n    echo \"--- $user ---\" >> \"$EVIDENCE_DIR\u002Fcrontabs.txt\"\ndone\nls -la \u002Fetc\u002Fcron.* > \"$EVIDENCE_DIR\u002Fcron-dirs.txt\" 2>&1\n\n# File system state\nlog \"Collecting filesystem state...\"\nfind \u002Ftmp \u002Fvar\u002Ftmp \u002Fdev\u002Fshm -type f -ls > \"$EVIDENCE_DIR\u002Ftemp-files.txt\" 2>\u002Fdev\u002Fnull\nfind \u002F -name \"*.sh\" -mtime -7 -ls > \"$EVIDENCE_DIR\u002Frecent-scripts.txt\" 2>\u002Fdev\u002Fnull\nfind \u002F -perm -4000 -type f -ls > \"$EVIDENCE_DIR\u002Fsuid-files.txt\" 2>\u002Fdev\u002Fnull\nfind \u002Fhome -name \".*history\" -ls > \"$EVIDENCE_DIR\u002Fhistory-files.txt\" 2>\u002Fdev\u002Fnull\n\n# Loaded kernel modules\nlog \"Collecting kernel modules...\"\nlsmod > \"$EVIDENCE_DIR\u002Fkernel-modules.txt\"\n\n# Open files\nlog \"Collecting open files...\"\nlsof -n > \"$EVIDENCE_DIR\u002Fopen-files.txt\" 2>\u002Fdev\u002Fnull\n\n# Systemd services\nlog \"Collecting service state...\"\nsystemctl list-units --type=service --all > \"$EVIDENCE_DIR\u002Fservices.txt\"\nsystemctl list-timers --all > \"$EVIDENCE_DIR\u002Ftimers.txt\"\n\n# Log preservation\nlog \"Preserving system logs...\"\ntar czf \"$EVIDENCE_DIR\u002Fvar-log.tar.gz\" \u002Fvar\u002Flog\u002F 2>\u002Fdev\u002Fnull\n\n# Docker containers (if present)\nif command -v docker &>\u002Fdev\u002Fnull; then\n  log \"Collecting Docker state...\"\n  docker ps -a > \"$EVIDENCE_DIR\u002Fdocker-containers.txt\"\n  docker images > \"$EVIDENCE_DIR\u002Fdocker-images.txt\"\n  docker network ls > \"$EVIDENCE_DIR\u002Fdocker-networks.txt\"\nfi\n\n# Kubernetes (if kubectl available)\nif command -v kubectl &>\u002Fdev\u002Fnull; then\n  log \"Collecting Kubernetes state...\"\n  kubectl get pods --all-namespaces > \"$EVIDENCE_DIR\u002Fk8s-pods.txt\" 2>\u002Fdev\u002Fnull\n  kubectl get events --all-namespaces --sort-by=.lastTimestamp > \"$EVIDENCE_DIR\u002Fk8s-events.txt\" 2>\u002Fdev\u002Fnull\nfi\n\n# Hash all evidence files\nlog \"Computing evidence hashes...\"\nfind \"$EVIDENCE_DIR\" -type f ! -name \"checksums.sha256\" -exec sha256sum {} \\; > \"$EVIDENCE_DIR\u002Fchecksums.sha256\"\n\nlog \"Evidence collection complete: $EVIDENCE_DIR\"\necho \"Total files collected: $(find \"$EVIDENCE_DIR\" -type f | wc -l)\"\n```\n\n### Memory Acquisition\n\n```bash\n#!\u002Fbin\u002Fbash\n# memory-capture.sh - Capture volatile memory for forensic analysis\n\nEVIDENCE_DIR=\"\u002Fevidence\u002Fmemory-$(hostname)-$(date +%Y%m%d-%H%M%S)\"\nmkdir -p \"$EVIDENCE_DIR\"\n\n# Using LiME (Linux Memory Extractor)\nif [ -f \u002Flib\u002Fmodules\u002F$(uname -r)\u002Fextra\u002Flime.ko ]; then\n  insmod \u002Flib\u002Fmodules\u002F$(uname -r)\u002Fextra\u002Flime.ko \"path=$EVIDENCE_DIR\u002Fmemory.lime format=lime\"\n  echo \"Memory captured with LiME\"\nfi\n\n# Alternative: \u002Fproc\u002Fkcore (partial, but always available)\ncp \u002Fproc\u002Fkcore \"$EVIDENCE_DIR\u002Fkcore\" 2>\u002Fdev\u002Fnull\n\n# Capture \u002Fproc\u002Fmeminfo for context\ncat \u002Fproc\u002Fmeminfo > \"$EVIDENCE_DIR\u002Fmeminfo.txt\"\n\n# Hash the memory dump\nsha256sum \"$EVIDENCE_DIR\"\u002F* > \"$EVIDENCE_DIR\u002Fchecksums.sha256\"\n```\n\n### AWS Evidence Collection\n\n```bash\n#!\u002Fbin\u002Fbash\n# aws-evidence-collect.sh - Collect evidence from compromised AWS resources\n\nINCIDENT_ID=\"${1:?Usage: $0 \u003Cincident-id>}\"\nINSTANCE_ID=\"${2:?Usage: $0 \u003Cincident-id> \u003Cinstance-id>}\"\nEVIDENCE_BUCKET=\"s3:\u002F\u002Fincident-evidence-${AWS_ACCOUNT_ID}\"\nEVIDENCE_PREFIX=\"${INCIDENT_ID}\u002F$(date +%Y%m%d-%H%M%S)\"\n\necho \"=== AWS Evidence Collection ===\"\necho \"Incident: $INCIDENT_ID\"\necho \"Instance: $INSTANCE_ID\"\n\n# Snapshot EBS volumes\necho \"Creating EBS snapshots...\"\nVOLUMES=$(aws ec2 describe-volumes \\\n  --filters \"Name=attachment.instance-id,Values=${INSTANCE_ID}\" \\\n  --query 'Volumes[].VolumeId' --output text)\n\nfor vol in $VOLUMES; do\n  SNAP_ID=$(aws ec2 create-snapshot \\\n    --volume-id \"$vol\" \\\n    --description \"IR Evidence - ${INCIDENT_ID} - ${vol}\" \\\n    --tag-specifications \"ResourceType=snapshot,Tags=[{Key=IncidentId,Value=${INCIDENT_ID}},{Key=Purpose,Value=forensic-evidence}]\" \\\n    --query 'SnapshotId' --output text)\n  echo \"  Snapshot created: $SNAP_ID for volume $vol\"\ndone\n\n# Capture instance metadata\necho \"Capturing instance metadata...\"\naws ec2 describe-instances --instance-ids \"$INSTANCE_ID\" \\\n  > \"\u002Ftmp\u002F${INCIDENT_ID}-instance-describe.json\"\naws s3 cp \"\u002Ftmp\u002F${INCIDENT_ID}-instance-describe.json\" \\\n  \"${EVIDENCE_BUCKET}\u002F${EVIDENCE_PREFIX}\u002Finstance-describe.json\"\n\n# Capture security group rules\nSG_IDS=$(aws ec2 describe-instances --instance-ids \"$INSTANCE_ID\" \\\n  --query 'Reservations[].Instances[].SecurityGroups[].GroupId' --output text)\nfor sg in $SG_IDS; do\n  aws ec2 describe-security-group-rules --filters \"Name=group-id,Values=${sg}\" \\\n    > \"\u002Ftmp\u002F${INCIDENT_ID}-sg-${sg}.json\"\n  aws s3 cp \"\u002Ftmp\u002F${INCIDENT_ID}-sg-${sg}.json\" \\\n    \"${EVIDENCE_BUCKET}\u002F${EVIDENCE_PREFIX}\u002Fsg-${sg}.json\"\ndone\n\n# Collect CloudTrail events for the instance\necho \"Collecting CloudTrail events...\"\naws cloudtrail lookup-events \\\n  --lookup-attributes \"AttributeKey=ResourceName,AttributeValue=${INSTANCE_ID}\" \\\n  --start-time \"$(date -d '7 days ago' -u +%Y-%m-%dT%H:%M:%SZ)\" \\\n  > \"\u002Ftmp\u002F${INCIDENT_ID}-cloudtrail.json\"\naws s3 cp \"\u002Ftmp\u002F${INCIDENT_ID}-cloudtrail.json\" \\\n  \"${EVIDENCE_BUCKET}\u002F${EVIDENCE_PREFIX}\u002Fcloudtrail.json\"\n\n# Collect VPC flow logs\necho \"Collecting VPC flow logs...\"\nENI_ID=$(aws ec2 describe-instances --instance-ids \"$INSTANCE_ID\" \\\n  --query 'Reservations[].Instances[].NetworkInterfaces[0].NetworkInterfaceId' --output text)\naws ec2 describe-flow-logs --filter \"Name=resource-id,Values=${ENI_ID}\" \\\n  > \"\u002Ftmp\u002F${INCIDENT_ID}-flow-logs.json\"\naws s3 cp \"\u002Ftmp\u002F${INCIDENT_ID}-flow-logs.json\" \\\n  \"${EVIDENCE_BUCKET}\u002F${EVIDENCE_PREFIX}\u002Fflow-logs-config.json\"\n\n# Isolate the instance (move to quarantine security group)\necho \"Isolating instance...\"\nQUARANTINE_SG=$(aws ec2 create-security-group \\\n  --group-name \"quarantine-${INCIDENT_ID}\" \\\n  --description \"Quarantine SG for incident ${INCIDENT_ID}\" \\\n  --vpc-id \"$(aws ec2 describe-instances --instance-ids \"$INSTANCE_ID\" \\\n    --query 'Reservations[].Instances[].VpcId' --output text)\" \\\n  --query 'GroupId' --output text)\n\n# Quarantine SG: deny all inbound, allow outbound only to evidence bucket\naws ec2 modify-instance-attribute \\\n  --instance-id \"$INSTANCE_ID\" \\\n  --groups \"$QUARANTINE_SG\"\n\necho \"Instance isolated with quarantine SG: $QUARANTINE_SG\"\necho \"Evidence stored at: ${EVIDENCE_BUCKET}\u002F${EVIDENCE_PREFIX}\u002F\"\n```\n\n## Forensics Commands Reference\n\n```bash\n# --- Disk forensics ---\n# Create forensic image of a disk\ndd if=\u002Fdev\u002Fsda of=\u002Fevidence\u002Fdisk.img bs=4M status=progress\nsha256sum \u002Fevidence\u002Fdisk.img > \u002Fevidence\u002Fdisk.img.sha256\n\n# Mount forensic image read-only\nmount -o ro,loop,noexec \u002Fevidence\u002Fdisk.img \u002Fmnt\u002Fforensic\n\n# Find recently modified files\nfind \u002Fmnt\u002Fforensic -type f -mtime -3 -ls | sort -k11\n\n# Find files by owner\nfind \u002Fmnt\u002Fforensic -user www-data -type f -newer \u002Ftmp\u002Freference-time -ls\n\n# --- Log analysis ---\n# Search auth logs for brute force\ngrep \"Failed password\" \u002Fvar\u002Flog\u002Fauth.log | awk '{print $11}' | sort | uniq -c | sort -rn | head -20\n\n# Search for privilege escalation\ngrep -E \"(sudo|su\\[)\" \u002Fvar\u002Flog\u002Fauth.log | grep -v \"session opened\"\n\n# Search web logs for attack patterns\ngrep -iE \"(union.*select|\u003Cscript|\\.\\.\\\u002F|%00)\" \u002Fvar\u002Flog\u002Fnginx\u002Faccess.log\n\n# Timeline analysis with find\nfind \u002F -newermt \"2025-01-15 00:00\" ! -newermt \"2025-01-16 00:00\" -ls 2>\u002Fdev\u002Fnull | sort -k9\n\n# --- Network forensics ---\n# Capture network traffic\ntcpdump -i eth0 -w \u002Fevidence\u002Fcapture.pcap -c 100000\n\n# Analyze pcap for suspicious connections\ntcpdump -r \u002Fevidence\u002Fcapture.pcap -nn 'dst port 4444 or dst port 8888 or dst port 1337'\n\n# Check for DNS tunneling\ntcpdump -r \u002Fevidence\u002Fcapture.pcap -nn 'udp port 53' | awk '{print $NF}' | sort | uniq -c | sort -rn | head -20\n\n# --- Malware analysis ---\n# Check file for known malware hashes\nsha256sum suspicious_file\n# Compare against VirusTotal: https:\u002F\u002Fwww.virustotal.com\n\n# Strings analysis\nstrings suspicious_file | grep -iE \"(http|ftp|ssh|password|key|token)\"\n\n# Check for packed\u002Fobfuscated binaries\nfile suspicious_file\nreadelf -h suspicious_file 2>\u002Fdev\u002Fnull\n```\n\n## Communication Templates\n\n### Initial Notification (Internal)\n\n```markdown\n## Security Incident Notification\n\n**Incident ID:** INC-YYYY-NNNN\n**Severity:** [Critical\u002FHigh\u002FMedium\u002FLow]\n**Status:** Active - Investigating\n**Time Detected:** YYYY-MM-DD HH:MM UTC\n**Reported By:** [Name\u002FSystem]\n\n### Summary\n[1-2 sentence description of what was detected]\n\n### Impact Assessment\n- **Systems affected:** [list]\n- **Data at risk:** [type and scope]\n- **Users impacted:** [count\u002Fscope]\n- **Business impact:** [description]\n\n### Current Actions\n- [ ] Evidence preservation in progress\n- [ ] Containment measures being applied\n- [ ] IR team assembled\n\n### Next Update\nExpected at: YYYY-MM-DD HH:MM UTC\n\n### Incident Commander\n[Name] - [Contact info]\n```\n\n### Stakeholder Update\n\n```markdown\n## Incident Update - INC-YYYY-NNNN\n\n**Update #:** N\n**Time:** YYYY-MM-DD HH:MM UTC\n**Severity:** [unchanged\u002Fupgraded\u002Fdowngraded]\n**Status:** [Investigating\u002FContained\u002FEradicating\u002FRecovering\u002FResolved]\n\n### Progress Since Last Update\n- [Bullet points of actions taken]\n\n### Current Understanding\n- **Root cause:** [Known\u002FUnder investigation]\n- **Scope:** [Expanded\u002FUnchanged\u002FReduced]\n- **Threat actor:** [If applicable]\n\n### Active Containment Measures\n- [List of measures in place]\n\n### Next Steps\n- [Planned actions with ETA]\n\n### Decisions Needed\n- [If any decisions required from leadership]\n```\n\n### External Breach Notification (if required)\n\n```markdown\n\n## Contents\n\n- [Notice of Data Security Incident](references\u002Fdetails.md)\n- [IR Playbook: Compromised Credentials](references\u002Fdetails.md)\n- [Troubleshooting](references\u002Fdetails.md)\n- [Best Practices](references\u002Fdetails.md)\n- [Related Skills](references\u002Fdetails.md)\n\n## When to Use This Skill\n\nUse this skill when:\n- Responding to an active security incident (breach, malware, unauthorized access)\n- Building incident response playbooks and runbooks\n- Conducting IR tabletop exercises and drills\n- Setting up evidence collection and forensic capabilities\n- Establishing communication protocols for security events\n- Performing post-incident reviews and process improvements\n\n## Limitations\n\n- Apply guidance only within authorized scope; test destructive steps in non-production first.\n- Docs-only import: upstream scripts and templates not bundled.\n\n### Example\n\n```bash\n# Read-only first: inventory before any active step.\nwhich \u003Ctool> && \u003Ctool> --help | head -n 20\n```\n\n> Adapted from [BagelHole\u002FDevOps-Security-Agent-Skills](https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: helper scripts and templates not bundled.\n","# Incident Response\n\nHandle security incidents effectively with structured response procedures.\n\n## Prerequisites\n\n- IR team roster with on-call rotation and escalation paths\n- Secure communication channel (separate from production systems)\n- Forensic workstation with analysis tools installed\n- Evidence storage with chain-of-custody controls\n- Legal counsel contact information\n- Pre-authorized incident response actions documented\n\n## Incident Response Phases\n\n```yaml\nphases:\n  1_preparation:\n    - IR team roster and 24\u002F7 contact info\n    - Tools and privileged access ready\n    - Playbooks documented and tested\n    - Evidence collection kit prepared\n    - Communication templates drafted\n\n  2_detection:\n    - Alert triage and validation\n    - Initial assessment and scoping\n    - Severity classification\n    - Incident ticket creation\n\n  3_containment:\n    - Short-term containment (stop bleeding)\n    - Evidence preservation (before changes)\n    - System isolation (network\u002Fhost level)\n    - Credential rotation if needed\n\n  4_eradication:\n    - Root cause analysis\n    - Remove threat actor access\n    - Patch exploited vulnerabilities\n    - Clean compromised systems\n\n  5_recovery:\n    - System restoration from clean backups\n    - Enhanced monitoring deployment\n    - Phased return to production\n    - Business continuity verification\n\n  6_lessons_learned:\n    - Post-incident review (within 72 hours)\n    - Timeline reconstruction\n    - Documentation update\n    - Process and detection improvements\n```\n\n## Severity Classification\n\n| Level | Impact | Response Time | Examples |\n|-------|--------|---------------|----------|\n| Critical (P1) | Active data breach, full outage, ransomware | Immediate (\u003C 15 min) | Data exfiltration in progress, ransomware spreading |\n| High (P2) | Service degraded, potential breach | \u003C 1 hour | Unauthorized admin access, malware detected |\n| Medium (P3) | Limited impact, contained | \u003C 4 hours | Phishing compromise (single user), policy violation |\n| Low (P4) | Minimal impact | Next business day | Failed brute force, blocked scanning activity |\n\n## Evidence Collection Scripts\n\n### Linux Evidence Collection\n\n```bash\n#!\u002Fbin\u002Fbash\n# linux-evidence-collect.sh - Collect forensic evidence from a Linux host\n# Run with sudo. Preserves evidence with timestamps and hashes.\n\nset -euo pipefail\n\nEVIDENCE_DIR=\"\u002Fevidence\u002F$(hostname)-$(date +%Y%m%d-%H%M%S)\"\nmkdir -p \"$EVIDENCE_DIR\"\nLOGFILE=\"$EVIDENCE_DIR\u002Fcollection.log\"\n\nlog() { echo \"[$(date -u +%Y-%m-%dT%H:%M:%SZ)] $*\" | tee -a \"$LOGFILE\"; }\n\nlog \"Starting evidence collection on $(hostname)\"\nlog \"Collector: $(whoami)\"\nlog \"System time: $(date -u)\"\n\n# System information\nlog \"Collecting system information...\"\nuname -a > \"$EVIDENCE_DIR\u002Funame.txt\"\ncat \u002Fetc\u002Fos-release > \"$EVIDENCE_DIR\u002Fos-release.txt\"\nuptime > \"$EVIDENCE_DIR\u002Fuptime.txt\"\ndate -u > \"$EVIDENCE_DIR\u002Fsystem-time.txt\"\n\n# Running processes (full command line)\nlog \"Collecting process list...\"\nps auxwwf > \"$EVIDENCE_DIR\u002Fprocesses.txt\"\nps -eo pid,ppid,user,args --sort=-pcpu > \"$EVIDENCE_DIR\u002Fprocesses-by-cpu.txt\"\n\n# Network connections\nlog \"Collecting network state...\"\nss -tulnp > \"$EVIDENCE_DIR\u002Flistening-ports.txt\"\nss -anp > \"$EVIDENCE_DIR\u002Fall-connections.txt\"\nip addr show > \"$EVIDENCE_DIR\u002Fip-addresses.txt\"\nip route show > \"$EVIDENCE_DIR\u002Froutes.txt\"\niptables -L -n -v > \"$EVIDENCE_DIR\u002Fiptables.txt\" 2>&1 || true\ncat \u002Fetc\u002Fresolv.conf > \"$EVIDENCE_DIR\u002Fdns-config.txt\"\n\n# User activity\nlog \"Collecting user activity...\"\nlast -a > \"$EVIDENCE_DIR\u002Flogin-history.txt\"\nlastb > \"$EVIDENCE_DIR\u002Ffailed-logins.txt\" 2>&1 || true\nwho > \"$EVIDENCE_DIR\u002Fcurrently-logged-in.txt\"\nw > \"$EVIDENCE_DIR\u002Fuser-activity.txt\"\ncat \u002Fetc\u002Fpasswd > \"$EVIDENCE_DIR\u002Fpasswd.txt\"\ncat \u002Fetc\u002Fshadow > \"$EVIDENCE_DIR\u002Fshadow.txt\" 2>\u002Fdev\u002Fnull || true\ncat \u002Fetc\u002Fgroup > \"$EVIDENCE_DIR\u002Fgroup.txt\"\n\n# Scheduled tasks\nlog \"Collecting scheduled tasks...\"\nfor user in $(cut -f1 -d: \u002Fetc\u002Fpasswd); do\n  crontab -u \"$user\" -l 2>\u002Fdev\u002Fnull >> \"$EVIDENCE_DIR\u002Fcrontabs.txt\" && \\\n    echo \"--- $user ---\" >> \"$EVIDENCE_DIR\u002Fcrontabs.txt\"\ndone\nls -la \u002Fetc\u002Fcron.* > \"$EVIDENCE_DIR\u002Fcron-dirs.txt\" 2>&1\n\n# File system state\nlog \"Collecting filesystem state...\"\nfind \u002Ftmp \u002Fvar\u002Ftmp \u002Fdev\u002Fshm -type f -ls > \"$EVIDENCE_DIR\u002Ftemp-files.txt\" 2>\u002Fdev\u002Fnull\nfind \u002F -name \"*.sh\" -mtime -7 -ls > \"$EVIDENCE_DIR\u002Frecent-scripts.txt\" 2>\u002Fdev\u002Fnull\nfind \u002F -perm -4000 -type f -ls > \"$EVIDENCE_DIR\u002Fsuid-files.txt\" 2>\u002Fdev\u002Fnull\nfind \u002Fhome -name \".*history\" -ls > \"$EVIDENCE_DIR\u002Fhistory-files.txt\" 2>\u002Fdev\u002Fnull\n\n# Loaded kernel modules\nlog \"Collecting kernel modules...\"\nlsmod > \"$EVIDENCE_DIR\u002Fkernel-modules.txt\"\n\n# Open files\nlog \"Collecting open files...\"\nlsof -n > \"$EVIDENCE_DIR\u002Fopen-files.txt\" 2>\u002Fdev\u002Fnull\n\n# Systemd services\nlog \"Collecting service state...\"\nsystemctl list-units --type=service --all > \"$EVIDENCE_DIR\u002Fservices.txt\"\nsystemctl list-timers --all > \"$EVIDENCE_DIR\u002Ftimers.txt\"\n\n# Log preservation\nlog \"Preserving system logs...\"\ntar czf \"$EVIDENCE_DIR\u002Fvar-log.tar.gz\" \u002Fvar\u002Flog\u002F 2>\u002Fdev\u002Fnull\n\n# Docker containers (if present)\nif command -v docker &>\u002Fdev\u002Fnull; then\n  log \"Collecting Docker state...\"\n  docker ps -a > \"$EVIDENCE_DIR\u002Fdocker-containers.txt\"\n  docker images > \"$EVIDENCE_DIR\u002Fdocker-images.txt\"\n  docker network ls > \"$EVIDENCE_DIR\u002Fdocker-networks.txt\"\nfi\n\n# Kubernetes (if kubectl available)\nif command -v kubectl &>\u002Fdev\u002Fnull; then\n  log \"Collecting Kubernetes state...\"\n  kubectl get pods --all-namespaces > \"$EVIDENCE_DIR\u002Fk8s-pods.txt\" 2>\u002Fdev\u002Fnull\n  kubectl get events --all-namespaces --sort-by=.lastTimestamp > \"$EVIDENCE_DIR\u002Fk8s-events.txt\" 2>\u002Fdev\u002Fnull\nfi\n\n# Hash all evidence files\nlog \"Computing evidence hashes...\"\nfind \"$EVIDENCE_DIR\" -type f ! -name \"checksums.sha256\" -exec sha256sum {} \\; > \"$EVIDENCE_DIR\u002Fchecksums.sha256\"\n\nlog \"Evidence collection complete: $EVIDENCE_DIR\"\necho \"Total files collected: $(find \"$EVIDENCE_DIR\" -type f | wc -l)\"\n```\n\n### Memory Acquisition\n\n```bash\n#!\u002Fbin\u002Fbash\n# memory-capture.sh - Capture volatile memory for forensic analysis\n\nEVIDENCE_DIR=\"\u002Fevidence\u002Fmemory-$(hostname)-$(date +%Y%m%d-%H%M%S)\"\nmkdir -p \"$EVIDENCE_DIR\"\n\n# Using LiME (Linux Memory Extractor)\nif [ -f \u002Flib\u002Fmodules\u002F$(uname -r)\u002Fextra\u002Flime.ko ]; then\n  insmod \u002Flib\u002Fmodules\u002F$(uname -r)\u002Fextra\u002Flime.ko \"path=$EVIDENCE_DIR\u002Fmemory.lime format=lime\"\n  echo \"Memory captured with LiME\"\nfi\n\n# Alternative: \u002Fproc\u002Fkcore (partial, but always available)\ncp \u002Fproc\u002Fkcore \"$EVIDENCE_DIR\u002Fkcore\" 2>\u002Fdev\u002Fnull\n\n# Capture \u002Fproc\u002Fmeminfo for context\ncat \u002Fproc\u002Fmeminfo > \"$EVIDENCE_DIR\u002Fmeminfo.txt\"\n\n# Hash the memory dump\nsha256sum \"$EVIDENCE_DIR\"\u002F* > \"$EVIDENCE_DIR\u002Fchecksums.sha256\"\n```\n\n### AWS Evidence Collection\n\n```bash\n#!\u002Fbin\u002Fbash\n# aws-evidence-collect.sh - Collect evidence from compromised AWS resources\n\nINCIDENT_ID=\"${1:?Usage: $0 \u003Cincident-id>}\"\nINSTANCE_ID=\"${2:?Usage: $0 \u003Cincident-id> \u003Cinstance-id>}\"\nEVIDENCE_BUCKET=\"s3:\u002F\u002Fincident-evidence-${AWS_ACCOUNT_ID}\"\nEVIDENCE_PREFIX=\"${INCIDENT_ID}\u002F$(date +%Y%m%d-%H%M%S)\"\n\necho \"=== AWS Evidence Collection ===\"\necho \"Incident: $INCIDENT_ID\"\necho \"Instance: $INSTANCE_ID\"\n\n# Snapshot EBS volumes\necho \"Creating EBS snapshots...\"\nVOLUMES=$(aws ec2 describe-volumes \\\n  --filters \"Name=attachment.instance-id,Values=${INSTANCE_ID}\" \\\n  --query 'Volumes[].VolumeId' --output text)\n\nfor vol in $VOLUMES; do\n  SNAP_ID=$(aws ec2 create-snapshot \\\n    --volume-id \"$vol\" \\\n    --description \"IR Evidence - ${INCIDENT_ID} - ${vol}\" \\\n    --tag-specifications \"ResourceType=snapshot,Tags=[{Key=IncidentId,Value=${INCIDENT_ID}},{Key=Purpose,Value=forensic-evidence}]\" \\\n    --query 'SnapshotId' --output text)\n  echo \"  Snapshot created: $SNAP_ID for volume $vol\"\ndone\n\n# Capture instance metadata\necho \"Capturing instance metadata...\"\naws ec2 describe-instances --instance-ids \"$INSTANCE_ID\" \\\n  > \"\u002Ftmp\u002F${INCIDENT_ID}-instance-describe.json\"\naws s3 cp \"\u002Ftmp\u002F${INCIDENT_ID}-instance-describe.json\" \\\n  \"${EVIDENCE_BUCKET}\u002F${EVIDENCE_PREFIX}\u002Finstance-describe.json\"\n\n# Capture security group rules\nSG_IDS=$(aws ec2 describe-instances --instance-ids \"$INSTANCE_ID\" \\\n  --query 'Reservations[].Instances[].SecurityGroups[].GroupId' --output text)\nfor sg in $SG_IDS; do\n  aws ec2 describe-security-group-rules --filters \"Name=group-id,Values=${sg}\" \\\n    > \"\u002Ftmp\u002F${INCIDENT_ID}-sg-${sg}.json\"\n  aws s3 cp \"\u002Ftmp\u002F${INCIDENT_ID}-sg-${sg}.json\" \\\n    \"${EVIDENCE_BUCKET}\u002F${EVIDENCE_PREFIX}\u002Fsg-${sg}.json\"\ndone\n\n# Collect CloudTrail events for the instance\necho \"Collecting CloudTrail events...\"\naws cloudtrail lookup-events \\\n  --lookup-attributes \"AttributeKey=ResourceName,AttributeValue=${INSTANCE_ID}\" \\\n  --start-time \"$(date -d '7 days ago' -u +%Y-%m-%dT%H:%M:%SZ)\" \\\n  > \"\u002Ftmp\u002F${INCIDENT_ID}-cloudtrail.json\"\naws s3 cp \"\u002Ftmp\u002F${INCIDENT_ID}-cloudtrail.json\" \\\n  \"${EVIDENCE_BUCKET}\u002F${EVIDENCE_PREFIX}\u002Fcloudtrail.json\"\n\n# Collect VPC flow logs\necho \"Collecting VPC flow logs...\"\nENI_ID=$(aws ec2 describe-instances --instance-ids \"$INSTANCE_ID\" \\\n  --query 'Reservations[].Instances[].NetworkInterfaces[0].NetworkInterfaceId' --output text)\naws ec2 describe-flow-logs --filter \"Name=resource-id,Values=${ENI_ID}\" \\\n  > \"\u002Ftmp\u002F${INCIDENT_ID}-flow-logs.json\"\naws s3 cp \"\u002Ftmp\u002F${INCIDENT_ID}-flow-logs.json\" \\\n  \"${EVIDENCE_BUCKET}\u002F${EVIDENCE_PREFIX}\u002Fflow-logs-config.json\"\n\n# Isolate the instance (move to quarantine security group)\necho \"Isolating instance...\"\nQUARANTINE_SG=$(aws ec2 create-security-group \\\n  --group-name \"quarantine-${INCIDENT_ID}\" \\\n  --description \"Quarantine SG for incident ${INCIDENT_ID}\" \\\n  --vpc-id \"$(aws ec2 describe-instances --instance-ids \"$INSTANCE_ID\" \\\n    --query 'Reservations[].Instances[].VpcId' --output text)\" \\\n  --query 'GroupId' --output text)\n\n# Quarantine SG: deny all inbound, allow outbound only to evidence bucket\naws ec2 modify-instance-attribute \\\n  --instance-id \"$INSTANCE_ID\" \\\n  --groups \"$QUARANTINE_SG\"\n\necho \"Instance isolated with quarantine SG: $QUARANTINE_SG\"\necho \"Evidence stored at: ${EVIDENCE_BUCKET}\u002F${EVIDENCE_PREFIX}\u002F\"\n```\n\n## Forensics Commands Reference\n\n```bash\n# --- Disk forensics ---\n# Create forensic image of a disk\ndd if=\u002Fdev\u002Fsda of=\u002Fevidence\u002Fdisk.img bs=4M status=progress\nsha256sum \u002Fevidence\u002Fdisk.img > \u002Fevidence\u002Fdisk.img.sha256\n\n# Mount forensic image read-only\nmount -o ro,loop,noexec \u002Fevidence\u002Fdisk.img \u002Fmnt\u002Fforensic\n\n# Find recently modified files\nfind \u002Fmnt\u002Fforensic -type f -mtime -3 -ls | sort -k11\n\n# Find files by owner\nfind \u002Fmnt\u002Fforensic -user www-data -type f -newer \u002Ftmp\u002Freference-time -ls\n\n# --- Log analysis ---\n# Search auth logs for brute force\ngrep \"Failed password\" \u002Fvar\u002Flog\u002Fauth.log | awk '{print $11}' | sort | uniq -c | sort -rn | head -20\n\n# Search for privilege escalation\ngrep -E \"(sudo|su\\[)\" \u002Fvar\u002Flog\u002Fauth.log | grep -v \"session opened\"\n\n# Search web logs for attack patterns\ngrep -iE \"(union.*select|\u003Cscript|\\.\\.\\\u002F|%00)\" \u002Fvar\u002Flog\u002Fnginx\u002Faccess.log\n\n# Timeline analysis with find\nfind \u002F -newermt \"2025-01-15 00:00\" ! -newermt \"2025-01-16 00:00\" -ls 2>\u002Fdev\u002Fnull | sort -k9\n\n# --- Network forensics ---\n# Capture network traffic\ntcpdump -i eth0 -w \u002Fevidence\u002Fcapture.pcap -c 100000\n\n# Analyze pcap for suspicious connections\ntcpdump -r \u002Fevidence\u002Fcapture.pcap -nn 'dst port 4444 or dst port 8888 or dst port 1337'\n\n# Check for DNS tunneling\ntcpdump -r \u002Fevidence\u002Fcapture.pcap -nn 'udp port 53' | awk '{print $NF}' | sort | uniq -c | sort -rn | head -20\n\n# --- Malware analysis ---\n# Check file for known malware hashes\nsha256sum suspicious_file\n# Compare against VirusTotal: https:\u002F\u002Fwww.virustotal.com\n\n# Strings analysis\nstrings suspicious_file | grep -iE \"(http|ftp|ssh|password|key|token)\"\n\n# Check for packed\u002Fobfuscated binaries\nfile suspicious_file\nreadelf -h suspicious_file 2>\u002Fdev\u002Fnull\n```\n\n## Communication Templates\n\n### Initial Notification (Internal)\n\n```markdown\n## Security Incident Notification\n\n**Incident ID:** INC-YYYY-NNNN\n**Severity:** [Critical\u002FHigh\u002FMedium\u002FLow]\n**Status:** Active - Investigating\n**Time Detected:** YYYY-MM-DD HH:MM UTC\n**Reported By:** [Name\u002FSystem]\n\n### Summary\n[1-2 sentence description of what was detected]\n\n### Impact Assessment\n- **Systems affected:** [list]\n- **Data at risk:** [type and scope]\n- **Users impacted:** [count\u002Fscope]\n- **Business impact:** [description]\n\n### Current Actions\n- [ ] Evidence preservation in progress\n- [ ] Containment measures being applied\n- [ ] IR team assembled\n\n### Next Update\nExpected at: YYYY-MM-DD HH:MM UTC\n\n### Incident Commander\n[Name] - [Contact info]\n```\n\n### Stakeholder Update\n\n```markdown\n## Incident Update - INC-YYYY-NNNN\n\n**Update #:** N\n**Time:** YYYY-MM-DD HH:MM UTC\n**Severity:** [unchanged\u002Fupgraded\u002Fdowngraded]\n**Status:** [Investigating\u002FContained\u002FEradicating\u002FRecovering\u002FResolved]\n\n### Progress Since Last Update\n- [Bullet points of actions taken]\n\n### Current Understanding\n- **Root cause:** [Known\u002FUnder investigation]\n- **Scope:** [Expanded\u002FUnchanged\u002FReduced]\n- **Threat actor:** [If applicable]\n\n### Active Containment Measures\n- [List of measures in place]\n\n### Next Steps\n- [Planned actions with ETA]\n\n### Decisions Needed\n- [If any decisions required from leadership]\n```\n\n### External Breach Notification (if required)\n\n```markdown\n\n## Contents\n\n- [Notice of Data Security Incident](references\u002Fdetails.md)\n- [IR Playbook: Compromised Credentials](references\u002Fdetails.md)\n- [Troubleshooting](references\u002Fdetails.md)\n- [Best Practices](references\u002Fdetails.md)\n- [Related Skills](references\u002Fdetails.md)\n\n## When to Use This Skill\n\nUse this skill when:\n- Responding to an active security incident (breach, malware, unauthorized access)\n- Building incident response playbooks and runbooks\n- Conducting IR tabletop exercises and drills\n- Setting up evidence collection and forensic capabilities\n- Establishing communication protocols for security events\n- Performing post-incident reviews and process improvements\n\n## Limitations\n\n- Apply guidance only within authorized scope; test destructive steps in non-production first.\n- Docs-only import: upstream scripts and templates not bundled.\n\n### Example\n\n```bash\n# Read-only first: inventory before any active step.\nwhich \u003Ctool> && \u003Ctool> --help | head -n 20\n```\n\n> Adapted from [BagelHole\u002FDevOps-Security-Agent-Skills](https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: helper scripts and templates not bundled.\n",{"name":5,"risk":27,"source":43,"license":14,"category":44,"metadata":45,"date_added":48,"description":7,"source_repo":49,"source_type":30,"compatibility":50,"license_source":51},"https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills","security",{"author":46,"version":47},"devops-skills","1.0","2026-09-20","BagelHole\u002FDevOps-Security-Agent-Skills","Requires the relevant security tooling (scanners, vault CLIs) and an authorized scope for any active assessment. Docs-only; helper scripts and templates not bundled.","https:\u002F\u002Fgithub.com\u002FBagelHole\u002FDevOps-Security-Agent-Skills\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fincident-response","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill incident-response",{"tool":63,"command":64},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill incident-response",{"tool":66,"command":67},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill incident-response","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fincident-response\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fdetails.md","REFERENCE","参考文档",4410,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fincident-response\u002Freferences\u002Fdetails.md",[78,100,124,147,175,199],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":89,"publishedAt":38},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[90,91,92,93,37,94,80,95,35,96,97,32,30,29,28,27,26,98,24,99],"ZeRO","trust","zero trust","architecture","verification","segmentation","access","configure","scripts","implementing",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":38},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[107,108,109,110,111,112,113,114,115,116,117,118,119,32,120,30,121,122,27,123],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":38},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[131,132,133,134,21,135,136,36,137,138,139,140,141,30,29,142,143,144,145,146],"transcript","youtube transcript","youtube","safe","codex","research","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":164,"publishedAt":38},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[153,156,159],{"categoryNo":154,"categoryName":155,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":157,"categoryName":158,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":160,"categoryName":161,"taxonomyType":162,"taxonomyTypeDesc":163},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[131,132,133,165,134,166,21,135,36,167,168,169,170,139,171,30,29,172,173,174],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":185,"publishedAt":38},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[181,184],{"categoryNo":182,"categoryName":183,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":157,"categoryName":158,"taxonomyType":87,"taxonomyTypeDesc":88},[133,186,187,111,134,188,189,190,191,36,169,192,193,194,195,29,196,142,197,198],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":38},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[205],{"categoryNo":154,"categoryName":155,"taxonomyType":87,"taxonomyTypeDesc":88},[207,133,208,209,134,166,167,210,211,168,169,170,139,212,171,30,29,172,213,145],"youtube full","full","google","server","dlp","credits","automatic"]