[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVZCXTW95B7FGFGYVRSP6Z":3,"skill-same:01M7EVZCXTW95B7FGFGYVRSP6Z":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},"01M7EVZCXTW95B7FGFGYVRSP6Z","soc-analyst",null,"Run security operations center workflows — alert triage, investigation, escalation, and shift handover for detection and response.","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-soc-analyst\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: soc-analyst\ndescription: Run security operations center workflows — alert triage, investigation, escalation, and shift handover for detection and response.\ncategory: security\n---\n\n## Overview\n\nA SOC analyst turns the firehose of security telemetry into decisions: is this alert real, what is its scope, and what happens next? The work is triage under time pressure — distinguishing true positives from noise, containing what matters, and escalating with clean evidence. Good SOC work is a disciplined workflow, not heroics.\n\nThis skill covers alert triage, investigation method, severity classification, escalation, and the hygiene (runbooks, tuning, handover) that keeps a SOC effective instead of drowning.\n\nThe SOC is the organization's nervous system — it does not prevent every injury, but it determines how fast the body reacts. Analyst quality compounds: every well-investigated alert improves the runbook, every tuning ticket reduces tomorrow's noise, and every clean escalation builds IR trust. Protect analyst time for investigation, not just queue-clearing.\n\n## When to use\n\n- Triaging SIEM\u002FEDR\u002FIDS alerts and deciding true vs false positive.\n- Investigating a suspicious host, user, or network pattern end to end.\n- Building or improving detection runbooks and alert tuning.\n- Handling shift handover so nothing in flight gets dropped.\n- Measuring and improving SOC performance (MTTD, MTTR, false-positive rate).\n\n## Core concepts\n\n- **The triage question:** \"Is there evidence of malicious activity, and if so, what is the blast radius?\" Everything else is detail.\n- **Alert severity vs incident severity:** an alert is a signal; an incident is a confirmed event with impact. Do not declare incidents from single alerts.\n- **Kill chain \u002F ATT&CK mapping:** map observed activity to tactics (initial access → execution → persistence → exfil → impact). It tells you what to look for next and what the attacker still needs.\n- **Blast radius first:** before deep forensics, bound the scope — which hosts, users, data. Containment decisions need scope, not perfect attribution.\n- **Evidence preservation:** note timestamps, capture volatile data early, avoid destructive actions on the affected host until forensics is consulted.\n- **Runbooks:** every high-volume alert type gets a written triage path. Analysts follow the runbook; the runbook gets improved from analyst feedback.\n\n- **Analyst tiers with clear escalation.** L1 triages against runbooks, L2 investigates deeply, L3 hunts and engineers detections. Blurred tiers mean everything lands on whoever is most senior and available.\n- **Threat intel with context.** IOC feeds are noise without relevance filtering — prioritize intel matching your industry, geography, and technology stack.\n- **Shift-left feedback.** Analysts should have a direct, fast path to detection engineers — the people closest to the alerts know best what is broken.\n\n## Practical workflow\n\n1. **Triage the queue:** sort by severity and asset criticality. For each alert: check the runbook, validate the signal (is the source reliable? is the asset real?), and disposition within the SLA — true positive, false positive, or benign-true (real activity, not malicious).\n2. **Investigate true positives:** pivot on indicators — user, host, process tree, network connections, auth logs. Build a timeline. Ask: first observed, how it got in, what it touched, whether it persists, whether data left.\n3. **Scope and classify:** determine affected hosts\u002Fusers\u002Fdata; classify severity (use a fixed rubric: e.g., confirmed compromise of a production host = P1). Map to ATT&CK for the handover.\n4. **Contain (with approval):** isolate host, disable account, block indicator — per playbook authority levels. Record every containment action with a timestamp.\n5. **Escalate cleanly:** incident ticket with summary, timeline, scope, evidence links, actions taken, and open questions. Page incident response per the escalation matrix; do not freelance beyond your authority.\n6. **Tune and hand over:** false positives get a tuning ticket (not silent dismissal); shift handover lists in-flight investigations, their state, and next steps. Update the runbook with what you learned.\n\n### Triage checklist (per alert)\n\n- [ ] Alert source and fidelity known; runbook exists\n- [ ] Asset\u002Fuser verified real and in scope\n- [ ] Corroborating evidence checked (2+ sources before \"true positive\")\n- [ ] Timeline started; first\u002Flast seen noted\n- [ ] Blast radius estimated before containment\n- [ ] Disposition + rationale logged; tuning ticket filed if FP\n\n### Sustaining the practice\n\n- Review the top-10 noisiest rules monthly; tune or justify each\n- Run quarterly purple-team or adversary-emulation validations of key detections\n- Rotate analysts through threat-intel and detection-engineering stints to build skill\n- Track analyst retention and burnout signals — turnover destroys institutional knowledge\n\n### Metrics that prove it works\n\n- MTTD and MTTR, trended monthly by severity\n- False-positive rate per detection rule (tune the worst offenders first)\n- % of alerts triaged within SLA; escalation accuracy (incidents confirmed \u002F escalations)\n- Analyst feedback loop: tuning tickets filed and closed per quarter\n\n## Common pitfalls\n\n- **Alert fatigue → click-through triage.** If analysts close alerts without investigation, the SOC is a checkbox. Tune noisy rules; measure FP rate per rule.\n- **Declaring incidents too early (or too late).** Single uncorroborated alert ≠ incident; confirmed lateral movement you sat on for a shift = breach of duty. Use the rubric.\n- **Forensics-destroying \"help.\"** Rebooting, reimaging, or running AV sweeps before evidence capture can destroy the timeline. Contain first, preserve second, remediate third.\n- **No blast-radius estimate.** Deep-diving one host while the attacker moves laterally elsewhere. Scope early, scope wide.\n- **Silent false positives.** Every FP dismissed without a tuning ticket returns next week. The tuning backlog is a SOC health metric.\n- **Bad handovers.** \"Watch the queue\" is not a handover. State, next steps, and watch items — written, every shift.\n- **Working the queue oldest-first.** Triage by severity × asset criticality, not arrival order — a P1 aging while you clear informational alerts is a process failure.\n- **Not recording benign-true dispositions.** \"Real activity, not malicious\" is tuning gold. Log it or the same alert returns forever.\n- **Treating every alert as equal effort.** A 5-minute runbook triage and a 4-hour investigation are different work items. Staff and SLA them differently.\n- **Knowledge trapped in chat.** Investigation findings shared only in chat threads are lost to the next shift. Conclusions belong in the ticket and the runbook.\n","## Overview\n\nA SOC analyst turns the firehose of security telemetry into decisions: is this alert real, what is its scope, and what happens next? The work is triage under time pressure — distinguishing true positives from noise, containing what matters, and escalating with clean evidence. Good SOC work is a disciplined workflow, not heroics.\n\nThis skill covers alert triage, investigation method, severity classification, escalation, and the hygiene (runbooks, tuning, handover) that keeps a SOC effective instead of drowning.\n\nThe SOC is the organization's nervous system — it does not prevent every injury, but it determines how fast the body reacts. Analyst quality compounds: every well-investigated alert improves the runbook, every tuning ticket reduces tomorrow's noise, and every clean escalation builds IR trust. Protect analyst time for investigation, not just queue-clearing.\n\n## When to use\n\n- Triaging SIEM\u002FEDR\u002FIDS alerts and deciding true vs false positive.\n- Investigating a suspicious host, user, or network pattern end to end.\n- Building or improving detection runbooks and alert tuning.\n- Handling shift handover so nothing in flight gets dropped.\n- Measuring and improving SOC performance (MTTD, MTTR, false-positive rate).\n\n## Core concepts\n\n- **The triage question:** \"Is there evidence of malicious activity, and if so, what is the blast radius?\" Everything else is detail.\n- **Alert severity vs incident severity:** an alert is a signal; an incident is a confirmed event with impact. Do not declare incidents from single alerts.\n- **Kill chain \u002F ATT&CK mapping:** map observed activity to tactics (initial access → execution → persistence → exfil → impact). It tells you what to look for next and what the attacker still needs.\n- **Blast radius first:** before deep forensics, bound the scope — which hosts, users, data. Containment decisions need scope, not perfect attribution.\n- **Evidence preservation:** note timestamps, capture volatile data early, avoid destructive actions on the affected host until forensics is consulted.\n- **Runbooks:** every high-volume alert type gets a written triage path. Analysts follow the runbook; the runbook gets improved from analyst feedback.\n\n- **Analyst tiers with clear escalation.** L1 triages against runbooks, L2 investigates deeply, L3 hunts and engineers detections. Blurred tiers mean everything lands on whoever is most senior and available.\n- **Threat intel with context.** IOC feeds are noise without relevance filtering — prioritize intel matching your industry, geography, and technology stack.\n- **Shift-left feedback.** Analysts should have a direct, fast path to detection engineers — the people closest to the alerts know best what is broken.\n\n## Practical workflow\n\n1. **Triage the queue:** sort by severity and asset criticality. For each alert: check the runbook, validate the signal (is the source reliable? is the asset real?), and disposition within the SLA — true positive, false positive, or benign-true (real activity, not malicious).\n2. **Investigate true positives:** pivot on indicators — user, host, process tree, network connections, auth logs. Build a timeline. Ask: first observed, how it got in, what it touched, whether it persists, whether data left.\n3. **Scope and classify:** determine affected hosts\u002Fusers\u002Fdata; classify severity (use a fixed rubric: e.g., confirmed compromise of a production host = P1). Map to ATT&CK for the handover.\n4. **Contain (with approval):** isolate host, disable account, block indicator — per playbook authority levels. Record every containment action with a timestamp.\n5. **Escalate cleanly:** incident ticket with summary, timeline, scope, evidence links, actions taken, and open questions. Page incident response per the escalation matrix; do not freelance beyond your authority.\n6. **Tune and hand over:** false positives get a tuning ticket (not silent dismissal); shift handover lists in-flight investigations, their state, and next steps. Update the runbook with what you learned.\n\n### Triage checklist (per alert)\n\n- [ ] Alert source and fidelity known; runbook exists\n- [ ] Asset\u002Fuser verified real and in scope\n- [ ] Corroborating evidence checked (2+ sources before \"true positive\")\n- [ ] Timeline started; first\u002Flast seen noted\n- [ ] Blast radius estimated before containment\n- [ ] Disposition + rationale logged; tuning ticket filed if FP\n\n### Sustaining the practice\n\n- Review the top-10 noisiest rules monthly; tune or justify each\n- Run quarterly purple-team or adversary-emulation validations of key detections\n- Rotate analysts through threat-intel and detection-engineering stints to build skill\n- Track analyst retention and burnout signals — turnover destroys institutional knowledge\n\n### Metrics that prove it works\n\n- MTTD and MTTR, trended monthly by severity\n- False-positive rate per detection rule (tune the worst offenders first)\n- % of alerts triaged within SLA; escalation accuracy (incidents confirmed \u002F escalations)\n- Analyst feedback loop: tuning tickets filed and closed per quarter\n\n## Common pitfalls\n\n- **Alert fatigue → click-through triage.** If analysts close alerts without investigation, the SOC is a checkbox. Tune noisy rules; measure FP rate per rule.\n- **Declaring incidents too early (or too late).** Single uncorroborated alert ≠ incident; confirmed lateral movement you sat on for a shift = breach of duty. Use the rubric.\n- **Forensics-destroying \"help.\"** Rebooting, reimaging, or running AV sweeps before evidence capture can destroy the timeline. Contain first, preserve second, remediate third.\n- **No blast-radius estimate.** Deep-diving one host while the attacker moves laterally elsewhere. Scope early, scope wide.\n- **Silent false positives.** Every FP dismissed without a tuning ticket returns next week. The tuning backlog is a SOC health metric.\n- **Bad handovers.** \"Watch the queue\" is not a handover. State, next steps, and watch items — written, every shift.\n- **Working the queue oldest-first.** Triage by severity × asset criticality, not arrival order — a P1 aging while you clear informational alerts is a process failure.\n- **Not recording benign-true dispositions.** \"Real activity, not malicious\" is tuning gold. Log it or the same alert returns forever.\n- **Treating every alert as equal effort.** A 5-minute runbook triage and a 4-hour investigation are different work items. Staff and SLA them differently.\n- **Knowledge trapped in chat.** Investigation findings shared only in chat threads are lost to the next shift. Conclusions belong in the ticket and the runbook.\n",{"name":5,"category":24,"description":7},"security","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-soc-analyst",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 soc-analyst",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill soc-analyst",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill soc-analyst","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-soc-analyst\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",[],[]]