[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PCQ0PV2JQBPMZHNGTKHADH":3,"skill-same:01M6PCQ0PV2JQBPMZHNGTKHADH":79},{"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":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":34,"commitSha":60,"skillDirectory":61,"forksCount":13,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6PCQ0PV2JQBPMZHNGTKHADH","redteam-report-template",null,"Client-facing red-team deliverable format","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\u002Fredteam-report-template\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"template","redteam report template","report","process","github","upstream","main","community","guidance","tooling","engagement","only","security","safe","format","team","Enterprise","red-team","https","license","2026-11-10 10:12:30",false,"---\nname: redteam-report-template\ndescription: Client-facing red-team deliverable format\ncategory: security\nrisk: safe\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: Process guidance; no tooling required. Docs-only; upstream templates\n  not bundled.\nsources: authorized-engagement-deliverable, enterprise-redteam-report-conventions\nreport_count: 1\n---\n\n## When to use\n\nUse this skill for **client-deliverable** reports:\n- External red-team engagements with a signed SOW\n- Pentest reports going to a CISO \u002F IT-Sec team (not a triager)\n- Findings that will be reviewed by both technical and non-technical stakeholders\n- Reports that need DOCX\u002FPDF output (not just markdown \u002F platform UI)\n\nDo NOT use for:\n- Bug-bounty platform submissions (use `report-writing` \u002F `bugcrowd-reporting` instead)\n- Quick proof-of-concept memos\n- Internal team writeups\n\n---\n\n## The 6-section format per finding\n\nThis is the canonical structure each finding follows:\n\n```markdown\n## Finding F##: \u003Cdescriptive title>\n\n**Severity:** Critical \u002F High \u002F Medium \u002F Low \u002F Informational\n**Status:** Confirmed \u002F Patched mid-engagement \u002F Suspected (1 signal)\n**CVSS 3.1:** \u003Cscore> (\u003Cvector>)\n**Affected Asset:** \u003CURL \u002F IP \u002F app name>\n\n### 1. Subject\n\u003COne-line statement of the issue. Plain English, no jargon.>\n\n### 2. Observations\n\u003CBulleted list of what was observed during testing. Concrete facts only — no interpretation yet.>\n- \u003CObservation 1>\n- \u003CObservation 2>\n- ...\n\n### 3. Description\n\u003CTechnical explanation of the vulnerability. 2-4 paragraphs. Reader should understand WHY the observations indicate a vulnerability, what the underlying flaw is.>\n\n### 4. Impact\n\u003CWhat an attacker could achieve. Concrete attacker outcomes, NOT generic CIA triad statements. Tie to the client's business — money, data, reputation, regulatory exposure.>\n\n### 5. Recommendation\n\u003CSpecific, actionable remediation. Vendor patch, configuration change, code-level fix. Avoid \"implement security best practices\" — say what specifically.>\n\n### 6. Proof of Concept (PoC)\n\u003CSteps to reproduce, numbered. Include the exact HTTP requests, payloads, tools used.>\n\n**Step 1:** \u003Caction>\n```http\n\u003Cfull HTTP request or curl one-liner>\n```\n\n**Step 2:** \u003Caction>\n```\n\u003Cresponse excerpt>\n```\n\n**Screenshot:**\n![F##_descriptive_name] (screenshots\u002FF##_descriptive_name.png)\n```\n\n---\n\n## Severity & status disciplines\n\n### Severity table (client-facing — different from CVSS-only)\n\n| Severity | Business definition | CVSS rough range |\n|---|---|---|\n| Critical | Direct revenue\u002Fdata loss without prerequisites | 9.0-10.0 |\n| High | Full account\u002Fsystem takeover with limited prerequisites | 7.0-8.9 |\n| Medium | Significant data exposure or partial compromise | 4.0-6.9 |\n| Low | Information disclosure with limited exploitation path | 0.1-3.9 |\n| Informational | Hygiene finding, no immediate exploit | N\u002FA |\n\n### Status field (red-team-specific)\n\nThis is the field that distinguishes red-team deliverables from bug-bounty reports. Use one of:\n\n- **Confirmed** — reproduced multiple times, with full PoC\n- **Confirmed; patched mid-engagement** — was reproducible, client patched during the test window (still ship the finding — see `mid-engagement-ir-detection`)\n- **Confirmed; partially reproducible** — works but needs specific conditions\n- **Suspected (1 signal)** — single indicator, not confirmed (rare — usually drop)\n- **Out-of-band** — finding from passive recon, not actively tested\n\n---\n\n## Mistakes to avoid (from authorized-engagement)\n\n### 1. Don't retract findings that stopped reproducing\nIf a finding was confirmed and then stopped working, that is almost always a CLIENT PATCH, not a finding-was-false. The correct response is \"Confirmed; patched mid-engagement\" with timestamps showing when it broke. See `mid-engagement-ir-detection`.\n\n### 2. Don't hedge in the Impact section\nBad: \"An attacker could potentially be able to access user data, which may lead to...\"\nGood: \"An attacker reads any user's profile data. Demonstrated on test user `victim@target.com` at 14:22 IST.\"\n\n### 3. Don't generic-CIA the impact\nBad: \"Loss of confidentiality and integrity of customer data\"\nGood: \"Read access to 247,000 customer records including PAN cards, addresses, GST numbers. India DPDPA Section 33 mandates 72-hour breach disclosure to DPB.\"\n\n### 4. Don't list every recon finding as a finding\nRecon notes (subdomains found, ports open, technologies fingerprinted) belong in a separate **Recon \u002F Attack Surface** appendix, not the findings list. A finding must have an attacker-attainable outcome.\n\n### 5. Don't bury the PoC\nEach finding MUST have reproducible steps. The PoC section is what proves the finding to a skeptical reader. If you can't write the PoC clearly, the finding probably isn't ready to ship.\n\n---\n\n## Document-level structure\n\n```\n1. Executive Summary (1 page, non-technical)\n   - Engagement overview (dates, scope)\n   - Risk posture summary (heat-map: \u003CX critical, Y high, Z medium...>)\n   - Top 3 strategic recommendations\n   - Comparison to industry baseline (optional)\n\n2. Engagement Details\n   - Scope (in-scope, out-of-scope, exclusions)\n   - Methodology (recon → exploit → reporting; or align with PTES \u002F OSSTMM)\n   - Tools used\n   - Timeline (start \u002F end \u002F key milestones)\n   - Team\n\n3. Risk Summary Table\n   | F# | Title | Severity | Status |\n   |----|-------|----------|--------|\n   | F01 | ... | Critical | Confirmed |\n   ...\n\n4. Findings (one per ## section, in severity order — Critical first)\n\n5. Attack Surface \u002F Recon Appendix\n   - Subdomains discovered\n   - Open ports \u002F services\n   - Technology fingerprints\n   - APKs found\n   - Credentials in breach corpora (count + sample only — redact)\n   - Identity-fabric map (IdP, MFA posture)\n\n6. Indicators of Compromise (IoCs)\n   - Source IPs used during testing (so SOC can correlate)\n   - User-Agent strings\n   - Test accounts created\n   - Files uploaded (with cleanup status)\n\n7. Cleanup Statement\n   - Confirmation that all test artifacts (accounts, uploads, persistence) were removed\n   - Outstanding cleanup items requiring client action\n\n8. Appendices (raw output, screenshots index, full target list)\n```\n\n---\n\n## DOCX generation pipeline (markdown → docx with embedded images)\n\n```bash\n# Prerequisite: pandoc installed\nbrew install pandoc\n\n# Convert\npandoc REPORT_FINAL.md \\\n  -o REPORT_FINAL.docx \\\n  --resource-path=engagement_log\u002Fpoc \\\n  --reference-doc=~\u002F.claude\u002Fskills\u002Fredteam-report-template\u002Ftemplates\u002Freference.docx \\\n  --toc \\\n  --toc-depth=2 \\\n  --highlight-style=tango\n\n# Verify image count\npython3 -c \"\nfrom docx import Document\nd = Document('REPORT_FINAL.docx')\nimgs = [r for r in d.part.rels.values() if 'image' in r.target_ref]\nprint(f'Embedded images: {len(imgs)}')\nprint(f'Paragraphs: {len(d.paragraphs)}')\nprint(f'Headings: {sum(1 for p in d.paragraphs if p.style.name.startswith(\\\"Heading\\\"))}')\n\"\n```\n\n### Image filename convention\n\n```\nscreenshots\u002FF\u003CNN>_\u003Cdescriptive>.png\n\nExamples:\nF01_locked_accounts.png\nF02a_saml_landing.png\nF02b_saml_ca_block_page.png\nF03_sqli_timing_chart.png\nF15_saml_metadata.png\n```\n\nVariants get letter suffixes (F02a, F02b). Always zero-pad finding number.\n\n---\n\n## Writing tone — for client deliverables\n\n| Section | Tone |\n|---|---|\n| Subject | Plain English, jargon-free, 1 line |\n| Observations | Bulleted facts, past tense (\"observed that...\") |\n| Description | Technical but accessible; assume CISO reader |\n| Impact | Business-translated; tie to revenue\u002Fregulation |\n| Recommendation | Imperative, specific, actionable |\n| PoC | Operator-level technical; copy-pasteable |\n\n**Always:**\n- Use past tense for observations (\"The endpoint returned a 200 status code\")\n- Use present tense for descriptions of the flaw (\"The application does not validate...\")\n- Use imperative for recommendations (\"Apply patch ... by ...\")\n- Number reproduction steps; never \"first... then... also...\"\n\n**Never:**\n- \"Could potentially\" — prove it or drop it\n- \"It might be possible\" — same\n- \"We recommend implementing security best practices\" — say which one specifically\n- \"The application is vulnerable to...\" without saying what specifically\n\n---\n\n## Audience translation — same finding, different framing\n\nExample: hardcoded JWT in APK\n\n| Section | Technical framing | CISO framing | Board framing |\n|---|---|---|---|\n| Impact | \"JWT signing key extracted from APK enables forging admin tokens\" | \"Anyone with the customer-facing mobile app can read any customer's invoice\" | \"A leaked secret in our mobile app lets attackers impersonate users\" |\n\nThe same finding's Impact paragraph should cover both ends — start with the business outcome, then drop into technical detail.\n\n---\n\n## Findings that are sometimes wrongly excluded\n\nRed-team deliverables should include — not just bug-bounty payable bugs:\n\n- **Information disclosure that helps attack mapping** (CodeIgniter debug toolbar leaking routes, version banners on appliances) — Medium\n- **User enumeration** (Microsoft OneDrive 302 vs 404 differential) — Medium\n- **Pre-existing security state observations** (247 accounts already locked by external attacker; weak password policies) — Informational with stakeholder relevance\n- **Defensive observations** (SOC patched our SQLi within 30 min — evidence of working detection) — Informational\u002Fpositive\n- **Sister-app pattern issues** (same code template across 7 apps) — Medium (multiplied blast radius)\n\nBug bounty would reject most of these. Red-team deliverables embrace them — the client paid for the assessment to know.\n\n---\n\n## Mid-engagement events to document\n\nBeyond findings themselves, the deliverable should include:\n\n- Detected SOC responses (timestamps when defenses kicked in)\n- Concurrent external attacker activity (if any was observed)\n- Findings the client patched during the engagement (with PoC pre-patch as evidence)\n- Tooling failures (e.g., MCP timeout, CAPTCHA not solvable) — these affect what was\u002Fwasn't testable\n\nEach gives the client context about their real-world detection capability, which often matters more than the findings themselves.\n\n---\n\n## Template library (where to put canned text)\n\nMaintain reusable boilerplate in:\n```\n~\u002F.claude\u002Fskills\u002Fredteam-report-template\u002Ftemplates\u002F\n    executive_summary.md      # Reusable exec summary skeleton\n    methodology.md            # Standard methodology section\n    cleanup_statement.md      # Standard cleanup language\n    reference.docx            # Pandoc style template (fonts, headings, colors)\n    cover.docx                # Cover page template\n```\n\nDon't write these from scratch each engagement; clone and customize.\n\n---\n\n## Quality checks before delivery\n\nPre-delivery checklist:\n\n- [ ] Every finding has all 6 sections populated (no \"TBD\")\n- [ ] Every finding has at least one screenshot or HTTP-level evidence\n- [ ] Every PoC includes redactions for client PII (mask emails, phone numbers, IDs)\n- [ ] Every screenshot is referenced in the MD with a relative path that resolves\n- [ ] DOCX render check — image count matches MD reference count\n- [ ] Severity ordering: Critical findings first, then High, etc.\n- [ ] Executive summary is updated to match final findings (count, themes)\n- [ ] Cleanup statement explicitly says what was created and what was removed\n- [ ] IoC section enables the SOC to reconstruct what they saw\n- [ ] Spell-check (especially client company name, product names)\n- [ ] All tool versions noted in methodology\n- [ ] Status field set correctly on every finding (especially patched-mid-engagement)\n\n---\n\n## Bridge to neighboring skills\n\n- `report-writing` — bug-bounty platform reports (different format, different audience)\n- `redteam-mindset` — informs what counts as a finding worth shipping\n- `mid-engagement-ir-detection` — informs the \"patched mid-engagement\" status pattern\n- `evidence-hygiene` — informs screenshot redaction discipline\n- `m365-entra-attack`, `enterprise-vpn-attack`, etc. — each provides finding-templates specific to its attack surface\n\n---\n\n## Anti-patterns\n\n- **DO NOT** write a 50-page report for 3 findings — pad-by-page erodes credibility\n- **DO NOT** use the same severity for everything — calibrate\n- **DO NOT** copy-paste OWASP top-10 boilerplate into Description sections\n- **DO NOT** include findings without PoCs — they read as speculative\n- **DO NOT** skip the Recommendation section's specificity — \"patch and review\" doesn't help\n- **DO NOT** mix bug-bounty CVSS scoring with red-team severity unthinkingly — context differs (e.g., a Medium on a CVSS basis can be Critical for the client if it touches a regulated dataset)\n\n---\n\n## Real engagement metric (authorized-engagement)\n\nFor calibration:\n- 14 findings shipped (2 Critical, 4 High, 5 Medium, 3 Low\u002FInfo)\n- 18 screenshots embedded\n- 52,737 bytes markdown \u002F 2,262,484 bytes DOCX\n- 414 paragraphs, 123 headings in DOCX\n- 16 inline images (2 were inline in MD-only edge cases)\n- Time-to-deliverable: ~6 hours after engagement close for first draft\n\nThese numbers are typical for a 1-week external red-team engagement on a mid-size enterprise. Scale down for short tests, up for full purple-team exercises.\n\n---\n\n## Related Skills & Chains\n\n- **`triage-validation`** — This template ingests findings that have ALREADY passed the 7-Question Gate. Engagement flow: every finding through `triage-validation` first → only validated findings → `redteam-report-template` packaging. Skipping triage produces a deliverable padded with informational noise that erodes client trust.\n- **`evidence-hygiene`** — The DOCX with 16 embedded screenshots only works if evidence was captured systematically throughout the engagement. Engagement flow: `evidence-hygiene` discipline at session start → timestamped, organized screenshot folder → `redteam-report-template` consumes that folder to populate Evidence blocks.\n- **`redteam-mindset`** — The Subject \u002F Observations \u002F Description \u002F Impact \u002F Recommendation \u002F PoC structure assumes the operator already thinks like a red-teamer (impact-first, blast-radius framing). Engagement flow: `redteam-mindset` loaded at engagement start → findings collected with red-team framing baked in → `redteam-report-template` produces deliverable without rewriting every Impact section.\n- **`mid-engagement-ir-detection`** — Defensive-action findings (SOC patches mid-test, new IPS rules deployed, account lockouts triggered by external attacker) are first-class findings in red-team deliverables. Engagement flow: `mid-engagement-ir-detection` captures behavior-change events → each becomes its own Subject in the deliverable, framed as \"client capability observation\" not as \"bug we missed.\"\n- **`report-writing`** + **`bugcrowd-reporting`** — Bug-bounty platform reports use DIFFERENT structure (one finding per submission, platform-specific severity scoring, OOS-clause counters). Engagement flow: if engagement mode is `bug-bounty` per project memory → use `report-writing` \u002F `bugcrowd-reporting` instead. This template is ONLY for external red-team \u002F enterprise client deliverables.\n\n## Limitations\n\n- Process guidance only; it does not authorize probing or exploitation — those steps need their own authorized skill and confirmation gate.\n- Docs-only import: upstream templates, commands, and research assets are not bundled.\n\n### Example\n\n```markdown\nApply this skill's checklist to the current engagement notes and report gaps.\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","## When to use\n\nUse this skill for **client-deliverable** reports:\n- External red-team engagements with a signed SOW\n- Pentest reports going to a CISO \u002F IT-Sec team (not a triager)\n- Findings that will be reviewed by both technical and non-technical stakeholders\n- Reports that need DOCX\u002FPDF output (not just markdown \u002F platform UI)\n\nDo NOT use for:\n- Bug-bounty platform submissions (use `report-writing` \u002F `bugcrowd-reporting` instead)\n- Quick proof-of-concept memos\n- Internal team writeups\n\n---\n\n## The 6-section format per finding\n\nThis is the canonical structure each finding follows:\n\n```markdown\n## Finding F##: \u003Cdescriptive title>\n\n**Severity:** Critical \u002F High \u002F Medium \u002F Low \u002F Informational\n**Status:** Confirmed \u002F Patched mid-engagement \u002F Suspected (1 signal)\n**CVSS 3.1:** \u003Cscore> (\u003Cvector>)\n**Affected Asset:** \u003CURL \u002F IP \u002F app name>\n\n### 1. Subject\n\u003COne-line statement of the issue. Plain English, no jargon.>\n\n### 2. Observations\n\u003CBulleted list of what was observed during testing. Concrete facts only — no interpretation yet.>\n- \u003CObservation 1>\n- \u003CObservation 2>\n- ...\n\n### 3. Description\n\u003CTechnical explanation of the vulnerability. 2-4 paragraphs. Reader should understand WHY the observations indicate a vulnerability, what the underlying flaw is.>\n\n### 4. Impact\n\u003CWhat an attacker could achieve. Concrete attacker outcomes, NOT generic CIA triad statements. Tie to the client's business — money, data, reputation, regulatory exposure.>\n\n### 5. Recommendation\n\u003CSpecific, actionable remediation. Vendor patch, configuration change, code-level fix. Avoid \"implement security best practices\" — say what specifically.>\n\n### 6. Proof of Concept (PoC)\n\u003CSteps to reproduce, numbered. Include the exact HTTP requests, payloads, tools used.>\n\n**Step 1:** \u003Caction>\n```http\n\u003Cfull HTTP request or curl one-liner>\n```\n\n**Step 2:** \u003Caction>\n```\n\u003Cresponse excerpt>\n```\n\n**Screenshot:**\n![F##_descriptive_name] (screenshots\u002FF##_descriptive_name.png)\n```\n\n---\n\n## Severity & status disciplines\n\n### Severity table (client-facing — different from CVSS-only)\n\n| Severity | Business definition | CVSS rough range |\n|---|---|---|\n| Critical | Direct revenue\u002Fdata loss without prerequisites | 9.0-10.0 |\n| High | Full account\u002Fsystem takeover with limited prerequisites | 7.0-8.9 |\n| Medium | Significant data exposure or partial compromise | 4.0-6.9 |\n| Low | Information disclosure with limited exploitation path | 0.1-3.9 |\n| Informational | Hygiene finding, no immediate exploit | N\u002FA |\n\n### Status field (red-team-specific)\n\nThis is the field that distinguishes red-team deliverables from bug-bounty reports. Use one of:\n\n- **Confirmed** — reproduced multiple times, with full PoC\n- **Confirmed; patched mid-engagement** — was reproducible, client patched during the test window (still ship the finding — see `mid-engagement-ir-detection`)\n- **Confirmed; partially reproducible** — works but needs specific conditions\n- **Suspected (1 signal)** — single indicator, not confirmed (rare — usually drop)\n- **Out-of-band** — finding from passive recon, not actively tested\n\n---\n\n## Mistakes to avoid (from authorized-engagement)\n\n### 1. Don't retract findings that stopped reproducing\nIf a finding was confirmed and then stopped working, that is almost always a CLIENT PATCH, not a finding-was-false. The correct response is \"Confirmed; patched mid-engagement\" with timestamps showing when it broke. See `mid-engagement-ir-detection`.\n\n### 2. Don't hedge in the Impact section\nBad: \"An attacker could potentially be able to access user data, which may lead to...\"\nGood: \"An attacker reads any user's profile data. Demonstrated on test user `victim@target.com` at 14:22 IST.\"\n\n### 3. Don't generic-CIA the impact\nBad: \"Loss of confidentiality and integrity of customer data\"\nGood: \"Read access to 247,000 customer records including PAN cards, addresses, GST numbers. India DPDPA Section 33 mandates 72-hour breach disclosure to DPB.\"\n\n### 4. Don't list every recon finding as a finding\nRecon notes (subdomains found, ports open, technologies fingerprinted) belong in a separate **Recon \u002F Attack Surface** appendix, not the findings list. A finding must have an attacker-attainable outcome.\n\n### 5. Don't bury the PoC\nEach finding MUST have reproducible steps. The PoC section is what proves the finding to a skeptical reader. If you can't write the PoC clearly, the finding probably isn't ready to ship.\n\n---\n\n## Document-level structure\n\n```\n1. Executive Summary (1 page, non-technical)\n   - Engagement overview (dates, scope)\n   - Risk posture summary (heat-map: \u003CX critical, Y high, Z medium...>)\n   - Top 3 strategic recommendations\n   - Comparison to industry baseline (optional)\n\n2. Engagement Details\n   - Scope (in-scope, out-of-scope, exclusions)\n   - Methodology (recon → exploit → reporting; or align with PTES \u002F OSSTMM)\n   - Tools used\n   - Timeline (start \u002F end \u002F key milestones)\n   - Team\n\n3. Risk Summary Table\n   | F# | Title | Severity | Status |\n   |----|-------|----------|--------|\n   | F01 | ... | Critical | Confirmed |\n   ...\n\n4. Findings (one per ## section, in severity order — Critical first)\n\n5. Attack Surface \u002F Recon Appendix\n   - Subdomains discovered\n   - Open ports \u002F services\n   - Technology fingerprints\n   - APKs found\n   - Credentials in breach corpora (count + sample only — redact)\n   - Identity-fabric map (IdP, MFA posture)\n\n6. Indicators of Compromise (IoCs)\n   - Source IPs used during testing (so SOC can correlate)\n   - User-Agent strings\n   - Test accounts created\n   - Files uploaded (with cleanup status)\n\n7. Cleanup Statement\n   - Confirmation that all test artifacts (accounts, uploads, persistence) were removed\n   - Outstanding cleanup items requiring client action\n\n8. Appendices (raw output, screenshots index, full target list)\n```\n\n---\n\n## DOCX generation pipeline (markdown → docx with embedded images)\n\n```bash\n# Prerequisite: pandoc installed\nbrew install pandoc\n\n# Convert\npandoc REPORT_FINAL.md \\\n  -o REPORT_FINAL.docx \\\n  --resource-path=engagement_log\u002Fpoc \\\n  --reference-doc=~\u002F.claude\u002Fskills\u002Fredteam-report-template\u002Ftemplates\u002Freference.docx \\\n  --toc \\\n  --toc-depth=2 \\\n  --highlight-style=tango\n\n# Verify image count\npython3 -c \"\nfrom docx import Document\nd = Document('REPORT_FINAL.docx')\nimgs = [r for r in d.part.rels.values() if 'image' in r.target_ref]\nprint(f'Embedded images: {len(imgs)}')\nprint(f'Paragraphs: {len(d.paragraphs)}')\nprint(f'Headings: {sum(1 for p in d.paragraphs if p.style.name.startswith(\\\"Heading\\\"))}')\n\"\n```\n\n### Image filename convention\n\n```\nscreenshots\u002FF\u003CNN>_\u003Cdescriptive>.png\n\nExamples:\nF01_locked_accounts.png\nF02a_saml_landing.png\nF02b_saml_ca_block_page.png\nF03_sqli_timing_chart.png\nF15_saml_metadata.png\n```\n\nVariants get letter suffixes (F02a, F02b). Always zero-pad finding number.\n\n---\n\n## Writing tone — for client deliverables\n\n| Section | Tone |\n|---|---|\n| Subject | Plain English, jargon-free, 1 line |\n| Observations | Bulleted facts, past tense (\"observed that...\") |\n| Description | Technical but accessible; assume CISO reader |\n| Impact | Business-translated; tie to revenue\u002Fregulation |\n| Recommendation | Imperative, specific, actionable |\n| PoC | Operator-level technical; copy-pasteable |\n\n**Always:**\n- Use past tense for observations (\"The endpoint returned a 200 status code\")\n- Use present tense for descriptions of the flaw (\"The application does not validate...\")\n- Use imperative for recommendations (\"Apply patch ... by ...\")\n- Number reproduction steps; never \"first... then... also...\"\n\n**Never:**\n- \"Could potentially\" — prove it or drop it\n- \"It might be possible\" — same\n- \"We recommend implementing security best practices\" — say which one specifically\n- \"The application is vulnerable to...\" without saying what specifically\n\n---\n\n## Audience translation — same finding, different framing\n\nExample: hardcoded JWT in APK\n\n| Section | Technical framing | CISO framing | Board framing |\n|---|---|---|---|\n| Impact | \"JWT signing key extracted from APK enables forging admin tokens\" | \"Anyone with the customer-facing mobile app can read any customer's invoice\" | \"A leaked secret in our mobile app lets attackers impersonate users\" |\n\nThe same finding's Impact paragraph should cover both ends — start with the business outcome, then drop into technical detail.\n\n---\n\n## Findings that are sometimes wrongly excluded\n\nRed-team deliverables should include — not just bug-bounty payable bugs:\n\n- **Information disclosure that helps attack mapping** (CodeIgniter debug toolbar leaking routes, version banners on appliances) — Medium\n- **User enumeration** (Microsoft OneDrive 302 vs 404 differential) — Medium\n- **Pre-existing security state observations** (247 accounts already locked by external attacker; weak password policies) — Informational with stakeholder relevance\n- **Defensive observations** (SOC patched our SQLi within 30 min — evidence of working detection) — Informational\u002Fpositive\n- **Sister-app pattern issues** (same code template across 7 apps) — Medium (multiplied blast radius)\n\nBug bounty would reject most of these. Red-team deliverables embrace them — the client paid for the assessment to know.\n\n---\n\n## Mid-engagement events to document\n\nBeyond findings themselves, the deliverable should include:\n\n- Detected SOC responses (timestamps when defenses kicked in)\n- Concurrent external attacker activity (if any was observed)\n- Findings the client patched during the engagement (with PoC pre-patch as evidence)\n- Tooling failures (e.g., MCP timeout, CAPTCHA not solvable) — these affect what was\u002Fwasn't testable\n\nEach gives the client context about their real-world detection capability, which often matters more than the findings themselves.\n\n---\n\n## Template library (where to put canned text)\n\nMaintain reusable boilerplate in:\n```\n~\u002F.claude\u002Fskills\u002Fredteam-report-template\u002Ftemplates\u002F\n    executive_summary.md      # Reusable exec summary skeleton\n    methodology.md            # Standard methodology section\n    cleanup_statement.md      # Standard cleanup language\n    reference.docx            # Pandoc style template (fonts, headings, colors)\n    cover.docx                # Cover page template\n```\n\nDon't write these from scratch each engagement; clone and customize.\n\n---\n\n## Quality checks before delivery\n\nPre-delivery checklist:\n\n- [ ] Every finding has all 6 sections populated (no \"TBD\")\n- [ ] Every finding has at least one screenshot or HTTP-level evidence\n- [ ] Every PoC includes redactions for client PII (mask emails, phone numbers, IDs)\n- [ ] Every screenshot is referenced in the MD with a relative path that resolves\n- [ ] DOCX render check — image count matches MD reference count\n- [ ] Severity ordering: Critical findings first, then High, etc.\n- [ ] Executive summary is updated to match final findings (count, themes)\n- [ ] Cleanup statement explicitly says what was created and what was removed\n- [ ] IoC section enables the SOC to reconstruct what they saw\n- [ ] Spell-check (especially client company name, product names)\n- [ ] All tool versions noted in methodology\n- [ ] Status field set correctly on every finding (especially patched-mid-engagement)\n\n---\n\n## Bridge to neighboring skills\n\n- `report-writing` — bug-bounty platform reports (different format, different audience)\n- `redteam-mindset` — informs what counts as a finding worth shipping\n- `mid-engagement-ir-detection` — informs the \"patched mid-engagement\" status pattern\n- `evidence-hygiene` — informs screenshot redaction discipline\n- `m365-entra-attack`, `enterprise-vpn-attack`, etc. — each provides finding-templates specific to its attack surface\n\n---\n\n## Anti-patterns\n\n- **DO NOT** write a 50-page report for 3 findings — pad-by-page erodes credibility\n- **DO NOT** use the same severity for everything — calibrate\n- **DO NOT** copy-paste OWASP top-10 boilerplate into Description sections\n- **DO NOT** include findings without PoCs — they read as speculative\n- **DO NOT** skip the Recommendation section's specificity — \"patch and review\" doesn't help\n- **DO NOT** mix bug-bounty CVSS scoring with red-team severity unthinkingly — context differs (e.g., a Medium on a CVSS basis can be Critical for the client if it touches a regulated dataset)\n\n---\n\n## Real engagement metric (authorized-engagement)\n\nFor calibration:\n- 14 findings shipped (2 Critical, 4 High, 5 Medium, 3 Low\u002FInfo)\n- 18 screenshots embedded\n- 52,737 bytes markdown \u002F 2,262,484 bytes DOCX\n- 414 paragraphs, 123 headings in DOCX\n- 16 inline images (2 were inline in MD-only edge cases)\n- Time-to-deliverable: ~6 hours after engagement close for first draft\n\nThese numbers are typical for a 1-week external red-team engagement on a mid-size enterprise. Scale down for short tests, up for full purple-team exercises.\n\n---\n\n## Related Skills & Chains\n\n- **`triage-validation`** — This template ingests findings that have ALREADY passed the 7-Question Gate. Engagement flow: every finding through `triage-validation` first → only validated findings → `redteam-report-template` packaging. Skipping triage produces a deliverable padded with informational noise that erodes client trust.\n- **`evidence-hygiene`** — The DOCX with 16 embedded screenshots only works if evidence was captured systematically throughout the engagement. Engagement flow: `evidence-hygiene` discipline at session start → timestamped, organized screenshot folder → `redteam-report-template` consumes that folder to populate Evidence blocks.\n- **`redteam-mindset`** — The Subject \u002F Observations \u002F Description \u002F Impact \u002F Recommendation \u002F PoC structure assumes the operator already thinks like a red-teamer (impact-first, blast-radius framing). Engagement flow: `redteam-mindset` loaded at engagement start → findings collected with red-team framing baked in → `redteam-report-template` produces deliverable without rewriting every Impact section.\n- **`mid-engagement-ir-detection`** — Defensive-action findings (SOC patches mid-test, new IPS rules deployed, account lockouts triggered by external attacker) are first-class findings in red-team deliverables. Engagement flow: `mid-engagement-ir-detection` captures behavior-change events → each becomes its own Subject in the deliverable, framed as \"client capability observation\" not as \"bug we missed.\"\n- **`report-writing`** + **`bugcrowd-reporting`** — Bug-bounty platform reports use DIFFERENT structure (one finding per submission, platform-specific severity scoring, OOS-clause counters). Engagement flow: if engagement mode is `bug-bounty` per project memory → use `report-writing` \u002F `bugcrowd-reporting` instead. This template is ONLY for external red-team \u002F enterprise client deliverables.\n\n## Limitations\n\n- Process guidance only; it does not authorize probing or exploitation — those steps need their own authorized skill and confirmation gate.\n- Docs-only import: upstream templates, commands, and research assets are not bundled.\n\n### Example\n\n```markdown\nApply this skill's checklist to the current engagement notes and report gaps.\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":41,"source":53,"license":14,"sources":54,"category":40,"date_added":55,"description":7,"source_repo":56,"source_type":35,"report_count":57,"compatibility":58,"license_source":59},"https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter","authorized-engagement-deliverable, enterprise-redteam-report-conventions","2026-09-20","elementalsouls\u002FClaude-BugHunter",1,"Process guidance; no tooling required. Docs-only; upstream templates not bundled.","https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fredteam-report-template","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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill redteam-report-template",{"tool":71,"command":72},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill redteam-report-template",{"tool":74,"command":75},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill redteam-report-template","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fredteam-report-template\u002FSKILL.md",true,[],[80,106,130,150,176,200],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":89,"publishedAt":48},"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",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[90,91,92,93,94,95,82,96,97,98,99,39,35,34,100,101,102,103,104,105],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","active","critical","scope","scripts","relevant","implementing",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":48},"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",[],[113,114,115,116,117,118,119,120,121,122,123,124,125,39,126,35,127,128,101,129],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":48},"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",[],[137,138,139,41,32,140,141,47,46,142,143,37,144,35,34,145,146,147,148,149],"transcript","youtube transcript","youtube","codex","research","text","fetch","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":165,"publishedAt":48},"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",[156,159,162],{"categoryNo":157,"categoryName":158,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":160,"categoryName":161,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":163,"categoryName":164,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师",[137,138,139,166,41,167,32,140,47,168,169,170,171,143,172,35,34,173,174,175],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":186,"publishedAt":48},"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",[182,185],{"categoryNo":183,"categoryName":184,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":160,"categoryName":161,"taxonomyType":20,"taxonomyTypeDesc":21},[139,187,188,117,41,189,190,191,192,47,170,193,194,195,196,34,197,145,198,199],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":207,"publishedAt":48},"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",[206],{"categoryNo":157,"categoryName":158,"taxonomyType":20,"taxonomyTypeDesc":21},[208,139,209,210,41,167,168,211,212,169,170,171,143,213,172,35,34,173,214,148],"youtube full","full","google","server","dlp","credits","automatic"]