[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D47X9AR71MGQR8JSG2DGXW":3,"skill-same:01M7D47X9AR71MGQR8JSG2DGXW":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7D47X9AR71MGQR8JSG2DGXW","phishing-triage",null,"Analyze a suspicious email, SMS or message for phishing\u002Fsmishing using mlab.sh - sender address reputation, domain spoofability (SPF\u002FDKIM\u002FDMARC), embedded URL analysis, callback phone numbers and smishing scoring. Use when the user pastes a suspicious message, reports a phishing attempt, or asks whether an email\u002FSMS\u002Flink is legit.","mlab-sh\u002Fmlab-claude","mlab-sh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F197380970?v=4","01M7D45Z8NKEZYYHGF1F1HFZ00","Mlab.sh","01M7D45Z9FXN34R73J4E5D9F63",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fphishing-triage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: phishing-triage\ndescription: Analyze a suspicious email, SMS or message for phishing\u002Fsmishing using mlab.sh - sender address reputation, domain spoofability (SPF\u002FDKIM\u002FDMARC), embedded URL analysis, callback phone numbers and smishing scoring. Use when the user pastes a suspicious message, reports a phishing attempt, or asks whether an email\u002FSMS\u002Flink is legit.\n---\n\n# Phishing \u002F Smishing Triage\n> Before interpreting any tool result, read `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Ftool-reference.md`: verified output shapes and gotchas that override intuition.\n\n\n## Workflow\n\nDecompose the message into its indicators, score each, then give one combined verdict.\n\n### 1. The message body (SMS or short message)\n\nFor an SMS or text-style message, run `smishing_risk` on the full RAW body - the IOC extractor does not parse defanged text, so refang (`hxxp` -> `http`, `[.]` -> `.`) if you only have a defanged copy. Pass `country` matching the user's locale pack (default `fr`). Use the returned `iocs[]` as your indicator list rather than parsing by hand, and re-defang everything for the report.\n\n### 2. The sender\n\n- Email address → `scan_email`. Key signals: disposable\u002Frole mailbox type, and the domain's spoofability verdict (SPF\u002FDKIM\u002FDMARC). A spoofable domain means the From header proves nothing.\n- Phone number → `scan_phone`. VoIP line type and country\u002Foperator mismatches with the claimed brand are strong signals.\n\n### 3. Embedded links\n\nFor each URL, run `scan_url` (static). Highlights to check: punycode\u002FUnicode host confusion, credentials-in-URL, IP-literal hosts, dangerous file extensions, known shorteners, embedded redirect targets, and the host's registration age when a previous domain scan exists.\n\nOnly set `resolve: true` on a shortener when the destination is needed for the verdict, and note in the report that the link was followed. If the sender domain itself looks central to the case and is unscanned, offer to run `start_domain_scan` (it consumes quota).\n\n### 4. Verdict\n\n```\n## Verdict: \u003Cphishing | suspicious | likely legitimate> (confidence: \u003Clow\u002Fmed\u002Fhigh>)\n\n**One-line summary for the end user:** \u003Cplain-language, no jargon>\n\n### Signals\n| Element | Finding | Weight |\n\u003Csender, each link, body score - with the tool-reported reasons>\n\n### What to do\n\u003Cfor an end user: don't click \u002F report to X \u002F delete. For a SOC: block indicators, search mail logs for the sender\u002FURL pattern>\n\n### Extracted IOCs\n\u003Cclean list, ready to paste into a blocklist or hunt>\n```\n\n## Rules\n\n- Quote the scoring reasons the tools return; never present a bare number as the argument.\n- A low smishing score with `conclusive: false` is not a clean bill; say what could not be checked.\n- Brand impersonation is a judgment call: state which brand the message imitates and which signals support that.\n- Never advise the user to interact with the message (reply, call the number, open the link) to \"test\" it.\n","# Phishing \u002F Smishing Triage\n> Before interpreting any tool result, read `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Ftool-reference.md`: verified output shapes and gotchas that override intuition.\n\n\n## Workflow\n\nDecompose the message into its indicators, score each, then give one combined verdict.\n\n### 1. The message body (SMS or short message)\n\nFor an SMS or text-style message, run `smishing_risk` on the full RAW body - the IOC extractor does not parse defanged text, so refang (`hxxp` -> `http`, `[.]` -> `.`) if you only have a defanged copy. Pass `country` matching the user's locale pack (default `fr`). Use the returned `iocs[]` as your indicator list rather than parsing by hand, and re-defang everything for the report.\n\n### 2. The sender\n\n- Email address → `scan_email`. Key signals: disposable\u002Frole mailbox type, and the domain's spoofability verdict (SPF\u002FDKIM\u002FDMARC). A spoofable domain means the From header proves nothing.\n- Phone number → `scan_phone`. VoIP line type and country\u002Foperator mismatches with the claimed brand are strong signals.\n\n### 3. Embedded links\n\nFor each URL, run `scan_url` (static). Highlights to check: punycode\u002FUnicode host confusion, credentials-in-URL, IP-literal hosts, dangerous file extensions, known shorteners, embedded redirect targets, and the host's registration age when a previous domain scan exists.\n\nOnly set `resolve: true` on a shortener when the destination is needed for the verdict, and note in the report that the link was followed. If the sender domain itself looks central to the case and is unscanned, offer to run `start_domain_scan` (it consumes quota).\n\n### 4. Verdict\n\n```\n## Verdict: \u003Cphishing | suspicious | likely legitimate> (confidence: \u003Clow\u002Fmed\u002Fhigh>)\n\n**One-line summary for the end user:** \u003Cplain-language, no jargon>\n\n### Signals\n| Element | Finding | Weight |\n\u003Csender, each link, body score - with the tool-reported reasons>\n\n### What to do\n\u003Cfor an end user: don't click \u002F report to X \u002F delete. For a SOC: block indicators, search mail logs for the sender\u002FURL pattern>\n\n### Extracted IOCs\n\u003Cclean list, ready to paste into a blocklist or hunt>\n```\n\n## Rules\n\n- Quote the scoring reasons the tools return; never present a bare number as the argument.\n- A low smishing score with `conclusive: false` is not a clean bill; say what could not be checked.\n- Brand impersonation is a judgment call: state which brand the message imitates and which signals support that.\n- Never advise the user to interact with the message (reply, call the number, open the link) to \"test\" it.\n",{"name":5,"description":7},"main","0678f3559c0b5576fd964874a3debae3f6b5a31c","plugins\u002Fmlab\u002Fskills\u002Fphishing-triage",0,"https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude","https:\u002F\u002Fgithub.com\u002Fmlab-sh","https:\u002F\u002Fmlab.sh","MLAB is a modular security analysis platform for IOC analysis at scale","2026-10-22 03:39:43",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add mlab-sh\u002Fmlab-claude --skill phishing-triage",{"tool":39,"command":40},"bunx","bunx skills add mlab-sh\u002Fmlab-claude --skill phishing-triage",{"tool":42,"command":43},"pnpm","pnpm dlx skills add mlab-sh\u002Fmlab-claude --skill phishing-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fphishing-triage\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"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},"01M7D494QGV4DTD8PE8NTDHRM4","threat-watch","Generate a threat landscape digest from mlab.sh - recent critical\u002FKEV CVEs filtered to a declared technology stack, with actor attribution. Use when the user asks what is new in vulnerabilities, wants a daily\u002Fweekly threat brief, asks about recent CVEs for a product, or sets up a recurring watch on their stack.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fthreat-watch\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":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7D48Z3YTQN4ZHMGTH1EXXR5","supply-chain-audit","Full supply-chain audit of a project - postmortem detects malicious code, install hooks and risky dependencies locally, then mlab.sh enriches what it finds (hashes, endpoints, actors, CVEs). Use when the user asks to audit a project's dependencies or supply chain, check a repo for malicious packages, or vet a codebase before adoption or deployment.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsupply-chain-audit\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7D48RXRAHKVAE6SWQT2EN6H","smishing-campaign","Analyze a batch of reported SMS\u002Ftext messages through mlab.sh - score each for smishing, cluster them into campaigns, and extract the shared infrastructure (URLs, callback numbers, sender patterns). Use when the user has multiple reported SMS from users\u002Femployees, or investigates an SMS phishing wave. For a single message, phishing-triage does the job.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsmishing-campaign\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D48KBNYFBJNS9MEHHWMW80","script-triage","Statically analyze a suspicious shell script through mlab.sh - install.sh, cron payloads, CI steps, curl-pipe-sh one-liners. Flags dangerous constructs (download-piped-to-shell, base64 decoding, reverse shells, persistence, anti-forensics, destructive deletes), extracts every IOC and enriches them. Use when the user pastes shell code and asks if it is safe\u002Fmalicious, or provides a .sh file to vet before running it.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fscript-triage\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D48E9ZYDPAN85NXAED50E6","sbom-export","Generate a CycloneDX SBOM locally with postmortem and push it through mlab.sh vulnerability scanning - for projects or container images where no single lockfile can be pasted. Use when the user asks for an SBOM, needs vuln scanning of a container image or a multi-ecosystem repo, or when sbom-audit lacks a usable lockfile.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsbom-export\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7D487A4AZ6KK5CV214QG013","sbom-audit","Audit a dependency lockfile or SBOM for known vulnerabilities via mlab.sh, prioritize findings by KEV status and EPSS, and attribute actively exploited CVEs to threat actors. Use when the user provides a lockfile (package-lock.json, yarn.lock, pnpm-lock.yaml, Cargo.lock, requirements.txt, poetry.lock, uv.lock, Pipfile.lock, go.sum, composer.lock, Gemfile.lock, pom.xml, gradle.lockfile, packages.lock.json, pubspec.lock, mix.lock) or a CycloneDX \u002F SPDX SBOM, or asks to check dependencies for vulnerabilities.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsbom-audit\u002FSKILL.md",[],[]]