clawdtributor

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

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill clawdtributor-jerome-prakash-l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clawdtributor
Source: https://github.com/JEROME-PRAKASH-L/openclaw/tree/main/.agents/skills/clawdtributor
Command: npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill clawdtributor-jerome-prakash-l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributor PRs and issues surface in the Discord #clawtributors channel, but maintainers need live GitHub status, risk classification, and review depth before acting. This Skill bridges the Discord archive and live GitHub state so triage decisions are based on current facts, not stale links. ## Core Features & Use Cases - Archive-to-live pipeline: Extracts GitHub PR/issue references from the local Discrawl Discord archive, then rechecks each one against the live GitHub API before listing or closing. - Maintainer-quality review: Inspects PR bodies, linked issues, diffs, checks, and current main to classify blast radius, verification needs, and whether items are obsolete or already fixed. - Structured triage output: Produces compact bullets with @handle, LOC, type, risk markers, blast radius, and verifiability, grouped by topic or sorted by maintainer importance. - Use Case: Ask for "5 new clawtributor candidates" and receive five live-open, high-confidence contributor PRs with risk markers and one-line summaries ready for maintainer review. ## Quick Start Ask the assistant to list the five best open clawtributor PR candidates with live status and risk markers.

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 with sqlite3 to extract github.com/openclaw/openclaw pull and issue references from the channel, then recheck each one live with the gh api pulls or issues endpoint before listing or acting on it.

How do I check if a GitHub PR is still open using the gh CLI?

Run gh api repos/openclaw/openclaw/pulls/<number> with a --jq projection selecting number, title, state, merged, and updatedAt. Clear GITHUB_TOKEN, GITHUB_TOKEN_NODIFF, and GH_TOKEN with empty assignments if gh reports bad credentials.

How do I map a GitHub PR link back to the Discord user who posted it?

Query the Discrawl sqlite database joining messages and members, filtering on the channel id and a content LIKE match for the PR URL, ordered by created_at descending. Show only the @handle in final output.

When should a contributor PR be closed as already fixed on main?

Only after proving it against current origin/main by inspecting the actual code path and adjacent tests, never from the title alone. Comment first when mutation is requested, and bulk close or reopen above five items requires explicit scope.

What risk markers does the triage output use?

Output uses color markers: green for low or narrow risk, yellow for medium or targeted proof needed, red for broad runtime risk, purple for security or owner-boundary review, plus checkmark for merged and white circle for closed unmerged.