clawdtributor

Triages Discord-discovered OpenClaw PRs and issues with live GitHub rechecks and maintainer-style reviews.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/AmirulAndalib/Vilvona-AI --skill clawdtributor-amirulandalib
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clawdtributor
Source: https://github.com/AmirulAndalib/Vilvona-AI/tree/main/.agents/skills/clawdtributor
Command: npx skills add https://github.com/AmirulAndalib/Vilvona-AI --skill clawdtributor-amirulandalib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributor PRs and issues surface in a Discord channel faster than maintainers can verify them, and stale or already-merged items waste review time. This Skill turns that noisy queue into a verified, prioritized list of live-open candidates with risk and verification assessments. ## Core Features & Use Cases - Archive-to-live pipeline: Extracts GitHub PR/issue references from the local Discord archive, then rechecks each one against the live GitHub API before listing anything as open. - Maintainer-quality review: Inspects PR bodies, diffs, checks, and current main-branch code to classify blast radius, detect duplicates or already-fixed items, and state whether local or live proof is needed. - Compact ranked output: Produces color-coded bullets with @handle, LOC, type, risk marker, blast radius, and verifiability, sorted by maintainer importance rather than recency. - Use Case: Ask for "5 new clawtributor candidates" and receive five verified live-open PRs, each with a one-line summary, risk marker, and proof hint, ready for triage decisions. ## Quick Start Ask the assistant to list the five best open clawtributor PR candidates with live status rechecks and risk summaries.

Frequently Asked Questions about clawdtributor

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

FAQPage Schema
How do I triage GitHub PRs discovered in a Discord channel?

Query the local discrawl archive for messages containing github.com/openclaw/openclaw pull or issue links, then recheck each reference with the gh API to confirm it is still open. Rank survivors by maintainer importance and report handle, LOC, type, and risk.

How to verify a PR is still open before reviewing it?

Call gh api repos/openclaw/openclaw/pulls/<number> with a jq projection of state, merged, draft, and updatedAt fields. Never rely on the archived Discord message alone, since items merge or close after being posted.

Why does gh api fail with bad credentials?

Stale GITHUB_TOKEN, GITHUB_TOKEN_NODIFF, or GH_TOKEN environment variables override valid authentication. Clear them with empty assignments inline before the gh command, as shown in the live recheck commands.

Can this Skill close or merge PRs directly?

It supports close and land decisions but requires proof against current main before closing, and a comment first when mutation is requested. Bulk close or reopen operations above five items require explicit scope from the user.

What review depth does each candidate get?

Each open item is checked against its PR body, linked issues, files, checks, and the current main code path. The output states blast radius across runtime surfaces and whether verification needs local tests, live provider proof, or is not directly verifiable.