[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMX2R7PQ13CFVTZYPPXV3M":3,"skill-same:01M7EMX2R7PQ13CFVTZYPPXV3M":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMX2R7PQ13CFVTZYPPXV3M","edr-pro",null,"Deploy and operate endpoint detection and response — policy tuning, behavioral detections, threat hunting, and response actions.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-edr-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: edr-pro\ndescription: Deploy and operate endpoint detection and response — policy tuning, behavioral detections, threat hunting, and response actions.\ncategory: security\n---\n\n## Overview\n\nEDR is the defender's eyes on the endpoint: it records process, file, registry, and network activity, detects malicious behavior, and enables remote response (isolate, kill, remediate). It is arguably the highest-value single security control for most organizations — and also one of the most misconfigured, oscillating between alert floods and silent monitor-mode deployments.\n\nThis skill covers the full EDR practice: deployment, policy design, detection tuning, threat hunting on EDR telemetry, and safe response operations.\n\nDeploy for coverage first, then tune for precision: get the agent everywhere (including servers, not just laptops), confirm telemetry is flowing, and only then start shaping policies and detections. An EDR covering 60% of endpoints with perfect tuning protects less than one covering 98% with acceptable noise.\n\n## When to use\n\n- Rolling out EDR to endpoints and servers for the first time.\n- Tuning noisy policies or investigating EDR-caused performance issues.\n- Building behavioral detections for your threat model.\n- Running threat hunts across endpoint telemetry.\n- Defining response playbooks (isolate, contain, remediate) with approval gates.\n\n## Core concepts\n\n- **Coverage is the metric that matters most.** Unprotected endpoints are invisible endpoints. Track deployment % by asset class relentlessly — servers and OT-adjacent systems included.\n- **Prevention vs detection modes.** Modern EDR does both: block known-malicious behaviors automatically, detect-and-alert on suspicious ones. Progressively enable blocking on high-confidence behaviors; keep detection on the ambiguous.\n- **Behavioral detections beat IOCs.** Detect techniques (credential dumping, LSASS access, suspicious parent-child process chains) mapped to ATT&CK — they survive attacker infrastructure changes.\n- **Policy layering.** Baseline policies for all endpoints, stricter for servers and high-risk groups, monitor-only for fragile\u002Flegacy systems with compensating controls. One global policy fits nobody.\n- **Telemetry retention.** EDR telemetry is your best hunting and investigation dataset — retain as long as budget allows (90+ days ideal), and know exactly what you keep.\n- **Response actions with gates.** Network isolation, process kill, and file quarantine are powerful — define who may trigger them, require approval for broad actions, and log everything.\n- **Tamper protection.** Attackers kill EDR first. Enforce tamper protection, alert on agent uninstall\u002Fdisable attempts, and monitor agent health as a security signal.\n- **Performance partnership.** EDR scans cost CPU\u002FIO — work with IT on exclusions for legitimate heavy workloads (build servers, databases) via documented, reviewed exception processes, not ad-hoc disabling.\n- **Threat hunting.** Proactive hypothesis-driven searches across EDR telemetry (\"show me all LSASS access outside expected processes\") catch what automated detections miss.\n- **Integration.** EDR alerts feed the SIEM\u002FSOC with process-tree context; EDR telemetry enriches firewall and identity investigations. An isolated EDR console is half the value.\n\n- **Cloud workload coverage.** Containers and serverless need their own sensor strategy — classic host agents do not cover ephemeral workloads. Plan EDR\u002FCWPP coverage per workload type.\n- **Offline and air-gapped endpoints.** Devices off-network for weeks miss policy updates and detections. Define maximum offline tolerance and catch-up procedures.\n\n## Practical workflow\n\n1. **Deploy for coverage:** phased rollout (IT pilot → general population → servers → tricky segments), tracking install % daily. Resolve the long tail — the last 5% takes 50% of the effort and is often the riskiest.\n2. **Verify telemetry:** confirm events flowing per endpoint, check for blind spots (agent version skew, policy gaps, offline systems), and alert on agent health failures.\n3. **Tune policies:** start from vendor recommended baselines, adjust for your environment, document every exclusion with justification and review date. Re-tune quarterly.\n4. **Build behavioral detections:** map your top ATT&CK techniques to EDR detection rules; test against benign baselines; deploy with runbooks linked.\n5. **Hunt regularly:** weekly hypothesis-driven hunts using threat intel and red-team TTPs; convert hunt findings into permanent detections.\n6. **Operate response:** playbooks for isolate\u002Fkill\u002Fquarantine with approval gates; post-action verification (re-scan, monitor for re-infection); lessons fed back into detections and policy.\n\n### Quick wins\n\n- Enable tamper protection everywhere this week — it is the cheapest high-value control\n- Audit agent coverage by asset class; close the server gap first\n- Review and justify every policy exclusion older than 90 days\n\n### Sustaining the practice\n\n- Review policy exclusions quarterly — each needs re-justification or removal\n- Re-run coverage audits monthly; new systems must get agents at provisioning\n- Hunt cadence: at least weekly, tied to current threat intel\n- Test tamper-protection and agent-health alerting with simulated disable attempts\n\n### Metrics that prove it works\n\n- Agent coverage % by asset class (target: 98%+)\n- Mean time to detect and to contain on endpoint incidents\n- False-positive rate per policy\u002Fdetection; analyst action rate\n- Threat-hunt findings converted to detections per quarter\n\n## Common pitfalls\n\n- **Monitor-only forever.** Detection without blocking on high-confidence behaviors leaves dwell time on the table. Progressively enable prevention.\n- **Coverage theater.** \"Deployed\" with 70% coverage and no plan for the rest. The uncovered 30% is where attackers live.\n- **Exclusion sprawl.** Every performance complaint becomes a permanent exclusion. Review exclusions quarterly with security+IT jointly.\n- **Killing the agent to 'fix' performance.** Disabling EDR for speed is a security incident, not a fix. Tune, exclude narrowly, or upgrade hardware.\n- **No tamper protection.** Attackers' first move is blinding the sensor. Enforce it and alert on tampering attempts.\n- **Alert-only hunting.** EDR telemetry unused for proactive hunting wastes its best capability. Schedule hunts like any other security operation.\n- **Forgetting servers.** Laptop-focused rollouts leave the crown-jewel servers unprotected. Servers get agents with server-tuned policies.\n- **Response without verification.** Isolating a host and calling it done misses persistence and lateral movement. Verify with re-scan and monitoring.\n- **Treating EDR as antivirus replacement only.** Its investigation and hunting value dwarfs the blocking value — train analysts on the telemetry, not just the alerts.\n- **No offline-device strategy.** Laptops off VPN for a month return with stale policies and missed detections. Enforce check-in requirements.\n","## Overview\n\nEDR is the defender's eyes on the endpoint: it records process, file, registry, and network activity, detects malicious behavior, and enables remote response (isolate, kill, remediate). It is arguably the highest-value single security control for most organizations — and also one of the most misconfigured, oscillating between alert floods and silent monitor-mode deployments.\n\nThis skill covers the full EDR practice: deployment, policy design, detection tuning, threat hunting on EDR telemetry, and safe response operations.\n\nDeploy for coverage first, then tune for precision: get the agent everywhere (including servers, not just laptops), confirm telemetry is flowing, and only then start shaping policies and detections. An EDR covering 60% of endpoints with perfect tuning protects less than one covering 98% with acceptable noise.\n\n## When to use\n\n- Rolling out EDR to endpoints and servers for the first time.\n- Tuning noisy policies or investigating EDR-caused performance issues.\n- Building behavioral detections for your threat model.\n- Running threat hunts across endpoint telemetry.\n- Defining response playbooks (isolate, contain, remediate) with approval gates.\n\n## Core concepts\n\n- **Coverage is the metric that matters most.** Unprotected endpoints are invisible endpoints. Track deployment % by asset class relentlessly — servers and OT-adjacent systems included.\n- **Prevention vs detection modes.** Modern EDR does both: block known-malicious behaviors automatically, detect-and-alert on suspicious ones. Progressively enable blocking on high-confidence behaviors; keep detection on the ambiguous.\n- **Behavioral detections beat IOCs.** Detect techniques (credential dumping, LSASS access, suspicious parent-child process chains) mapped to ATT&CK — they survive attacker infrastructure changes.\n- **Policy layering.** Baseline policies for all endpoints, stricter for servers and high-risk groups, monitor-only for fragile\u002Flegacy systems with compensating controls. One global policy fits nobody.\n- **Telemetry retention.** EDR telemetry is your best hunting and investigation dataset — retain as long as budget allows (90+ days ideal), and know exactly what you keep.\n- **Response actions with gates.** Network isolation, process kill, and file quarantine are powerful — define who may trigger them, require approval for broad actions, and log everything.\n- **Tamper protection.** Attackers kill EDR first. Enforce tamper protection, alert on agent uninstall\u002Fdisable attempts, and monitor agent health as a security signal.\n- **Performance partnership.** EDR scans cost CPU\u002FIO — work with IT on exclusions for legitimate heavy workloads (build servers, databases) via documented, reviewed exception processes, not ad-hoc disabling.\n- **Threat hunting.** Proactive hypothesis-driven searches across EDR telemetry (\"show me all LSASS access outside expected processes\") catch what automated detections miss.\n- **Integration.** EDR alerts feed the SIEM\u002FSOC with process-tree context; EDR telemetry enriches firewall and identity investigations. An isolated EDR console is half the value.\n\n- **Cloud workload coverage.** Containers and serverless need their own sensor strategy — classic host agents do not cover ephemeral workloads. Plan EDR\u002FCWPP coverage per workload type.\n- **Offline and air-gapped endpoints.** Devices off-network for weeks miss policy updates and detections. Define maximum offline tolerance and catch-up procedures.\n\n## Practical workflow\n\n1. **Deploy for coverage:** phased rollout (IT pilot → general population → servers → tricky segments), tracking install % daily. Resolve the long tail — the last 5% takes 50% of the effort and is often the riskiest.\n2. **Verify telemetry:** confirm events flowing per endpoint, check for blind spots (agent version skew, policy gaps, offline systems), and alert on agent health failures.\n3. **Tune policies:** start from vendor recommended baselines, adjust for your environment, document every exclusion with justification and review date. Re-tune quarterly.\n4. **Build behavioral detections:** map your top ATT&CK techniques to EDR detection rules; test against benign baselines; deploy with runbooks linked.\n5. **Hunt regularly:** weekly hypothesis-driven hunts using threat intel and red-team TTPs; convert hunt findings into permanent detections.\n6. **Operate response:** playbooks for isolate\u002Fkill\u002Fquarantine with approval gates; post-action verification (re-scan, monitor for re-infection); lessons fed back into detections and policy.\n\n### Quick wins\n\n- Enable tamper protection everywhere this week — it is the cheapest high-value control\n- Audit agent coverage by asset class; close the server gap first\n- Review and justify every policy exclusion older than 90 days\n\n### Sustaining the practice\n\n- Review policy exclusions quarterly — each needs re-justification or removal\n- Re-run coverage audits monthly; new systems must get agents at provisioning\n- Hunt cadence: at least weekly, tied to current threat intel\n- Test tamper-protection and agent-health alerting with simulated disable attempts\n\n### Metrics that prove it works\n\n- Agent coverage % by asset class (target: 98%+)\n- Mean time to detect and to contain on endpoint incidents\n- False-positive rate per policy\u002Fdetection; analyst action rate\n- Threat-hunt findings converted to detections per quarter\n\n## Common pitfalls\n\n- **Monitor-only forever.** Detection without blocking on high-confidence behaviors leaves dwell time on the table. Progressively enable prevention.\n- **Coverage theater.** \"Deployed\" with 70% coverage and no plan for the rest. The uncovered 30% is where attackers live.\n- **Exclusion sprawl.** Every performance complaint becomes a permanent exclusion. Review exclusions quarterly with security+IT jointly.\n- **Killing the agent to 'fix' performance.** Disabling EDR for speed is a security incident, not a fix. Tune, exclude narrowly, or upgrade hardware.\n- **No tamper protection.** Attackers' first move is blinding the sensor. Enforce it and alert on tampering attempts.\n- **Alert-only hunting.** EDR telemetry unused for proactive hunting wastes its best capability. Schedule hunts like any other security operation.\n- **Forgetting servers.** Laptop-focused rollouts leave the crown-jewel servers unprotected. Servers get agents with server-tuned policies.\n- **Response without verification.** Isolating a host and calling it done misses persistence and lateral movement. Verify with re-scan and monitoring.\n- **Treating EDR as antivirus replacement only.** Its investigation and hunting value dwarfs the blocking value — train analysts on the telemetry, not just the alerts.\n- **No offline-device strategy.** Laptops off VPN for a month return with stale policies and missed detections. Enforce check-in requirements.\n",{"name":5,"category":24,"description":7},"security","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-edr-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill edr-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill edr-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill edr-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-edr-pro\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]