'report' 검색 결과

Turn research, analysis, or any markdown the agent just produced into a live, beautifully designed web report with a shareable tracked URL via ReportRoom. Use when the user says "publish this", "make this shareable", "turn this into a report", "put this on a page", or wants findings to live beyond the chat. Not for recurring client deliverables (use client-reporter), slide decks (use deck-publisher), or proposals that need view alerts (use proposal-tracker).

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

Use at the Mem Off hackathon. Keeps a running, evidence-backed report on how the participant's memory system performed for their coding agent during the day — what the harness measured, what cognee-report's scorecard says, what was recalled and whether it helped — in ./memoff-report.md and ./memoff-report.json. The report is submitted together with the action results; it never contains quotes, keys, data or names.

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

Writes a DRAFT weekly KPI report from the figures the user pastes or attaches (this week, last week, optionally target and earlier weeks): a metrics table with change versus last week computed only from the stated figures, plain-language notes per metric, and numbered questions on every figure that moved more than the agreed threshold, crossed its target or broke its run. Use when the user asks to "write the weekly KPI report", "turn these numbers into this week's metrics report", "what changed versus last week", "draft the Monday numbers update" or "add commentary to this metrics table". Do not use for a recurring emailed report with a maintained trend sheet, use report-attachment-analyzer instead; for actuals versus budget, use budget-variance-explainer. Drafts for human review; never approves, authorises or signs off.

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

Generate HTML reports and structured metrics from model evaluation results. Creates publication-ready reports with embedded outputs (images, audio, charts) and metrics.json for cross-model comparison. Use when generating reports, writing metrics, creating evaluation summaries, or formatting benchmark results. Triggers on "generate report", "write metrics", "create report", "evaluation summary", "benchmark results", "format results".

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

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

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

점수가 매겨진 경쟁사 자료를 시장 지도, 비교표, 차별화 여지와 우선 실행안을 담은 보고서로 정리합니다. 경영진 보고와 팀의 경쟁 전략 결정에 활용합니다.

• 경영진·이사회용 경쟁 현황 보고
• 완성된 경쟁사 프로필 통합
• 차별화 여지와 경쟁 위협 검토

환자 정보를 바탕으로 회진, 증례 발표, 기록용 보고서를 구성합니다. 병력과 검사 결과, 감별 진단, 문제별 대응 계획을 인쇄용 HTML로 정리합니다.

• 증례 발표 자료 준비
• 회진이나 인계용 경과 요약
• 임상 소견을 SOAP 형식으로 정리

주요 지표와 분석 결과, 유지율 그래프를 잡지 형식의 한 페이지 HTML 보고서로 정리합니다. 종이 질감 배경과 파스텔색 카드를 사용해 경영 회의 자료를 만듭니다.

• 잡지 형식의 사업 보고서 작성
• 경영 회의용 한 페이지 자료 작성
• 주요 지표와 분석 내용 정리

claude-mem에 저장된 개발 이력을 읽어 설계 변화, 난제 해결, 작업 패턴을 서사형 보고서로 정리하고, 기억 재사용으로 절약한 토큰을 추정합니다.

• 프로젝트 개발 이력을 돌아볼 때
• 설계 결정과 영향을 추적할 때
• 오류 조사와 작업 패턴을 살필 때

에이전트의 작업 기록과 토큰 수로 완료한 성과별 비용과 재작업 비용을 정리합니다. 추정액과 실측액을 구분하고 근거를 담은 HTML, JSON, CSV 보고서를 만듭니다.

• 주간 지출과 성과를 확인할 때
• 완료한 성과별 비용을 비교할 때
• 반복 작업과 재작업 비용을 조사할 때

시장·경쟁사·소비자·재무 조사의 목차와 필요한 데이터를 설계하고, 수집한 정보를 도표·출처·전략적 시사점이 담긴 보고서로 정리합니다.

• 조사 목차와 수집할 데이터 설계
• 시장·경쟁사 조사 결과의 보고서 작성
• 소비자 이해와 브랜드 전략 정리

Create market research reports that connect claims to sources, compare competitors, and estimate market size. Build alternative forecasts with explicit assumptions, so readers can review the calculations, uncertainties, and evidence behind each conclusion.

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

• Preparing a market report for a new business
• Comparing market size estimates and their assumptions
• Building competitor comparisons with traceable sources

Build draft structures and aggregate tables for clinical case, trial, diagnostic, and safety reports from verified synthetic, de-identified, or aggregate data. Local checks flag structural and consistency issues; qualified professional review remains required.

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

• Prepare a structured case-report draft
• Check trial-report sections for missing items
• Format aggregate adverse-event tables

Turn a Cherry Studio support conversation into an editable draft for a bug report, usability issue, or feature request. The user reviews the wording, chooses any diagnostic data, and submits the report themselves.

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

• Draft a bug report from a support conversation
• Organize feedback about interface usability
• Prepare a feature request for review

Check web pages and components for accessibility issues against WCAG 2.2, web accessibility guidelines. Receive a report prioritized by user impact, or request targeted code fixes followed by verification of resolved and newly introduced issues.

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

• Get a prioritized accessibility report for a page
• Audit accessibility patterns across components
• Fix reported issues and verify the changes

Create task-oriented READMEs, API references, architecture documentation, and security reports. Organize information from quick starts to deeper explanations, and turn completed investigations into formal Markdown reports with supporting evidence, reproducible steps, and appropriately masked sensitive information.

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

• Writing a README with a clear quick start
• Organizing API and architecture documentation
• Reporting reverse engineering or penetration test findings

Research social discussions using public posts or authorized exports, and produce reports that link each claim to inspected evidence. Track duplicate posts, distinguish speakers, document access gaps, and audit conclusions that exceed the observed sample.

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

• Comparing product discussions across social platforms
• Creating cited reports from supplied post exports
• Checking repost duplication and comment attribution

Turn stock, industry, strategy, or backtest research into structured Markdown reports. Present conclusions, supporting data, ratings, risks, and recommendations using consistent tables and terminology, with PDF delivery supported through the specified rendering tool.

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

• Write a detailed stock research report
• Organize an industry or market outlook
• Report results from tests on historical trading data

Retrieve U.S. company filings and financial series from SEC EDGAR. Resolve stock tickers to company identifiers, list recent reports with document links, and fetch reported metrics such as revenue or assets without an API key.

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

• Find a company's recent annual reports and document links
• List quarterly reports and material event filings
• Retrieve reported revenue or net income series

Review Cuckoo or AnyRun behavior reports for signs that malware is avoiding an analysis environment. Identify timing checks, virtual machine detection, and user activity checks, then produce a JSON report with evidence, technique mappings, and an evasion sophistication score.

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

• Investigating malware that stays inactive in a sandbox
• Reviewing behavior reports for analysis evasion
• Developing detections for anti-analysis behavior

Create a one-page Monday briefing that combines cash, sales, sales opportunities, saved performance reports, and upcoming commitments. Identify one priority for the week using connected services or data supplied through pasted text and uploaded files.

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

• Reviewing cash, sales, and sales opportunities on Monday
• Combining saved performance reports into a weekly briefing
• Checking upcoming commitments and replies you owe

Turn marketing results into a report with key metrics, comparisons over time, wins, and areas to improve. Prioritize recommendations by expected impact and effort, then outline the next period’s actions for teams or leadership.

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

• Reviewing results after a marketing campaign
• Preparing weekly or monthly channel reports
• Summarizing marketing performance for leadership

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

Turn rough bug reports, feature requests, support notes, or pull requests into concise issues. Explain the current problem and desired behavior in plain language, preserving useful evidence without prescribing how developers should implement a solution.

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

• Simplifying a lengthy bug report
• Drafting an issue from a pull request
• Clarifying the intended experience for a new feature