Run any Skill in Manus with one click

constituency-ingest

Stars1

Forks0

UpdatedMarch 21, 2026 at 23:03

Gather seat-level constituency information. Use when: updating one Kerala constituency inside the district coverage, review, and verification files with current-cycle supportability notes.

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

Court, Municipal, and License ClerksOffice and Administrative Support Occupations·SOC 43-4031

SKILL.md

readonly

name	constituency-ingest
description	Gather seat-level constituency information. Use when: updating one Kerala constituency inside the district coverage, review, and verification files with current-cycle supportability notes.

Constituency Ingest

When to Use

Refreshing one constituency's live field
Correcting one seat inside district coverage files
Recording whether a seat is supportable, partial, or unsafe

Files

public/data/constituencies.json
research/constituency-coverage/<district>.md
research/constituency-coverage-reviews/<district>-review.md
research/constituency-coverage-verification/<district>-verification.md

Procedure

Find the seat's districtId in public/data/constituencies.json
Read the three district files for that district
Check Tier 1 and Tier 2 sources for the seat
Update only the matching seat section
State the strongest supportable field, confidence, and gaps

Guardrails

Work one constituency at a time
Do not force a full three-front slate when only one lane is source-locked
If higher-tier and lower-tier sources conflict, mark the seat under_review or unsafe
Keep exact source dates in the notes
Never use constituency notes alone to publish product data

Handoff

If one candidate becomes the clear front-runner, queue candidate-facts-ingest
If the district is fully supportable, the publish step belongs to district-migration

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	constituency-ingest
description	Gather seat-level constituency information. Use when: updating one Kerala constituency inside the district coverage, review, and verification files with current-cycle supportability notes.

Constituency Ingest

When to Use

Refreshing one constituency's live field
Correcting one seat inside district coverage files
Recording whether a seat is supportable, partial, or unsafe

Files

public/data/constituencies.json
research/constituency-coverage/<district>.md
research/constituency-coverage-reviews/<district>-review.md
research/constituency-coverage-verification/<district>-verification.md

Procedure

Find the seat's districtId in public/data/constituencies.json
Read the three district files for that district
Check Tier 1 and Tier 2 sources for the seat
Update only the matching seat section
State the strongest supportable field, confidence, and gaps

Guardrails

Work one constituency at a time
Do not force a full three-front slate when only one lane is source-locked
If higher-tier and lower-tier sources conflict, mark the seat under_review or unsafe
Keep exact source dates in the notes
Never use constituency notes alone to publish product data

Handoff

If one candidate becomes the clear front-runner, queue candidate-facts-ingest
If the district is fully supportable, the publish step belongs to district-migration