collector-check

Validates data collectors against a six-item checklist and reports pass, fail, or human-review results.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/hivgb1-ai/do-better-workspace-v2 --skill collector-check-hivgb1-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: collector-check
Source: https://github.com/hivgb1-ai/do-better-workspace-v2/tree/main/.claude/skills/collector-check
Command: npx skills add https://github.com/hivgb1-ai/do-better-workspace-v2 --skill collector-check-hivgb1-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-developers cannot manually verify whether a new data collector (e.g., a channel pulling messages into an inbox) is safe and reliable to attach to their system. This Skill automates that verification by running a six-question checklist and reporting clear pass/fail/human-check verdicts. ## Core Features & Use Cases - Six-Point Automated Inspection: Checks non-duplication (runs the collector twice and compares raw file counts), freshness tracking (verifies the declared state file updates), fidelity (samples raw files for truncation), privacy (greps for OTP/verification-code patterns), sustainability (lists human-maintenance dependencies), and capture completeness (full capture vs. selective). - Structured Verdict Report: Outputs a table with per-item results and a final judgment: attach as-is, fix first, or awaiting human confirmation. - Registry Drift Detection: When the declared registry (자리-선언표.yaml) disagrees with reality, it recommends updating the declaration first. - Use Case: Before connecting a new messaging channel to your PKM inbox, ask for a collector check to confirm it will not create duplicates, leak authentication codes, or silently drop content. ## Quick Start Ask the AI to run a collector check on the new channel before attaching it to the system.

Frequently Asked Questions about collector-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a new data collector is safe to attach?▼

Run the collector check, which executes a six-question inspection covering duplication, freshness, fidelity, privacy, sustainability, and capture completeness. It reports each item as pass, fail, or human-check with a final attach-or-fix verdict.

How to test that a data collector does not create duplicates?▼

The check runs the collector's declared command twice in a row and compares raw file counts before and after. Zero growth means the non-duplication promise holds; collectors without a run command are checked via their declared unique-marker mechanism.

Can automated checks detect privacy leaks in collected data?▼

Yes, the check greps raw collected files for OTP and verification-code patterns such as 4-6 digit codes near authentication keywords. Matches produce a warning recommending a collector-level blocklist rather than a hard failure.

What happens when a check requires human confirmation?▼

Items the machine cannot verify, such as comparing collected text against the original source app, are marked as human-check. The report tells you exactly what to open and compare, and the final verdict waits on that confirmation.

Why does the collector check report registry drift?▼

When the declared registry file disagrees with reality, such as a missing state file, the check recommends updating the declaration first. This prevents stale declarations from misrepresenting the actual system state.