'report-writing' 검색 결과

Prepare Bugcrowd submissions with accurate vulnerability categories, evidence-based severity requests, and explanations of program scope. Structure references between related reports, document QA testing conditions, and draft responses when a finding is downgraded or considered out of scope.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose a suitable Bugcrowd vulnerability category
• Explain a severity request using demonstrated impact
• Respond to out-of-scope decisions

Prevent common AI report pitfalls — bug blending, inflated threat models, and generic language. Train Claude with your best past reports for concise, technical submissions. Based on Critical Thinking Bug Bounty Podcast Episode 166.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn validated security findings into clear bug bounty reports for HackerOne, Bugcrowd, Intigriti, or Immunefi. Provides templates, reproducible evidence structure, severity scoring guidance, and submission checks focused on demonstrated impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft a report for a specific bounty platform
• Document reproducible requests and evidence
• Explain severity using demonstrated impact

Turn validated vulnerabilities into clear bug bounty reports for HackerOne, Bugcrowd, Intigriti, or Immunefi. Platform templates help organize demonstrated impact, reproducible steps, supporting evidence, severity reasoning, and concrete fixes in language reviewers can follow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft a report using a platform-specific template
• Write clear titles and impact summaries
• Organize reproduction steps and supporting evidence

Prepare screenshots and network traffic records for bug bounty submissions by masking session secrets and personal data while preserving useful verification details. The skill covers capture setup, HAR cleanup, evidence filenames, and credential handling after submission.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Masking secrets in evidence screenshots
• Cleaning HAR files before submission
• Capturing evidence in Burp Suite and Chrome DevTools

Guidelines for writing well-structured, cited research reports

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides privacy audit report writing including executive summary drafting, findings classification (critical, high, medium, low), evidence referencing, root cause analysis documentation, recommendation formulation, management response tracking, and report distribution protocols. Covers report structure from scope definition through appendices and sign-off. Keywords: audit report, findings documentation, executive summary, recommendations, report structure, privacy audit deliverables.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when any case fails or you reject a criterion - what goes in the review_criterion note, the failed case and the numbered need_revision comment, with severity

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates structured cyber threat intelligence reports at strategic, operational, and tactical levels tailored to specific audiences including executives, security operations teams, and technical analysts. Use when producing finished intelligence products from raw collection data, creating sector threat briefings, or delivering post-incident intelligence assessments. Activates for requests involving CTI report writing, threat briefings, intelligence products, finished intelligence, or executive security reporting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bug bounty report writing for H1/Bugcrowd/Intigriti/Immunefi — report templates, human tone guidelines, impact-first writing, CVSS 3.1 scoring, title formula, impact statement formula, severity decision guide, downgrade counters, pre-submit checklist. Validation gates and the submittability/always-rejected decision are owned by triage-validation; this skill owns the written report itself (templates, tone, formulas). Use after validating a finding and before submitting. Never use 'could potentially' — prove it or don't report.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Companion to the generic report-writing skill. Use when working specifically on Bugcrowd submissions where VRT mapping, OOS-clause rebuttals, or per-program target selection matter.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.