Run any Skill in Manus with one click

timeline-batch-enrichment

Stars1

Forks0

UpdatedApril 1, 2026 at 16:27

Refresh generated candidate timeline seeds and deepen staged timelines in bulk. Use when: reseeding statewide timeline minima, enriching one priority seat cluster, or syncing public candidate timelines after staged event work.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

aarshps

aarshps/hora-prathinidhi

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

SKILL.md

readonly

name	timeline-batch-enrichment
description	Refresh generated candidate timeline seeds and deepen staged timelines in bulk. Use when: reseeding statewide timeline minima, enriching one priority seat cluster, or syncing public candidate timelines after staged event work.

Timeline Batch Enrichment

When to Use

Refreshing research/candidate-timeline-seeds/ for live-app-linked candidates
Deepening staged timelines for one priority seat or district cluster
Projecting staged timeline updates into public candidate dossiers

Canonical Outputs

research/candidate-timeline-seeds/<candidateId>.json
research/candidate-timelines/<candidateId>.json
public/data/candidate-details/<detailId>.json

Procedure

Read docs/INGESTION_OPERATING_MODEL.md
Trigger facts/timeline agents for the target candidate or priority seat cluster
Keep generated events stable by preserving eventId; suppress instead of deleting when an item should stay hidden
Trigger publication-agent for approved candidates
Trigger ingestion-validator-agent

Guardrails

Do not edit public/data/ first
Do not remove manual timeline events just because a generated seed changed
Do not publish current-cycle definitive status above the evidence tier allowed in docs/INGESTION_OPERATING_MODEL.md
If a candidate facts row is withheld, keep generated current-cycle events suppressed

Handoff

If the seed contract or merge rules change, update the ingestion docs, repo docs, and handoff notes in the same session

More from this repository

same repository

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-batch-enrichment
description	Refresh generated candidate timeline seeds and deepen staged timelines in bulk. Use when: reseeding statewide timeline minima, enriching one priority seat cluster, or syncing public candidate timelines after staged event work.

Timeline Batch Enrichment

When to Use

Refreshing research/candidate-timeline-seeds/ for live-app-linked candidates
Deepening staged timelines for one priority seat or district cluster
Projecting staged timeline updates into public candidate dossiers

Canonical Outputs

research/candidate-timeline-seeds/<candidateId>.json
research/candidate-timelines/<candidateId>.json
public/data/candidate-details/<detailId>.json

Procedure

Read docs/INGESTION_OPERATING_MODEL.md
Trigger facts/timeline agents for the target candidate or priority seat cluster
Keep generated events stable by preserving eventId; suppress instead of deleting when an item should stay hidden
Trigger publication-agent for approved candidates
Trigger ingestion-validator-agent

Guardrails

Do not edit public/data/ first
Do not remove manual timeline events just because a generated seed changed
Do not publish current-cycle definitive status above the evidence tier allowed in docs/INGESTION_OPERATING_MODEL.md
If a candidate facts row is withheld, keep generated current-cycle events suppressed

Handoff

If the seed contract or merge rules change, update the ingestion docs, repo docs, and handoff notes in the same session