contributor-reward

Convert leaderboard rankings into token-distribution instructions with idempotent state updates.

Updated Jun 2, 2026

Search Tags:#automation #idempotent #rewards #dry-run #leaderboard #contributor #token-distribution

Ready to run

npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill contributor-reward-atrium-hermes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: contributor-reward
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/contributor-reward
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill contributor-reward-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Contributor Reward Skill closes the loop between weekly leaderboard rankings and on-chain token transfers by generating a tier-priced reward plan, writing it into memory/distributions.yml, and handing off to distribute-tokens for execution. It emphasizes plan generation over money movement, enabling safe, auditable, idempotent workflows.

Core Features & Use Cases

Transforms fork-contributor-leaderboard rankings into a per-week reward plan with tiered USDC amounts.
Writes the planned payouts to memory/distributions.yml and prepares an actionable, auditable record for operators.
Supports dry-run previews and first-PR bonus handling to reward eligible contributors while preventing duplicate payouts.
Updates per-week state and tracks first-PR bonuses to ensure idempotent re-runs.

Quick Start

Run the contributor reward plan for the most recent leaderboard week or specify a target ISO week to process.

Frequently Asked Questions about contributor-reward

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

FAQPage Schema

How do I automate weekly contributor token rewards from a leaderboard?▼

To automate weekly contributor token rewards, this Skill translates leaderboard rankings from markdown files into tiered USDC distribution instructions and writes them to distributions.yml. It calculates payouts for top contributors while enforcing idempotent state updates to prevent duplicate transfers.

Can I preview token distributions before executing on-chain transfers?▼

Yes, you can preview token distributions using the dry-run mode. This allows you to generate and review the reward plan written to distributions.yml without executing any actual blockchain transfers, ensuring your payout calculations are correct before commitment.

How does the contributor reward system handle duplicate payouts across re-runs?▼

The system prevents duplicate payouts by enforcing idempotent state updates. It tracks per-week state and first-PR bonuses in a dedicated JSON file, ensuring that re-running the reward plan for the same ISO week does not overwrite existing distributions or issue redundant rewards.

How do I calculate first-PR bonuses for new leaderboard contributors?▼

The system calculates first-PR bonuses by checking contributor history against stored state. It identifies eligible new contributors within the top ranks, applies the bonus to their tier-priced USDC reward, and records the bonus status to maintain idempotent re-runs.

What is the minimum score threshold for distributing contributor rewards?▼

The minimum score threshold is a configured requirement that contributors must meet to qualify for rewards. The Skill targets only the top contributors ranked 1-5 who exceed this score, ensuring that token distributions are allocated exclusively to high-impact participants.

Why does my distributions.yml file not update when re-running the contributor reward plan?▼

Your distributions.yml file does not update because the Skill enforces safe write rules to prevent overwriting existing distribution records. This idempotent behavior ensures that previously generated payout plans remain intact when you re-run the process for the same week.