Menu
hada.io RSS feed monitoring for AI agent/harness articles with automated /scout analysis
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | hada-scout |
| description | hada.io RSS feed monitoring for AI agent/harness articles with automated /scout analysis |
| scope | package |
| version | 1.0.0 |
| user-invocable | false |
Automated pipeline that monitors hada.io (via feedburner RSS) for AI agent, harness, benchmark, and eval-related articles, then runs /scout analysis on each match.
Complement geeknews-scout with harness/eval-focused coverage from hada.io. While geeknews-scout casts a broad net over AI agent news, hada-scout narrows to benchmark/evaluation framework content — the domain most relevant to oh-my-customcode's harness and agent-eval subsystems.
hada-scout issueshada-scout + pending-scoutpending-scout labelclaude -p "/scout {url}" (max 5 executions per run)pending-scouthada-scout uses harness/benchmark/eval focused keywords, distinct from geeknews-scout's broader AI agent coverage:
harness|benchmark|eval|evaluation framework|agent framework|코드 리뷰 자동화|하네스|벤치마크|평가
Geeknews-scout handles: Claude|Anthropic|MCP|AI agent|에이전트|agentic|multi-agent|...
| Label | Purpose |
|---|---|
hada-scout | Source identification — all hada-scout created issues |
pending-scout | Awaiting /scout analysis (set by Layer 1, cleared by Layer 2) |
scout:internalize | /scout verdict: adopt into project |
scout:integrate | /scout verdict: use as external dependency |
scout:skip | /scout verdict: not relevant |
pending-scout issues are processed in the next scheduled runinfra/geeknews-scout/ubuntu-ext clusterinfra/hada-scout/
check-feed.sh — Layer 1 feed pollerscout-runner.sh — Layer 2 /scout executorDockerfilecronjob.template.yamldeploy.sh.env.example| Variable | Default | Description |
|---|---|---|
GH_TOKEN | (required) | GitHub PAT for issue creation |
REPO | baekenough/oh-my-customcode | Target repo |
FEED_URL | http://feeds.feedburner.com/geeknews-feed | hada.io RSS feed |
KEYWORDS | (see above) | Pipe-separated keyword regex |
MAX_SCOUT_PER_RUN | 5 | Max /scout executions per Layer 2 run |
| Rule | How |
|---|---|
| R009 | Layer 1 and Layer 2 run as independent CronJobs |
| R010 | Skill defines the architecture; implementation delegated to infra-docker-expert for K8s manifests |
| scout skill | Layer 2 invokes /scout via claude -p subprocess |
GitHub Issue #841
Invoke and resume YAML-defined pipelines by name — /pipeline auto-dev runs the full release pipeline
Full Self Driving — autonomous release loop that processes all auto-dev-eligible GitHub issues until none remain, by repeatedly running /pipeline auto-dev then /homework.
On explicit /homework invocation, analyze the current and linked previous sessions, extract mistakes (찐빠), and report them via omcustom-feedback with a confirmation gate. Auto-activation on session cleanup/session-end signals is OPT-IN (default OFF) — requires an explicit project/user directive. Use when explicitly auditing recent work for harness gaps.
Pre-action boundary checking — validates agent tool calls against declared capabilities and task contracts
Auto-detect project context and optimize harness — deactivate unused agents/skills, suggest missing experts, generate project profile
Adversarial code review using attacker mindset — trust boundary, attack surface, business logic, and defense evaluation