'reporting' 검색 결과

Map threat groups’ documented attack techniques in MITRE ATT&CK Navigator. Creates visual layers and heatmaps, compares groups, and highlights techniques missing from existing detection coverage to support security reporting and decisions about detection priorities.

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

• Visualizing a threat group's attack techniques
• Comparing techniques shared by multiple threat groups
• Finding gaps in existing detection coverage

Plan team structure and hiring by defining needed roles, headcount, timing, and costs. Produce text-based org charts and prioritized hiring roadmaps, and identify structural risks such as excessive management overhead or dependence on one person.

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

• Plan required roles, headcount, and hiring dates
• Review reporting lines and team boundaries
• Set priorities and sequence upcoming hires

Develop and review FastGPT data migration tasks for automatic system upgrades. Define safe reruns, resume points, progress reporting, and failure handling, while checking task order and whether upgrades must block application startup.

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

• Adding a data migration to an automatic upgrade
• Designing batch processing that resumes after interruption
• Reviewing startup blocking and failure policies

Scan repository documentation, tests, and code for small, well-supported problems, then apply minimal fixes on one branch. Verify each fix before committing it separately, and record larger findings for reporting.

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

• Running scheduled repository maintenance
• Finding small issues in documentation, tests, and code
• Collecting separately verified fixes on one branch

Manage complex software and SaaS projects by assessing schedules, budgets, quality, risks, and team capacity. Compare priorities across projects, identify resource constraints, and turn portfolio analysis into executive reports with recommendations for decisions and follow-up.

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

• Review progress and health across multiple projects
• Assess risks and prioritize response actions
• Rebalance staffing based on team capacity

Plan security programs for growing companies by estimating financial risk and prioritizing controls. Produce compliance roadmaps, budget justifications, incident response plans, vendor assessments, and board reports that connect security decisions to business impact.

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

• Justify security budgets with estimated financial losses
• Plan SOC 2 or ISO 27001 compliance work
• Prepare incident coordination and communication plans

Plan revenue growth for B2B SaaS businesses by analyzing sales opportunities, pricing, customer retention, and sales capacity. Develop scenario forecasts, churn intervention plans, hiring models, and revenue reporting for board discussions.

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

• Forecast next quarter’s revenue
• Analyze churn and expansion revenue
• Review pricing and packaging

Guide product strategy for growing companies by assessing customer fit, product investment priorities, and team structure. Produces scorecards, portfolio recommendations, organization proposals, and board reporting materials to support decisions about what to build and fund.

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

• Defining a product vision for the next three to five years
• Assessing product fit using retention and customer feedback
• Choosing which products to invest in, maintain, or retire

Diagnose GKE nodes marked NotReady or Unknown using node conditions, events, logs, and resource metrics. The skill gathers evidence, distinguishes temporary transitions from faults, and proposes fixes for a person to apply.

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

• Investigate persistent NotReady or Unknown node status
• Check why kubelet stopped reporting node status
• Investigate evictions or Pending Pods linked to node health

Set up the official Google Ads MCP Server, a connector that lets AI assistants retrieve campaign data and reporting metrics through natural language. The guide covers installation, credentials, client configuration, and connection checks.

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

• Connecting Claude Code or Cursor to Google Ads
• Configuring API credentials and environment variables
• Testing campaign queries in natural language

Use the P7 engineering workflow in Codex CLI through a command alias. It guides planning, implementation, and a three-question self-review, then requires command and output evidence before reporting completion.

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

• Calling the P7 workflow from Codex CLI
• Planning, implementing, and reviewing a coding task
• Reporting completion with command and output evidence

Organize Jira issues, plan sprints, and define workflows with clear ownership and acceptance criteria. Get help writing JQL, Jira's query language, to find stalled work, review workloads, and support project reporting.

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

• Organizing issues and acceptance criteria
• Planning sprints from recent team performance
• Finding stalled issues and blockers with JQL

Navigate a smart contract security knowledge base in a suggested reading order. Find guides covering audit preparation, vulnerability patterns, code searches, reproduction tests, reporting, case studies, and AI tools without losing track of the next topic.

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

• Finding a starting point for learning smart contract auditing
• Following guides from preparation through reporting
• Locating audit case studies

Run TVM's TIRx compiler tests alongside tirx-kernels import and correctness checks. It verifies the local build, selects GPUs, runs parallel tests, saves full logs, and guides failure investigation and result reporting.

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

• Testing TIRx compiler and kernel changes
• Checking tirx-kernels imports and registry entries
• Running parallel tests across selected GPUs

Check estimated token usage against daily limits before and after each automated loop run. Switch to reporting only, exit early when required, and record run outcomes so repeated agent work stays within configured limits.

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

• Checking daily token usage before a run
• Switching to reporting only near budget limits
• Exiting early when there is no actionable work

Trace a security finding from an attacker’s entry point to its impact using repository evidence. Examine access, permissions, existing defenses, and counterevidence to assess severity and decide whether the finding warrants reporting.

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

• Trace how an attacker could exploit a finding
• Reassess severity against existing defenses
• Check counterevidence before reporting

Compare two GEO audits, which assess a site's readiness for AI search visibility, and produce a monthly client report. Summarize score changes, crawler access, completed actions, newly discovered issues, and priorities for the following month.

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

• Prepare a monthly GEO progress report for a client
• Compare baseline and current audit scores
• Review completed actions and next month's priorities

Add Sentry error reporting and performance monitoring to services, scheduled jobs, and database operations. Follow examples for capturing exceptions with useful context and measuring execution time through spans, which record individual operations for investigation.

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

• Adding error reporting to an API
• Recording failures and execution time for scheduled jobs
• Measuring database and asynchronous operations

Verify work before reporting completion, committing changes, or creating a pull request. Run the checks that support each claim, inspect their output and exit codes, and report the actual results rather than relying on assumptions or agent reports.

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

• Verify results before reporting completion
• Reproduce the original bug to check a fix
• Check tests and builds before committing or opening a PR

Verify development results before reporting success or preparing commits and pull requests. Run checks that support each claim, inspect their actual output, and report remaining gaps instead of relying on assumptions or another agent’s success message.

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

• Checking evidence before reporting a bug as fixed
• Confirming test and build results before a commit
• Verifying that a regression test detects the bug

Create or modify Excel workbooks, then independently check the saved file with Python. Verify required sheets, columns, populated cells, row counts, and sample selections against the requested structure before reporting the work as complete.

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

• Creating Excel workbooks from reference data
• Identifying the correct workbook before editing
• Checking required sheets, columns, and row counts

Check generated PDFs with PyPDF2 before reporting completion. A Python script verifies that each file can be opened and has the expected page count, helping identify outputs that need regeneration.

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

• Checking a generated one-page summary
• Verifying page counts across multiple PDFs
• Checking PDFs before reporting completion

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

Organize authorized phishing exercises from sending infrastructure and email scenarios to landing pages and reporting. Uses GoPhish campaign tracking to review opens, clicks, and submissions while assessing employee awareness and email security controls.

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

• Planning an authorized phishing exercise
• Preparing sending infrastructure and landing pages
• Reviewing email, QR code, and callback scenarios