'report' 검색 결과

Apply ReportLab’s built-in paragraph styles to PDF titles, headings, and body text. Learn how to reuse existing styles and create named variations without duplicate style names that can cause KeyError exceptions.

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

• Applying consistent styles to PDF titles and body text
• Checking available built-in paragraph styles
• Creating a custom style based on an existing one

Create multi-page PDFs with headings, tables, and consistent styling using reportlab, a Python library for building PDF documents. Run code directly through run_shell to control margins and page breaks when shell_agent document creation is unreliable.

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

• Creating multi-page reports with tables
• Adjusting document margins and page breaks
• Generating PDFs when shell_agent creation fails

[omh] Periodic report for executives: weekly/monthly reports, executive briefs, PPT-ready outlines, and upload packages. Use when the user says: report-package, report package, weekly report, monthly report, executive report, exec brief, leadership deck, status package.

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

Generate affiliate performance reports with KPIs and recommendations. Triggers on: "show my affiliate report", "how are my programs doing", "performance review", "earnings report", "monthly affiliate report", "weekly report", "analyze my affiliate earnings", "which program is best", "EPC report", "conversion rate analysis", "revenue breakdown", "campaign performance".

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

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.

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

Structured diagnostic code library for JavaScript/TypeScript. Turns errors and other conditions into typed, machine-readable `Diagnostic` instances with stable codes, docs URLs, and actionable fields. Use this skill whenever the project imports `nostics`, or works with `defineDiagnostics`/`defineProdDiagnostics`, the `Diagnostic` class, diagnostic code registries, or structured error handling. Also covers reporters (`createConsoleReporter`, `createFetchReporter` from nostics/reporters/fetch, `createFileReporter` from nostics/reporters/node, `createDevReporter` from nostics/reporters/dev), formatters (`formatDiagnostic`, `ansiFormatter`, `jsonFormatter`), and Vite plugins (`nosticsStrip` from @nostics/unplugin/strip-transform, `nosticsCollector` from @nostics/unplugin/dev-server-collector). Also use when migrating a library's existing `console.warn`/`console.error`/`warn()` helpers or thrown `Error`s to diagnostics: follow `references/migration.md`.

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

Writes professional bug bounty reports for HackerOne, Bugcrowd, and Intigriti with CVSS 4.0 scoring, business impact, working exploits, and remediation. Runs 5-check Pre-Report Verification first: hallucination detection, AI writing patterns, PoC reproducibility, duplicate detection, and impact plausibility. Use when user describes a vulnerability, shares HTTP logs, HAR files, recon output, or screenshots; says 'write a bug report', 'format my finding', 'draft a vuln report', 'is this valid', 'rate my vulnerability', 'verify my report', or any variant. Trigger for partial or messy input — raw notes, one-liners, or full writeups all work. Do not wait for perfect input.

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

Builds the "Report Sources" child page for a finished Weekly Community Signal report — an evidence-backed defense of WHY every item landed in the column/section/rank it did. The agent argues each placement like a lawyer (claim → evidence → rule → rebuttal) but is under oath: it CANNOT invent, spin, or overstate — every claim ties to a verifiable fact (issue #, label, PR type, quoted comment, npm output, the front-door test). Not CYA — it's so Nathan can defend the report with facts and see the exact reasoning behind each call. Runs after the report (invoked by weekly-report, last steps) and on "report sources", "defend the report", "why is this here".

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

Build a single-screen financial report as a self-contained HTML file. Present revenue, recurring revenue changes, margins, cash runway, charts, profit and loss comparisons, key accounts, and an outlook for monthly, quarterly, or yearly reporting.

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

• Preparing a monthly or quarterly financial report
• Reviewing SaaS recurring revenue and cash runway
• Comparing profit and loss with the previous period

Turn CSV, Excel, or JSON data into a visual report page with key metrics, multiple charts, a data table, and written observations. The report uses supplied data and includes its source, reporting period, and methodology.

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

• Turn growth data into a visual weekly report
• Present key metrics and year-over-year changes
• Share charts alongside source data and methodology

Prepare and submit bug reports or feature requests to GitHub, checking for duplicates and following issue templates. Reports are previewed for approval before submission, or saved locally when GitHub authentication is unavailable.

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

• Report a bug to GitHub with clear reproduction steps
• Prepare a feature request using the issue template
• Save reports locally when GitHub login is unavailable

Prepare an initial equity research report through five separate tasks covering company research, financial forecasts, valuation, charts, and report assembly. Outputs include research notes, an Excel financial model, chart files, and a detailed Word report.

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

• Researching a company’s business, competitors, and risks
• Building financial forecasts with three scenarios
• Estimating a price target using multiple valuation methods

Investigate Linux intrusions using auditd records. Configure audit rules, search events with ausearch, summarize activity with aureport, reconstruct a timeline of suspicious actions, and forward logs to a central security monitoring system.

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

• Investigating unauthorized access or privilege escalation
• Checking changes to critical files and SSH keys
• Reconstructing an incident timeline

Read data from Google Sheets and turn it into a Google Docs report. The workflow covers creating the document, writing report sections, and granting a stakeholder permission to read the finished file.

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

• Create a sales report from spreadsheet data
• Write a report with a summary and key deals
• Grant stakeholders read access to a report

Save reports with timestamps and categories, then retrieve the latest version using familiar keywords. Before delivery, check that links point directly to the relevant content and flag actionable items that lack a link.

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

• Saving and retrieving the latest morning briefing
• Finding meeting digests by keyword
• Checking research report links before delivery

Draft and edit internal updates, newsletters, FAQs, and incident reports using the appropriate reference format. Turn supplied notes or information retrieved through connected tools into concise communications tailored to the audience and reporting period.

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

• Drafting weekly progress, plans, and problems updates
• Creating company-wide newsletters
• Organizing frequently asked questions and answers

Create custom Google Analytics reports with user counts, page views, and breakdowns by city or date. The skill covers API setup, authentication, and checking whether selected measurements and grouping fields can be used together.

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

• Report active users by city and date
• Automate recurring analytics reports
• Check which report fields work together

Assess reported phishing emails by checking sender authentication, links, and attachments. Post a risk rating, supporting evidence, and a recommended action to Slack, leaving blocking, deletion, and other changes to the security team.

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

• Triage newly reported suspicious emails
• Reassess a specific reported email
• Explain the evidence behind a risk rating

Create weekly reports from Postgres metrics, comparing current figures with recent weeks. Add plain-language explanations for notable changes, flag missing data, and post one report to Slack while keeping database access read-only.

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

• Preparing a weekly metrics report for Slack
• Reviewing weekly changes and recent trends
• Explaining notable changes and flagging data gaps

Structure and revise investment research into readable Markdown reports for Codex. Explain business economics, competitive advantages, opposing arguments, and valuation, then connect the evidence to price bands and actions for prospective investors and existing holders.

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

• Restructure a lengthy investment research report
• Explain how a company earns money and sustains its advantages
• Strengthen a report's bear case and observable risk indicators

Turn vulnerability notes, proof-of-concept code, source code, or security findings into self-contained reports. The skill checks claims against evidence, explains prerequisites and demonstrated impact, and supports both individual vulnerabilities and collections of disclosure reports.

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

• Turning vulnerability notes into a disclosure report
• Checking source code and proof-of-concept claims
• Preparing separate reports for multiple vulnerabilities

Turn penetration test and red team results into reports for executives and technical teams. Structure findings, explain severity scores and business impact, organize evidence, and document remediation steps and retest plans.

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

• Preparing a final penetration test report
• Rewriting an executive summary for nontechnical readers
• Creating a reusable security reporting template

Plan, design, author, preview, publish, and manage Power BI reports across requirements, page design, local PBIR/PBIP edits, validation, screenshots, Fabric upload/download, and rebinding. Use for report lifecycle work; use semantic-model-authoring for model or DAX changes and fabriciq for data questions. Triggers: plan Power BI report, design report page, edit PBIR, preview PBIP, publish report, rebind report

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

Step-by-step workflow for creating complete Power BI reports from scratch using pbir CLI. Covers model discovery, report creation, page layout, theme setup, visual placement, field binding, filtering, formatting, validation, and publishing. Automatically invoke when the user asks to "create a new report", "build a report from scratch", "make a dashboard", "set up a report with KPIs", "create an executive dashboard", "add pages and visuals to a new report".

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