원클릭으로 Manus에서 모든 스킬 실행

시작하기

timeline-review-checker

스타1

포크0

업데이트2026년 4월 6일 07:07

Optional helper for one candidate review pass in the active worker-pool model.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

aarshps

aarshps/hora-prathinidhi

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Timeline Review Checker

When to Use

Running an explicit second-pass review when the end-to-end worker is split into helpers
Evaluating staged facts and timeline claims against all guardrails
Writing canonical review JSON for a candidate already inside the active queued -> assigned -> published | blocked workflow

Canonical Output

research/swarm/reviews/<candidateId>.json
research/swarm/tasks/<candidateId>.json (publication handoff or blocked state)
research/swarm/escalations/state.json when blocked

Procedure

Read research/swarm/guardrails.json and the candidate task before acting
Confirm the candidate is claimed in the owning shard's activeAssignments
Independently verify timeline and facts: source tier, eventStatus ceiling, date validity, no duplicate eventId, no overclaiming, no unsupported reword-only strengthening, no affidavit/declaration microcard spam, and no facts/timeline conflicts
Write canonical review JSON with the active worker-pool metadata the repo already uses
Apply the decision in task file as a publish handoff or blocked stop; if policy-blocked, update the rolling entry in research/swarm/escalations/state.json

Defect Codes

BAD_SOURCE_TIER · PRE_WITHDRAWAL_OVERCLAIM · TIMELINE_RULE_VIOLATION · FACTS_SCHEMA_DRIFT · PROVENANCE_DRIFT · LEGACY_SURFACE_WRITE · MISSING_EXACT_DATE · NON_VOTER_USEFUL_EVENT · DUPLICATE_ASSIGNMENT · BATCH_RULE_VIOLATION · PUBLIC_COPY_LIMIT · OVERSTATED_REWORD · DECLARATION_SPAM

Guardrails

Do not edit candidate facts or timelines
Do not write review prose outside the JSON payload
Task file is authoritative under contention
Do not create run-numbered escalation artifacts
This helper is optional; the default end-to-end worker may write its own review JSON before publication

Handoff

Approved -> publication by the same worker or orchestrator follow-up; rejected/blocked -> orchestrator follow-up

이 저장소의 다른 Skills

같은 저장소

data-validation

aarshps/hora-prathinidhi

Validate integrity of all public/data JSON files. Use when: after editing candidates, constituencies, or districts JSON; before committing data changes; checking coverage completeness; debugging data mismatches.

2026-04-251

public-candidate-sync

aarshps/hora-prathinidhi

Refresh public district candidate rows from structured live-field research plus staged facts/timelines. Use when: surfacing all candidates per constituency in the app, resyncing public/data after research candidate changes, or restoring legacy candidate route aliases.

2026-04-251

session-wrap-up

aarshps/hora-prathinidhi

Wrap up a meaningful repo work session. Use when: folding durable learnings into repo-local skills, syncing AGENTS/README/handoff docs, or preparing the final close-out commit and push.

2026-04-241

issue-watch-closeout

aarshps/hora-prathinidhi

Drive recurring GitHub issue work from shipped slices to final closeout or reusable closed-issue audits.

2026-04-241

constituency-outcome-slice

aarshps/hora-prathinidhi

Work one bounded constituency possible-outcome slice. Use when: creating or reviewing seat-local outcome packets under the new 1 primary + 3 reviewer workflow.

2026-04-081

ui-conventions

aarshps/hora-prathinidhi

UI rules for the Kerala elections app. Use when: modifying components, adding status indicators, changing how candidates or constituencies display, or touching motion.

2026-04-071

name	timeline-review-checker
description	Optional helper for one candidate review pass in the active worker-pool model.

Timeline Review Checker

When to Use

Running an explicit second-pass review when the end-to-end worker is split into helpers
Evaluating staged facts and timeline claims against all guardrails
Writing canonical review JSON for a candidate already inside the active queued -> assigned -> published | blocked workflow

Canonical Output

research/swarm/reviews/<candidateId>.json
research/swarm/tasks/<candidateId>.json (publication handoff or blocked state)
research/swarm/escalations/state.json when blocked

Procedure

Read research/swarm/guardrails.json and the candidate task before acting
Confirm the candidate is claimed in the owning shard's activeAssignments
Independently verify timeline and facts: source tier, eventStatus ceiling, date validity, no duplicate eventId, no overclaiming, no unsupported reword-only strengthening, no affidavit/declaration microcard spam, and no facts/timeline conflicts
Write canonical review JSON with the active worker-pool metadata the repo already uses
Apply the decision in task file as a publish handoff or blocked stop; if policy-blocked, update the rolling entry in research/swarm/escalations/state.json

Defect Codes

Guardrails

Do not edit candidate facts or timelines
Do not write review prose outside the JSON payload
Task file is authoritative under contention
Do not create run-numbered escalation artifacts
This helper is optional; the default end-to-end worker may write its own review JSON before publication

Handoff

Approved -> publication by the same worker or orchestrator follow-up; rejected/blocked -> orchestrator follow-up