data-audit
Report on data completeness for the SPARTA QRA pipeline (Control -> URL -> Knowledge -> QRA). Queries DuckDB to show coverage percentages at each stage.
소스 정보
- 저장소
- grahama1970/agent-stack-public
- 최근 소스 활동
- 2026년 9월 24일 15:51
- 감지된 SKILL.md 언어
- 영어
- 스타
- 0
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
4 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- data-audit
- description
- Report on data completeness for the SPARTA QRA pipeline (Control -> URL -> Knowledge -> QRA). Queries DuckDB to show coverage percentages at each stage.
- triggers
- ["audit sparta","check coverage","data completeness","pipeline status"]
- metadata
- {"short-description":"SPARTA data completeness auditor.","project-path":"${HOME}/workspace/experiments/pi-mono/.agent/skills/data-audit"}
- provides
- ["data-audit"]
- composes
- ["create-figure","task-monitor","agentic-evals"]
- disciplines
- ["data-engineering","evaluation-quality"]
# Data Audit
Audits the SPARTA pipeline data coverage.
## Usage
```bash
# Run full audit
.agent/skills/data-audit/run.sh
# Run for specific run ID (points to specific DB path if needed)
.agent/skills/data-audit/run.sh --run-id <run-id>
```
## Logic
Connects to SPARTA DuckDB and calculates coverage for:
1. **Controls**: Base set.
2. **URLs**: Controls mapped to at least one URL.
3. **Knowledge**: Controls mapped to URLs that have extracted chunks.
4. **QRA**: Controls that have generated QRA pairs.
## Visualization
After generating coverage data, offer to visualize via `/create-figure`:
```bash
# Pipeline coverage as stacked bar chart
create-figure metrics --input audit.json --output coverage.png --type bar --title "SPARTA Pipeline Coverage"
# Coverage heatmap by category
create-figure heatmap --input audit.json --output coverage-heatmap.png
```
**When to offer:** After presenting coverage percentages, ask: "Want me to chart the pipeline coverage?"
## Common Mistakes
### WRONG: Running audit without a DuckDB path when needed
```bash
./run.sh # may fail if DuckDB path is not configured
```
### RIGHT: Specify run ID or verify default DB path
```bash
./run.sh --run-id <run-id> # explicit run
```
### WRONG: Reporting raw counts without coverage percentages
```
Controls: 800, URLs: 500, QRAs: 200 # raw numbers are meaningless
```
### RIGHT: Report coverage ratios at each pipeline stage
```
Controls: 800 → URLs: 500 (62.5%) → Knowledge: 350 (43.8%) → QRA: 200 (25.0%)
```
### WRONG: Not visualizing results for stakeholder communication
```bash
./run.sh # text output only, hard to share
```
### RIGHT: Generate charts via /create-figure after audit
```bash
./run.sh > audit.json
create-figure metrics --input audit.json --output coverage.png --type bar
```
GitHub에서 보기