[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P5TPZTE08KSMZJFE8QGKH3":3,"skill-same:01M6P5TPZTE08KSMZJFE8QGKH3":69},{"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":27,"commitSha":50,"skillDirectory":51,"forksCount":13,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6P5TPZTE08KSMZJFE8QGKH3","hunt-exceptional-conditions",null,"Hunt mishandling of exceptional conditions","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\u002Fhunt-exceptional-conditions\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"hunt exceptional conditions","hunt","for","testing","relevant","helper","scripts","scope","commands","main","community","only","public","authorization","https","license","testing tools","security","github","docs","2026-11-10 10:12:30",false,"---\nname: hunt-exceptional-conditions\ndescription: Hunt mishandling of exceptional conditions\ncategory: security\nrisk: offensive\nsource: https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\nsource_repo: elementalsouls\u002FClaude-BugHunter\nsource_type: community\ndate_added: '2026-09-20'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\u002Fblob\u002Fmain\u002FLICENSE\ncompatibility: Requires explicit written authorization for a target scope plus the\n  relevant testing tools for this technique. Docs-only; helper scripts and commands\n  not bundled.\nreport_count: 0\nsources: hackerone_public\n---\n> **⚠️ AUTHORIZED USE ONLY**\n> This skill is for educational purposes or authorized security assessments only.\n> You must have explicit, written permission from the system owner before using this tool.\n> Misuse of this tool is illegal and strictly prohibited.\n\n> **Mandatory confirmation gate**\n> Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:\n> 1. Ask the user to state the exact target URL, IP, account, or resource.\n> 2. Ask the user to confirm written authorization and the permitted scope.\n> 3. Show the exact command(s) and explain their expected effect.\n> 4. Wait for explicit confirmation in the current conversation.\n>\n> Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.\n\n# HUNT-EXCEPTIONAL-CONDITIONS — Verbose Errors \u002F Fail-Open (A10:2025)\n\n## What actually pays\n\nWell-built apps catch errors and return a clean, generic message. A broken app,\nwhen handed input it didn't expect, throws an unhandled exception and renders a\n**developer error page** straight to the client — leaking the stack trace, the\nORM\u002Fquery internals, server-side file paths, and framework\u002Flibrary versions.\nThat disclosure is the finding (and it arms SQLi\u002FRCE\u002Fpath attacks next).\n\n## Recon\n\nAny endpoint that parses input is a candidate; the richest are:\n\n```\nJSON APIs that expect typed fields:  POST \u002Fapi\u002F* with {numbers, ids, enums}\nEndpoints with numeric\u002Fid path or query params:  \u002Fitem\u002F{id}, ?page=, ?quantity=\nSearch \u002F filter \u002F sort params\nFile or content-type sensitive uploads\n```\n\n## Attack — send what the code didn't anticipate\n\nTake a known-good request and break ONE assumption at a time:\n\n- **Wrong type:** a field the app expects to be a number\u002Fstring is sent as an\n  array or object — `{\"rating\":\"x\",\"comment\":[1,2,3]}`, `{\"quantity\":{}}`.\n- **Malformed body:** truncated\u002F!invalid JSON, an unterminated string, a stray\n  brace, a wrong\u002Fmissing Content-Type.\n- **Boundary\u002Foversized:** a very long string, a huge\u002Fnegative\u002Foverflow number.\n- **Null byte \u002F control chars** embedded in a value.\n\n```\nPOST \u002Fapi\u002FFeedbacks   {\"rating\":\"notanumber\",\"comment\":[1,2,3]}\nGET  \u002Fitem\u002F' OR \u002Fitem\u002F%00   (also exercises the error path)\n```\n\nWatch the RESPONSE BODY, not just the status: a 500 (or even a 200\u002F400) whose\nbody contains a stack trace or framework error page is the signal.\n\n## What counts as a leak (the success signal)\n\nA finding is confirmed when the response body contains a cross-framework error-disclosure signature:\n\n- **Node\u002FExpress + Sequelize:** `SequelizeDatabaseError`, `node_modules\u002Fsequelize`,\n  a JS stack with internal paths.\n- **PHP:** `\u003Cb>Warning\u003C\u002Fb> ... \u002Fvar\u002Fwww\u002F...\u002Ffile.php on line N`.\n- **Python:** `Traceback (most recent call last)`, `werkzeug.exceptions`.\n- **Java:** `at com.app.Foo(Foo.java:42)` stack frames.\n- **.NET:** `Server Error in '\u002F' Application`, a `[System.XxxException: ...]` YSOD.\n\nA clean JSON error (`{\"error\":\"Invalid input\"}`) with no internals is NOT a\nfinding — that's correct handling. Disclosure of internal structure is.\n\n## Validation discipline\n\n- Capture the exact leaked artifact (path, ORM class, version, stack frame) —\n  that's the evidence. \"It returned 500\" alone is not disclosure.\n- Note what the leak enables next (e.g. a disclosed SQL error → hunt-sqli; a\n  disclosed absolute path → hunt-lfi).\n\n## When to Use\n\n- You have explicit, written authorization to assess the target in scope, and the task matches this skill's vulnerability class or technique within a bug-bounty or penetration-test engagement.\n- You need the recon, exploitation, or validation workflow described below — executed strictly inside the approved scope.\n\n## Limitations\n\n- Authorized scope only: the confirmation gate above is mandatory before any probing, exploitation, or credential-access command.\n- Docs-only import: upstream helper scripts, commands, engine, and research assets are not bundled; reinstall tooling from the source repo when needed.\n- Validate every finding (see `triage-validation`) before reporting; report via `report-writing`. Prefer a sandbox, disposable VM, or controlled lab.\n\n### Example\n\n```bash\n# Read-only first step; confirm scope before anything active.\ncat scope.txt  # target list from the authorized engagement brief\n```\n\n> Adapted from [elementalsouls\u002FClaude-BugHunter](https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: executable helpers, commands, engine, and research assets not bundled.\n","> **⚠️ AUTHORIZED USE ONLY**\n> This skill is for educational purposes or authorized security assessments only.\n> You must have explicit, written permission from the system owner before using this tool.\n> Misuse of this tool is illegal and strictly prohibited.\n\n> **Mandatory confirmation gate**\n> Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:\n> 1. Ask the user to state the exact target URL, IP, account, or resource.\n> 2. Ask the user to confirm written authorization and the permitted scope.\n> 3. Show the exact command(s) and explain their expected effect.\n> 4. Wait for explicit confirmation in the current conversation.\n>\n> Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.\n\n# HUNT-EXCEPTIONAL-CONDITIONS — Verbose Errors \u002F Fail-Open (A10:2025)\n\n## What actually pays\n\nWell-built apps catch errors and return a clean, generic message. A broken app,\nwhen handed input it didn't expect, throws an unhandled exception and renders a\n**developer error page** straight to the client — leaking the stack trace, the\nORM\u002Fquery internals, server-side file paths, and framework\u002Flibrary versions.\nThat disclosure is the finding (and it arms SQLi\u002FRCE\u002Fpath attacks next).\n\n## Recon\n\nAny endpoint that parses input is a candidate; the richest are:\n\n```\nJSON APIs that expect typed fields:  POST \u002Fapi\u002F* with {numbers, ids, enums}\nEndpoints with numeric\u002Fid path or query params:  \u002Fitem\u002F{id}, ?page=, ?quantity=\nSearch \u002F filter \u002F sort params\nFile or content-type sensitive uploads\n```\n\n## Attack — send what the code didn't anticipate\n\nTake a known-good request and break ONE assumption at a time:\n\n- **Wrong type:** a field the app expects to be a number\u002Fstring is sent as an\n  array or object — `{\"rating\":\"x\",\"comment\":[1,2,3]}`, `{\"quantity\":{}}`.\n- **Malformed body:** truncated\u002F!invalid JSON, an unterminated string, a stray\n  brace, a wrong\u002Fmissing Content-Type.\n- **Boundary\u002Foversized:** a very long string, a huge\u002Fnegative\u002Foverflow number.\n- **Null byte \u002F control chars** embedded in a value.\n\n```\nPOST \u002Fapi\u002FFeedbacks   {\"rating\":\"notanumber\",\"comment\":[1,2,3]}\nGET  \u002Fitem\u002F' OR \u002Fitem\u002F%00   (also exercises the error path)\n```\n\nWatch the RESPONSE BODY, not just the status: a 500 (or even a 200\u002F400) whose\nbody contains a stack trace or framework error page is the signal.\n\n## What counts as a leak (the success signal)\n\nA finding is confirmed when the response body contains a cross-framework error-disclosure signature:\n\n- **Node\u002FExpress + Sequelize:** `SequelizeDatabaseError`, `node_modules\u002Fsequelize`,\n  a JS stack with internal paths.\n- **PHP:** `\u003Cb>Warning\u003C\u002Fb> ... \u002Fvar\u002Fwww\u002F...\u002Ffile.php on line N`.\n- **Python:** `Traceback (most recent call last)`, `werkzeug.exceptions`.\n- **Java:** `at com.app.Foo(Foo.java:42)` stack frames.\n- **.NET:** `Server Error in '\u002F' Application`, a `[System.XxxException: ...]` YSOD.\n\nA clean JSON error (`{\"error\":\"Invalid input\"}`) with no internals is NOT a\nfinding — that's correct handling. Disclosure of internal structure is.\n\n## Validation discipline\n\n- Capture the exact leaked artifact (path, ORM class, version, stack frame) —\n  that's the evidence. \"It returned 500\" alone is not disclosure.\n- Note what the leak enables next (e.g. a disclosed SQL error → hunt-sqli; a\n  disclosed absolute path → hunt-lfi).\n\n## When to Use\n\n- You have explicit, written authorization to assess the target in scope, and the task matches this skill's vulnerability class or technique within a bug-bounty or penetration-test engagement.\n- You need the recon, exploitation, or validation workflow described below — executed strictly inside the approved scope.\n\n## Limitations\n\n- Authorized scope only: the confirmation gate above is mandatory before any probing, exploitation, or credential-access command.\n- Docs-only import: upstream helper scripts, commands, engine, and research assets are not bundled; reinstall tooling from the source repo when needed.\n- Validate every finding (see `triage-validation`) before reporting; report via `report-writing`. Prefer a sandbox, disposable VM, or controlled lab.\n\n### Example\n\n```bash\n# Read-only first step; confirm scope before anything active.\ncat scope.txt  # target list from the authorized engagement brief\n```\n\n> Adapted from [elementalsouls\u002FClaude-BugHunter](https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: executable helpers, commands, engine, and research assets not bundled.\n",{"name":5,"risk":43,"source":44,"license":14,"sources":45,"category":35,"date_added":46,"description":7,"source_repo":47,"source_type":28,"report_count":13,"compatibility":48,"license_source":49},"offensive","https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter","hackerone_public","2026-09-20","elementalsouls\u002FClaude-BugHunter","Requires explicit written authorization for a target scope plus the relevant testing tools for this technique. Docs-only; helper scripts and commands not bundled.","https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fhunt-exceptional-conditions","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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-exceptional-conditions",{"tool":61,"command":62},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-exceptional-conditions",{"tool":64,"command":65},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill hunt-exceptional-conditions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fhunt-exceptional-conditions\u002FSKILL.md",true,[],[70,95,119,141,169,193],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"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",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[82,83,84,85,86,87,72,88,89,90,91,29,28,27,92,93,25,24,22,94],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","active","critical","implementing",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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",[],[102,103,104,105,106,107,108,109,110,111,112,113,114,29,115,28,116,117,93,118],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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",[],[126,127,128,129,36,130,131,33,32,132,133,134,135,28,27,136,137,138,139,140],"transcript","youtube transcript","youtube","safe","codex","research","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":158,"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",[147,150,153],{"categoryNo":148,"categoryName":149,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":151,"categoryName":152,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[126,127,128,159,129,160,36,130,33,161,162,163,164,133,165,28,27,166,167,168],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":179,"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",[175,178],{"categoryNo":176,"categoryName":177,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":151,"categoryName":152,"taxonomyType":79,"taxonomyTypeDesc":80},[128,180,181,106,129,182,183,184,185,33,163,186,187,188,189,27,190,136,191,192],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":200,"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",[199],{"categoryNo":148,"categoryName":149,"taxonomyType":79,"taxonomyTypeDesc":80},[201,128,202,203,129,160,161,204,205,162,163,164,133,206,165,28,27,166,207,139],"youtube full","full","google","server","dlp","credits","automatic"]