Atlas / Skills / revfactory / Report Generator

Report GeneratorSAFE

skills/revfactory/report-generator
Verdict
SAFE
Grade
B
Trust score
89 /100
Version
—
Hosts
—
License
Apache-2.0
Stars
1,297
01

Overview

An agent skill published by revfactory.

Read from source at commit 459e1bb8f76eOBSERVED · 2026-10-12
02

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: report-generator
description: "work report agent team to datacollection→analysis→visualization→→summaryto Korean creation Full pipeline. 'work report create it', 'monthbetween report writing', 'minutebasis results reporting', 'project report', 'marketanalysis report', ' report', 'KPI report', 'data analysis report', 'results summary reporting' etc. work report writing before skill usage. existing data analysis result case also visualization, , summary degreeKRW. However, actualtime BI dashboard building, data directly annual, ERP whensystem integration is outside this skill's scope."
---

# Report Generator — work report Full pipeline

work report datacollection→analysis→visualization→→summary An agent team collaborates to generate all deliverables at once.

## execution mode

**agent team** — 5 agents communicate directly via SendMessage and cross-verify each other's work.

## agent composition

| agent | file | role | type |
|---------|------|------|------|
| data-collector | `.claude/agents/data-collector.md` | data , figure , refinement | general-purpose |
| analyst | `.claude/agents/analyst.md` | statistics analysis, trend, insight derive | general-purpose |
| visualizer | `.claude/agents/visualizer.md` | chart, , diagram peopletax | general-purpose |
| report-writer | `.claude/agents/report-writer.md` | report structure and | general-purpose |
| executive-summarizer | `.claude/agents/executive-summarizer.md` | management summary, cross-verification | general-purpose |

## workflow

### Phase 1: preparation (Orchestrator directly perform)

1. Extract from user input:
 - **report week**: regarding reportperson
 - **reporting type**: basis(monthbetween/minutebasis/annualbetween) / project / analysis
 - **reporting target**: management / team / actualspecialist / external
 - **duration**: reporting target duration
 - **existing material** (optional): user provideKorean data, analysis result, before report
2. `_workspace/` Create the directory at the project root
3. Organize input and save to `_workspace/00_input.md`
4. If existing files are provided, copy them to `_workspace/`and skip the corresponding Phase
5. Determine the **execution mode** based on the scope of the request ( "task scaleby mode" reference)

### Phase 2: team composition and execution

| order | task | responsible | dependency | deliverable |
|------|------|------|------|--------|
| 1 | data collection | collector | None | `_workspace/01_data_collection.md` |
| 2 | data analysis | analyst | task 1 | `_workspace/02_analysis_report.md` |
| 3a | visualization peopletax | visualizer | task 2 | `_workspace/03_visualization_spec.md` |
| 3b | report | writer | task 2 | `_workspace/04_full_report.md` |
| 4 | summary and verify | summarizer | task 3a, 3b | `_workspace/05_executive_summary.md` |

task 3a(visualization) and 3b ** execution**. task 2(analysis) only dependency.

**teamKRW between flow:**
- collector complete → analystto data+quality deliver, visualizerto data deliver
- analyst complete → visualizerto visualization proposal deliver, writerto insight+ beforeitems proposal deliver
- visualizer complete → writerto visualization peopletax+ position deliver
- writer complete → summarizerto report specialist deliver
- summarizer all deliverable cross-verification. 🔴 required revision findings when Request revision from the relevant agent -> rework -> re-verify (up to 2 rounds)

### Phase 3: integration and final deliverable

1. `_workspace/` Verify all files in the directory
2. verify reportConfirm that all critical revisions from the review report have been addressed
3. Report the final summary to the user:
 - data collection — `01_data_collection.md`
 - analysis report — `02_analysis_report.md`
 - visualization peopletax — `03_visualization_spec.md`
 - final report — `04_full_report.md`
 - management summary — `05_executive_summary.md`

## task scaleby mode

| user request pattern | execution mode | deploy agent |
|----------------|----------|-------------|
| "work report create it", "Full report" | **Full pipeline** | 5people beforeKRW |
| " data analysis report " (data provide) | **analysis mode** | analyst + visualizer + writer + summarizer |
| " report summaryplease do" (report provide) | **summary mode** | summarizer |
| "visualization only please do" (analysis result provide) | **visualization mode** | visualizer + summarizer |
| " report reviewplease do" | **review mode** | summarizer |

**existing file utilization**: user data, analysis result etc. existing file provide applicable stage case.

## data deliver protocol

| strategy | method | also |
|------|------|------|
| File-based | `_workspace/` | Store and share major deliverables |
| Message-based | SendMessage | Real-time key information transfer, revision requests |

File naming convention: `{}_{agent}_{deliverable}.{extensionspecialist}`

## error handling

| error type | strategy |
|----------|------|
| web search failure | collection user provide material basedas task, "external data un-secure" specify |
| data insufficient | report data scope within analysis perform, addition secure possible item specify |
| agent failure | Retry once -> proceed without that deliverable, verify report specify |
| verifyfrom 🔴 findings | Request revision from the relevant agent -> rework -> re-verify (up to 2 rounds) |
| reporting target people | management reporting (PREP structure) basicas applied |

## test scenario

### flow
**Prompt**: "2024year 4minutebasis sales performance report create it. reporting target management."
**expected result**:
- data collection: sales related items data, trend collection
- analysis: beforeyear basis versus, minutebasisby , total pyeongbalanced comparison
- visualization: sales chart, by proportion KRW chart, KPI 
- report: PREP structure, management tone, 3items or more
- summary: 1degree management summary + consistency matrix beforeitem confirm

### existing data utilization flow
**Prompt**: " CSV data analysis repor
03

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeNA
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.

Audited 2026-10-12 · audit v0.4.1 · source sha 459e1bb8f76efull audit observations/trust-audit/skill/revfactory__report-generator.json · Report an issue / request a re-scan
04

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-12459e1bb8f76eSAFEB89first audit
05

Questions

Is Report Generator safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can Report Generator access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

How current is this page?

The grade is for one exact copy of the source (459e1bb8f76e), read on 2026-10-12. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement