[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DBGJR5WB8RQMBX2EVNPZP1":3,"skill-same:01M7DBGJR5WB8RQMBX2EVNPZP1":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7DBGJR5WB8RQMBX2EVNPZP1","web-report",null,"alicewe1\u002Falice_skill","alicewe1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102134151?v=4","01M7D9STCM8HAESM958JP0989K","Alice_we","01M7D9STDR22MTD9FTTWPAZNV8",64,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fweb-report\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: web-report\ndescription: >\n  Web penetration testing report generation skill. Activate when the user wants to write, generate,\n  or finalize a report for a web pentest or bug bounty engagement. Consolidates outputs from\n  web-recon, web-exploitation, and web-postexploitation skills into a structured technical and\n  executive report. Produces findings in standardized format (name, criticality, CVSS, description,\n  impact, recommendation, evidence). Default mode: combined technical + executive report.\n  Publishes to Notion via MCP when available.\ndomain: web-application-security\ntags: [report, pentest-report, web-pentest, bug-bounty, cvss, executive-report, technical-report, notion]\nx-alice-class: pentest\n---# Web Report — Technical & Executive Report Generation\n\n## Architecture\n\nThis skill is Claude-driven. It reads output directories from prior skills, organizes all confirmed\nfindings, writes the full report in the correct format, reviews it twice, and publishes to Notion.\n\n```\nInput directories (any combination):\n  $RECON_OUT    — web-recon output (nuclei findings, live hosts, JS secrets, CMS results)\n  $EXPLOIT_OUT  — web-exploitation output (sqli\u002F, xss\u002F, lfi\u002F, ssrf\u002F, auth\u002F, findings\u002F)\n  $POSTEX_OUT   — web-postexploitation output (if applicable)\n  $EVIDENCE_DIR — screenshots directory (gowitness\u002F, manual captures)\n```\n\n---\n\n## Initial Setup\n\n```bash\nTARGET=\"https:\u002F\u002Ftarget.com\"\nDOMAIN=\"target.com\"\nCLIENT=\"Client Company Name\"\nENGAGEMENT=\"Web Application Penetration Test\"\nTESTER=\"[Your Name \u002F Company]\"\nDATE=\"$(date +%Y-%m-%d)\"\n\nRECON_OUT=\"$(pwd)\u002Ftarget\"\nEXPLOIT_OUT=\"$(pwd)\u002Ftarget-exploit\"\nPOSTEX_OUT=\"$(pwd)\u002Ftarget-postex\"       # leave empty if not applicable\nEVIDENCE_DIR=\"$(pwd)\u002Ftarget\u002Fevidence\"\n\n# Report mode — default: combined (recommended)\nREPORT_MODE=\"combined\"  # options: combined | technical | executive\n```\n\nCreate progress tasks with TaskCreate:\n```\n\"PHASE 1 — Finding Triage & Consolidation\"\n\"PHASE 2 — Evidence Collection & Organization\"\n\"PHASE 3 — Report Writing\"\n\"PHASE 4 — Review #1 (completeness and technical accuracy)\"\n\"PHASE 5 — Review #2 (clarity, language, formatting)\"\n\"PHASE 6 — Notion Publication\"\n```\n\n---\n\n## Report Modes\n\n| Mode | Target audience | What it includes |\n|------|----------------|-----------------|\n| `combined` (default) | Mixed — technical and management | Full technical detail + executive sections with plain-language explanations. Recommended when audience is unknown. |\n| `technical` | Security team, developers | Full technical detail, commands, payloads, reproduction steps |\n| `executive` | C-level, managers, non-technical | Summary, business impact, risk ratings, no raw payloads or commands |\n\n**When mode is not specified: always use `combined`.**\n\n---\n\n## PHASE 1 — Finding Triage & Consolidation\n\nRead all confirmed findings from prior skill outputs:\n\n```bash\n# web-recon findings\ncat \"$RECON_OUT\u002Fvulns\u002Fnuclei.txt\" 2>\u002Fdev\u002Fnull          # nuclei confirmed findings\ncat \"$RECON_OUT\u002Fjs\u002Fsecrets.json\" 2>\u002Fdev\u002Fnull           # JS secrets\ncat \"$RECON_OUT\u002Fvulns\u002Fcms_*.txt\" 2>\u002Fdev\u002Fnull           # CMS vulnerabilities\n\n# web-exploitation findings\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fsqli_confirmed.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fxss_confirmed.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Flfi_confirmed.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fssrf_confirmed.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fopen_redirect.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fjwt_endpoints.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fcookie_issues.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fclickjacking.txt\" 2>\u002Fdev\u002Fnull\n\n# List all screenshots\nls \"$EVIDENCE_DIR\u002F\" 2>\u002Fdev\u002Fnull\nls \"$RECON_OUT\u002Fscreenshots\u002F\" 2>\u002Fdev\u002Fnull\n```\n\nBuild a consolidated finding list, grouped by severity:\n```\nCRITICAL  — RCE, SQLi with data extraction, SSRF→cloud metadata, Authentication bypass (full account takeover)\nHIGH      — SQLi (no output), Stored XSS, SSTI, XXE, LFI with sensitive file read, JWT algorithm confusion, File upload\nMEDIUM    — Reflected XSS, IDOR, CSRF on sensitive action, Open redirect, Broken auth (partial), Insecure deserialization\nLOW       — Clickjacking, Missing security headers, Information disclosure, DOM XSS (limited impact)\nINFO      — Best practice recommendations, exposed JS source maps, verbose error messages\n```\n\n---\n\n## PHASE 2 — Evidence Organization\n\n### Screenshot cataloging\n\n```bash\n# List and describe all evidence\nls -lt \"$EVIDENCE_DIR\u002F\" 2>\u002Fdev\u002Fnull\nls -lt \"$RECON_OUT\u002Fscreenshots\u002F\" 2>\u002Fdev\u002Fnull   # gowitness screenshots\n\n# For each finding, identify its evidence file(s)\n# Naming convention: \u003Cseverity>_\u003Cfinding_type>_\u003Cdescription>.\u003Cext>\n# Example:\n#   critical_sqli_login_page_error.png\n#   high_xss_stored_comment_field.png\n#   high_lfi_etc_passwd.png\n```\n\nFor each screenshot\u002Fevidence file, write a 1-2 sentence explanation:\n- **What** is visible in the screenshot\n- **Why** it demonstrates the vulnerability (what makes it a confirmed finding vs. a hypothesis)\n\n### Submitting screenshots to Notion\n\nWhen Notion MCP is available:\n```\n1. Create finding page: mcp__Notion__notion-create-pages\n2. For each screenshot: describe it in the evidence block (Notion does not support direct image upload via API — note the local file path and describe it clearly)\n3. If images need to be hosted: upload to an image hosting service and embed the URL\n```\n\n---\n\n## PHASE 3 — Report Writing\n\n### Document structure\n\n```\nCOVER PAGE\n  - Client name\n  - Engagement type\n  - Date\n  - Tester name \u002F company\n\nEXECUTIVE SUMMARY  (always present, even in technical mode)\n  - Overview of tested scope\n  - Total vulnerabilities by severity (table)\n  - Overall risk score\n  - 3-5 key findings in plain language\n  - General priority recommendation\n\nMETHODOLOGY (technical \u002F combined)\n  - Tools used\n  - Phases executed\n  - Scope limitations and notes\n\nVULNERABILITY SUMMARY (table)\n  | # | Name | Criticality | CVSS | Endpoint | Status |\n  |---|------|-------------|------|----------|--------|\n\nDETAILED FINDINGS (one section per finding)\n\nCONCLUSION\n\nAPPENDIX — Tools and References\n```\n\n---\n\n## Finding Template — Required Format\n\n**Apply this template for every confirmed finding. Write each field as a full paragraph.**\n\n```\n### [CRITICALITY] — [Vulnerability Name]\n\n**Criticality:** Critical \u002F High \u002F Medium \u002F Low \u002F Informational\n**CVSS Score:** X.X (Critical\u002FHigh\u002FMedium\u002FLow)\n**CVSS Vector:** CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H\n**Affected endpoint:** https:\u002F\u002Ftarget.com\u002Fendpoint?param=value\n**Method:** GET \u002F POST \u002F PUT\n**Vulnerable parameter:** param_name\n\n---\n\n**Description**\n\n[1 robust paragraph — minimum 4-6 sentences. Explain WHAT the vulnerability is, HOW it works\ntechnically, WHY this endpoint is vulnerable, and what code\u002Fconfiguration characteristic makes\nit exploitable. In combined\u002Fexecutive mode: open with a plain-language analogy before the\ntechnical detail.]\n\n---\n\n**Impact \u002F Observation**\n\n[1 robust paragraph — minimum 4-6 sentences. Explain WHAT an attacker CAN do by exploiting this\nvulnerability, what data or systems are at risk, what the business impact is (not just technical),\nand how likely real exploitation is. Note if the vulnerability is exploitable remotely, without\nauthentication, or chainable with others.]\n\n---\n\n**Recommendation \u002F Remediation**\n\n[1 robust paragraph — minimum 4-6 sentences. Explain WHAT must be done to fix it, with enough\ntechnical specificity for a developer to implement. Include primary fix + defense in depth\n(multiple control layers). Mention recommended fix timeline based on criticality.]\n\n---\n\n**Evidence**\n\n[For each screenshot or PoC:]\n\n*Figure X — [descriptive title]*\n`File: evidence\u002Fcritical_sqli_login.png`\n\n> [2-4 sentences explaining WHAT is happening in the image: what was sent, what the server\n> returned, what this proves. Language clear enough for a non-technical person to understand\n> that a real problem occurred.]\n\n[If PoC in code:]\n\\`\\`\\`http\nGET \u002Fendpoint?id=1' OR 1=1-- HTTP\u002F1.1\nHost: target.com\n...\n\\`\\`\\`\n*The above demonstrates [what was done]. The server response confirms [what was observed].*\n```\n\n---\n\n## CVSS Reference Table (web findings)\n\nUse these as baseline — adjust based on actual exploitability and scope:\n\n| Vulnerability | CVSS Base | Criticality | Vector |\n|----------------|-----------|-------------|--------|\n| RCE (unauthenticated) | 9.8 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| SQLi (data extraction) | 9.8 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| SSRF → cloud metadata | 9.1 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:C\u002FC:H\u002FI:L\u002FA:N |\n| Auth bypass (full ATO) | 9.8 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| SSTI → RCE | 9.8 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| File upload → RCE | 9.8 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| XXE (file read) | 7.5 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N |\n| LFI (sensitive files) | 7.5 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N |\n| JWT algorithm confusion | 9.1 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:N |\n| JWT weak secret | 8.8 | High | AV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:N |\n| Stored XSS | 8.8 | High | AV:N\u002FAC:L\u002FPR:L\u002FUI:R\u002FS:C\u002FC:H\u002FI:H\u002FA:N |\n| IDOR (sensitive data) | 8.1 | High | AV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:N |\n| Insecure deserialization | 8.8 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| Broken auth (partial) | 7.5 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N |\n| SQLi (blind, no output) | 8.6 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N |\n| SSRF (internal network) | 8.6 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:C\u002FC:H\u002FI:N\u002FA:N |\n| Reflected XSS | 6.1 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:C\u002FC:L\u002FI:L\u002FA:N |\n| CSRF (sensitive action) | 6.5 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:U\u002FC:N\u002FI:H\u002FA:N |\n| Open redirect | 6.1 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:C\u002FC:L\u002FI:L\u002FA:N |\n| CRLF injection | 6.1 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:C\u002FC:L\u002FI:L\u002FA:N |\n| Host header injection | 7.2 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:C\u002FC:L\u002FI:L\u002FA:N |\n| Clickjacking | 4.7 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:C\u002FC:N\u002FI:L\u002FA:N |\n| Missing security headers | 3.1 | Low | AV:N\u002FAC:H\u002FPR:N\u002FUI:R\u002FS:U\u002FC:L\u002FI:N\u002FA:N |\n| Information disclosure | 5.3 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:L\u002FI:N\u002FA:N |\n| Exposed JS source map | 5.3 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:L\u002FI:N\u002FA:N |\n| Exposed .git repository | 7.5 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N |\n\n> **Adjust CVSS based on context**: if authentication is required (PR:L or PR:H), if the scope changes (S:C vs S:U), or if chaining is needed (AC:H).\n\n---\n\n## PHASE 4 & 5 — Double Review\n\n**Review #1 — Technical accuracy:**\n- Every finding has: name, criticality, CVSS score + vector, affected endpoint, description, impact, recommendation, evidence\n- CVSS scores are consistent with the actual exploitability demonstrated\n- Evidence correctly described — screenshots match their finding\n- Reproduction steps are accurate and testable\n- No finding is listed without confirmed exploitation evidence\n\n**Review #2 — Language, clarity, and formatting:**\n- All text is clear and consistent in language and style\n- Executive sections use no jargon without explanation\n- No spelling or grammatical errors\n- Paragraphs are 4-6 sentences minimum and substantive\n- Table of findings is complete and sorted by CVSS (highest first)\n- All evidence files are correctly referenced (file paths or Notion links)\n\n**After both reviews:** explicitly confirm: *\"Report reviewed twice. No pending items identified.\"*\n\n---\n\n## PHASE 6 — Notion Publication\n\nWhen `mcp__Notion__*` is available:\n\n```\n1. Create parent page: mcp__Notion__notion-create-pages\n   Title: \"Pentest Report — [CLIENT] — [DATE]\"\n   Content: Executive Summary + Finding Summary Table\n\n2. For each finding (Critical\u002FHigh\u002FMedium):\n   Create subpage: mcp__Notion__notion-create-pages (child of parent)\n   Title: \"[CVSS] [CRITICALITY] — [Vulnerability Name]\"\n   Content: Full finding in template format\n\n3. Create appendix page with:\n   - Tools used\n   - Scope and methodology\n   - Raw output references (file paths)\n```\n\n---\n\n## Executive Summary Template\n\n```\n## Executive Summary\n\nThis report presents the results of the penetration test conducted against [TARGET] from\n[START_DATE] to [END_DATE], performed by [TESTER]. The objective of the engagement was to\nidentify security vulnerabilities in the web application and assess the potential impact of\ntheir exploitation.\n\n**Assessed scope:** [list of in-scope URLs\u002Fendpoints]\n\n**Overall result:** X vulnerabilities were identified: Y critical, Z high, W medium, and V low\nseverity. [1-2 sentences summarizing the most severe finding and its business impact.]\n\n**Severity distribution:**\n| Severity      | Count |\n|---------------|-------|\n| Critical      | X     |\n| High          | X     |\n| Medium        | X     |\n| Low           | X     |\n| Informational | X     |\n\n**Key findings:**\n1. [Name] — [1 business-impact sentence]\n2. [Name] — [1 business-impact sentence]\n3. [Name] — [1 business-impact sentence]\n\n**Priority recommendation:** [1-2 sentences on what to fix first and why, in language accessible\nto management.]\n```\n\n---\n\n## MCP Integration\n\n### Notion (`mcp__Notion__*`)\n- `notion-create-pages` — create main page and subpages per finding\n- `notion-update-page` — update pages with additional evidence after review\n- `notion-create-comment` — add review observations\n\n---\n\n## Operational Notes\n\n- **Completeness before publishing**: never publish the report without both reviews completed\n- **Evidence required**: every Critical\u002FHigh finding must have at least 1 screenshot or documented PoC\n- **CVSS adjusted to context**: the base score is a reference — adjust PR, AC and S based on the actual case\n- **Combined language**: in `combined` mode, each finding opens with 1 business-language sentence before technical details\n- **Confidentiality**: the report is a confidential document delivered to the client — credentials, hashes and sensitive data obtained during the test are included as proof of exploitation; the client is responsible for secure handling of the document\n","## Architecture\n\nThis skill is Claude-driven. It reads output directories from prior skills, organizes all confirmed\nfindings, writes the full report in the correct format, reviews it twice, and publishes to Notion.\n\n```\nInput directories (any combination):\n  $RECON_OUT    — web-recon output (nuclei findings, live hosts, JS secrets, CMS results)\n  $EXPLOIT_OUT  — web-exploitation output (sqli\u002F, xss\u002F, lfi\u002F, ssrf\u002F, auth\u002F, findings\u002F)\n  $POSTEX_OUT   — web-postexploitation output (if applicable)\n  $EVIDENCE_DIR — screenshots directory (gowitness\u002F, manual captures)\n```\n\n---\n\n## Initial Setup\n\n```bash\nTARGET=\"https:\u002F\u002Ftarget.com\"\nDOMAIN=\"target.com\"\nCLIENT=\"Client Company Name\"\nENGAGEMENT=\"Web Application Penetration Test\"\nTESTER=\"[Your Name \u002F Company]\"\nDATE=\"$(date +%Y-%m-%d)\"\n\nRECON_OUT=\"$(pwd)\u002Ftarget\"\nEXPLOIT_OUT=\"$(pwd)\u002Ftarget-exploit\"\nPOSTEX_OUT=\"$(pwd)\u002Ftarget-postex\"       # leave empty if not applicable\nEVIDENCE_DIR=\"$(pwd)\u002Ftarget\u002Fevidence\"\n\n# Report mode — default: combined (recommended)\nREPORT_MODE=\"combined\"  # options: combined | technical | executive\n```\n\nCreate progress tasks with TaskCreate:\n```\n\"PHASE 1 — Finding Triage & Consolidation\"\n\"PHASE 2 — Evidence Collection & Organization\"\n\"PHASE 3 — Report Writing\"\n\"PHASE 4 — Review #1 (completeness and technical accuracy)\"\n\"PHASE 5 — Review #2 (clarity, language, formatting)\"\n\"PHASE 6 — Notion Publication\"\n```\n\n---\n\n## Report Modes\n\n| Mode | Target audience | What it includes |\n|------|----------------|-----------------|\n| `combined` (default) | Mixed — technical and management | Full technical detail + executive sections with plain-language explanations. Recommended when audience is unknown. |\n| `technical` | Security team, developers | Full technical detail, commands, payloads, reproduction steps |\n| `executive` | C-level, managers, non-technical | Summary, business impact, risk ratings, no raw payloads or commands |\n\n**When mode is not specified: always use `combined`.**\n\n---\n\n## PHASE 1 — Finding Triage & Consolidation\n\nRead all confirmed findings from prior skill outputs:\n\n```bash\n# web-recon findings\ncat \"$RECON_OUT\u002Fvulns\u002Fnuclei.txt\" 2>\u002Fdev\u002Fnull          # nuclei confirmed findings\ncat \"$RECON_OUT\u002Fjs\u002Fsecrets.json\" 2>\u002Fdev\u002Fnull           # JS secrets\ncat \"$RECON_OUT\u002Fvulns\u002Fcms_*.txt\" 2>\u002Fdev\u002Fnull           # CMS vulnerabilities\n\n# web-exploitation findings\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fsqli_confirmed.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fxss_confirmed.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Flfi_confirmed.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fssrf_confirmed.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fopen_redirect.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fjwt_endpoints.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fcookie_issues.txt\" 2>\u002Fdev\u002Fnull\ncat \"$EXPLOIT_OUT\u002Ffindings\u002Fclickjacking.txt\" 2>\u002Fdev\u002Fnull\n\n# List all screenshots\nls \"$EVIDENCE_DIR\u002F\" 2>\u002Fdev\u002Fnull\nls \"$RECON_OUT\u002Fscreenshots\u002F\" 2>\u002Fdev\u002Fnull\n```\n\nBuild a consolidated finding list, grouped by severity:\n```\nCRITICAL  — RCE, SQLi with data extraction, SSRF→cloud metadata, Authentication bypass (full account takeover)\nHIGH      — SQLi (no output), Stored XSS, SSTI, XXE, LFI with sensitive file read, JWT algorithm confusion, File upload\nMEDIUM    — Reflected XSS, IDOR, CSRF on sensitive action, Open redirect, Broken auth (partial), Insecure deserialization\nLOW       — Clickjacking, Missing security headers, Information disclosure, DOM XSS (limited impact)\nINFO      — Best practice recommendations, exposed JS source maps, verbose error messages\n```\n\n---\n\n## PHASE 2 — Evidence Organization\n\n### Screenshot cataloging\n\n```bash\n# List and describe all evidence\nls -lt \"$EVIDENCE_DIR\u002F\" 2>\u002Fdev\u002Fnull\nls -lt \"$RECON_OUT\u002Fscreenshots\u002F\" 2>\u002Fdev\u002Fnull   # gowitness screenshots\n\n# For each finding, identify its evidence file(s)\n# Naming convention: \u003Cseverity>_\u003Cfinding_type>_\u003Cdescription>.\u003Cext>\n# Example:\n#   critical_sqli_login_page_error.png\n#   high_xss_stored_comment_field.png\n#   high_lfi_etc_passwd.png\n```\n\nFor each screenshot\u002Fevidence file, write a 1-2 sentence explanation:\n- **What** is visible in the screenshot\n- **Why** it demonstrates the vulnerability (what makes it a confirmed finding vs. a hypothesis)\n\n### Submitting screenshots to Notion\n\nWhen Notion MCP is available:\n```\n1. Create finding page: mcp__Notion__notion-create-pages\n2. For each screenshot: describe it in the evidence block (Notion does not support direct image upload via API — note the local file path and describe it clearly)\n3. If images need to be hosted: upload to an image hosting service and embed the URL\n```\n\n---\n\n## PHASE 3 — Report Writing\n\n### Document structure\n\n```\nCOVER PAGE\n  - Client name\n  - Engagement type\n  - Date\n  - Tester name \u002F company\n\nEXECUTIVE SUMMARY  (always present, even in technical mode)\n  - Overview of tested scope\n  - Total vulnerabilities by severity (table)\n  - Overall risk score\n  - 3-5 key findings in plain language\n  - General priority recommendation\n\nMETHODOLOGY (technical \u002F combined)\n  - Tools used\n  - Phases executed\n  - Scope limitations and notes\n\nVULNERABILITY SUMMARY (table)\n  | # | Name | Criticality | CVSS | Endpoint | Status |\n  |---|------|-------------|------|----------|--------|\n\nDETAILED FINDINGS (one section per finding)\n\nCONCLUSION\n\nAPPENDIX — Tools and References\n```\n\n---\n\n## Finding Template — Required Format\n\n**Apply this template for every confirmed finding. Write each field as a full paragraph.**\n\n```\n### [CRITICALITY] — [Vulnerability Name]\n\n**Criticality:** Critical \u002F High \u002F Medium \u002F Low \u002F Informational\n**CVSS Score:** X.X (Critical\u002FHigh\u002FMedium\u002FLow)\n**CVSS Vector:** CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H\n**Affected endpoint:** https:\u002F\u002Ftarget.com\u002Fendpoint?param=value\n**Method:** GET \u002F POST \u002F PUT\n**Vulnerable parameter:** param_name\n\n---\n\n**Description**\n\n[1 robust paragraph — minimum 4-6 sentences. Explain WHAT the vulnerability is, HOW it works\ntechnically, WHY this endpoint is vulnerable, and what code\u002Fconfiguration characteristic makes\nit exploitable. In combined\u002Fexecutive mode: open with a plain-language analogy before the\ntechnical detail.]\n\n---\n\n**Impact \u002F Observation**\n\n[1 robust paragraph — minimum 4-6 sentences. Explain WHAT an attacker CAN do by exploiting this\nvulnerability, what data or systems are at risk, what the business impact is (not just technical),\nand how likely real exploitation is. Note if the vulnerability is exploitable remotely, without\nauthentication, or chainable with others.]\n\n---\n\n**Recommendation \u002F Remediation**\n\n[1 robust paragraph — minimum 4-6 sentences. Explain WHAT must be done to fix it, with enough\ntechnical specificity for a developer to implement. Include primary fix + defense in depth\n(multiple control layers). Mention recommended fix timeline based on criticality.]\n\n---\n\n**Evidence**\n\n[For each screenshot or PoC:]\n\n*Figure X — [descriptive title]*\n`File: evidence\u002Fcritical_sqli_login.png`\n\n> [2-4 sentences explaining WHAT is happening in the image: what was sent, what the server\n> returned, what this proves. Language clear enough for a non-technical person to understand\n> that a real problem occurred.]\n\n[If PoC in code:]\n\\`\\`\\`http\nGET \u002Fendpoint?id=1' OR 1=1-- HTTP\u002F1.1\nHost: target.com\n...\n\\`\\`\\`\n*The above demonstrates [what was done]. The server response confirms [what was observed].*\n```\n\n---\n\n## CVSS Reference Table (web findings)\n\nUse these as baseline — adjust based on actual exploitability and scope:\n\n| Vulnerability | CVSS Base | Criticality | Vector |\n|----------------|-----------|-------------|--------|\n| RCE (unauthenticated) | 9.8 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| SQLi (data extraction) | 9.8 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| SSRF → cloud metadata | 9.1 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:C\u002FC:H\u002FI:L\u002FA:N |\n| Auth bypass (full ATO) | 9.8 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| SSTI → RCE | 9.8 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| File upload → RCE | 9.8 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| XXE (file read) | 7.5 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N |\n| LFI (sensitive files) | 7.5 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N |\n| JWT algorithm confusion | 9.1 | Critical | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:N |\n| JWT weak secret | 8.8 | High | AV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:N |\n| Stored XSS | 8.8 | High | AV:N\u002FAC:L\u002FPR:L\u002FUI:R\u002FS:C\u002FC:H\u002FI:H\u002FA:N |\n| IDOR (sensitive data) | 8.1 | High | AV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:N |\n| Insecure deserialization | 8.8 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H |\n| Broken auth (partial) | 7.5 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N |\n| SQLi (blind, no output) | 8.6 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N |\n| SSRF (internal network) | 8.6 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:C\u002FC:H\u002FI:N\u002FA:N |\n| Reflected XSS | 6.1 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:C\u002FC:L\u002FI:L\u002FA:N |\n| CSRF (sensitive action) | 6.5 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:U\u002FC:N\u002FI:H\u002FA:N |\n| Open redirect | 6.1 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:C\u002FC:L\u002FI:L\u002FA:N |\n| CRLF injection | 6.1 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:C\u002FC:L\u002FI:L\u002FA:N |\n| Host header injection | 7.2 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:C\u002FC:L\u002FI:L\u002FA:N |\n| Clickjacking | 4.7 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:C\u002FC:N\u002FI:L\u002FA:N |\n| Missing security headers | 3.1 | Low | AV:N\u002FAC:H\u002FPR:N\u002FUI:R\u002FS:U\u002FC:L\u002FI:N\u002FA:N |\n| Information disclosure | 5.3 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:L\u002FI:N\u002FA:N |\n| Exposed JS source map | 5.3 | Medium | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:L\u002FI:N\u002FA:N |\n| Exposed .git repository | 7.5 | High | AV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N |\n\n> **Adjust CVSS based on context**: if authentication is required (PR:L or PR:H), if the scope changes (S:C vs S:U), or if chaining is needed (AC:H).\n\n---\n\n## PHASE 4 & 5 — Double Review\n\n**Review #1 — Technical accuracy:**\n- Every finding has: name, criticality, CVSS score + vector, affected endpoint, description, impact, recommendation, evidence\n- CVSS scores are consistent with the actual exploitability demonstrated\n- Evidence correctly described — screenshots match their finding\n- Reproduction steps are accurate and testable\n- No finding is listed without confirmed exploitation evidence\n\n**Review #2 — Language, clarity, and formatting:**\n- All text is clear and consistent in language and style\n- Executive sections use no jargon without explanation\n- No spelling or grammatical errors\n- Paragraphs are 4-6 sentences minimum and substantive\n- Table of findings is complete and sorted by CVSS (highest first)\n- All evidence files are correctly referenced (file paths or Notion links)\n\n**After both reviews:** explicitly confirm: *\"Report reviewed twice. No pending items identified.\"*\n\n---\n\n## PHASE 6 — Notion Publication\n\nWhen `mcp__Notion__*` is available:\n\n```\n1. Create parent page: mcp__Notion__notion-create-pages\n   Title: \"Pentest Report — [CLIENT] — [DATE]\"\n   Content: Executive Summary + Finding Summary Table\n\n2. For each finding (Critical\u002FHigh\u002FMedium):\n   Create subpage: mcp__Notion__notion-create-pages (child of parent)\n   Title: \"[CVSS] [CRITICALITY] — [Vulnerability Name]\"\n   Content: Full finding in template format\n\n3. Create appendix page with:\n   - Tools used\n   - Scope and methodology\n   - Raw output references (file paths)\n```\n\n---\n\n## Executive Summary Template\n\n```\n## Executive Summary\n\nThis report presents the results of the penetration test conducted against [TARGET] from\n[START_DATE] to [END_DATE], performed by [TESTER]. The objective of the engagement was to\nidentify security vulnerabilities in the web application and assess the potential impact of\ntheir exploitation.\n\n**Assessed scope:** [list of in-scope URLs\u002Fendpoints]\n\n**Overall result:** X vulnerabilities were identified: Y critical, Z high, W medium, and V low\nseverity. [1-2 sentences summarizing the most severe finding and its business impact.]\n\n**Severity distribution:**\n| Severity      | Count |\n|---------------|-------|\n| Critical      | X     |\n| High          | X     |\n| Medium        | X     |\n| Low           | X     |\n| Informational | X     |\n\n**Key findings:**\n1. [Name] — [1 business-impact sentence]\n2. [Name] — [1 business-impact sentence]\n3. [Name] — [1 business-impact sentence]\n\n**Priority recommendation:** [1-2 sentences on what to fix first and why, in language accessible\nto management.]\n```\n\n---\n\n## MCP Integration\n\n### Notion (`mcp__Notion__*`)\n- `notion-create-pages` — create main page and subpages per finding\n- `notion-update-page` — update pages with additional evidence after review\n- `notion-create-comment` — add review observations\n\n---\n\n## Operational Notes\n\n- **Completeness before publishing**: never publish the report without both reviews completed\n- **Evidence required**: every Critical\u002FHigh finding must have at least 1 screenshot or documented PoC\n- **CVSS adjusted to context**: the base score is a reference — adjust PR, AC and S based on the actual case\n- **Combined language**: in `combined` mode, each finding opens with 1 business-language sentence before technical details\n- **Confidentiality**: the report is a confidential document delivered to the client — credentials, hashes and sensitive data obtained during the test are included as proof of exploitation; the client is responsible for secure handling of the document\n",{},"main","19a54ac988e9929160334271f5c1924ddd9b227e","_modules\u002Fweb-report",19,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill","https:\u002F\u002Fgithub.com\u002Falicewe1","写一些自己用得上的工具，能自动化就绝不手动 · 自动化 \u002F 工程效率 \u002F Agent 技能生态 · 保持好奇，持续构建","2026-09-30 00:41:20",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add alicewe1\u002Falice_skill --skill web-report",{"tool":37,"command":38},"bunx","bunx skills add alicewe1\u002Falice_skill --skill web-report",{"tool":40,"command":41},"pnpm","pnpm dlx skills add alicewe1\u002Falice_skill --skill web-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fweb-report\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7DBMD9P6R27SWQCW5HYVWG0","alice","Alice 六类技能总路由。用户输入 Alice 或要求查看 Alice 技能菜单时，严格输出固定菜单；输入攻\u002F防模式、六类入口或直接描述任务时，按类别→领域→模块渐进路由。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Faliceskill\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7DBM8X5M7YXPYBVFMWF8HRC","alice-reverse","逆向分析渐进路由（二进制 \u002F 移动端 \u002F 协议 \u002F 取证 \u002F 保护机制 \u002F 运行时观测）。触发词：二进制\u002F移动端\u002F反编译\u002FFrida\u002FIDA\u002FGhidra\u002FPE\u002FELF\u002FAPK\u002F协议\u002F取证；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-reverse\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7DBM630E2YKQP29194TT7HC","alice-pentest","web安全渐进路由（Web \u002F API \u002F 资产发现 \u002F 漏洞验证 \u002F 云与网络安全）。触发词：Web\u002FAPI\u002F资产发现\u002F端口\u002F漏洞验证\u002F云与网络安全；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-pentest\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7DBM20M2VDYV5D3MYDGBTQX","alice-game","游戏攻防渐进路由（游戏客户端 \u002F 内存 \u002F 图形 \u002F 反作弊 \u002F 安全研究）。触发词：游戏客户端\u002F内存\u002F图形\u002F偏移\u002F反作弊\u002F模拟器\u002F覆盖层；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-game\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7DBKXVEKB8931MZG23VACFN","alice-crack","卡密授权渐进路由（卡密 \u002F 激活 \u002F 授权验证 \u002F 许可证管理 \u002F 本地授权分析）。触发词：卡密\u002F激活\u002F授权验证\u002Flicense\u002F机器码\u002F试用状态；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-crack\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7DBKTMT90MGV2WP8K73TMQD","alice-assist","技能指令渐进路由（技能路由 \u002F 评分 \u002F 吸收 \u002F 迁移 \u002F 自动化 \u002F 文档与平台集成）。触发词：技能创建\u002F吸收\u002F评分\u002F迁移\u002F自动化\u002F文档\u002F平台指令；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-assist\u002FSKILL.md",[],[]]