oss-contributor

What This Skill Does

The oss-contributor skill transforms your OpenClaw agent into an autonomous open-source maintainer. It periodically scans designated GitHub repositories for issues tagged with specific labels like 'good-first-issue', 'help-wanted', or 'documentation'. Once an issue is identified, the agent evaluates its complexity, generates a code fix, creates a fork if necessary, and submits a pull request—all while adhering to GitHub API standards. It is designed to run in the background, allowing your agent to contribute to the open-source ecosystem, improve codebases, and maintain activity on your GitHub profile during idle processing cycles.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/kbo4sho/oss-contributor

Ensure your GH_TOKEN environment variable is configured with appropriate repository permissions. The skill will automatically attempt to load configuration settings from ~/clawd/oss-contributor.json or a local ./oss-contributor.json file. If no file is present, it will rely on default CLI flag settings.

Use Cases

• Automated Open Source Growth: Maintain a consistent GitHub contribution graph by automating small bug fixes and documentation improvements.
• Community Maintenance: Help library maintainers clear out their backlog of 'good-first-issue' tickets without manual intervention.
• Idle Productivity: Utilize your agent's compute time for community service when not engaged in primary tasks.
• Automated Triage: Use it as a discovery tool to find trending repositories matching your specific interests or tech stack.

Example Prompts

1. '/oss-contributor --repos openclaw/openclaw --labels good-first-issue --limit 3 --auto'
2. '/oss-contributor --discover --languages typescript --max-complexity low'
3. '/oss-contributor --dry-run --notify-channel -1002381931352'

Tips & Limitations

• Safety First: Always use --dry-run when testing the skill on new repositories to verify the agent's proposed changes before making them public.
• Rate Limiting: Be mindful of GitHub API rate limits. The agent uses the REST API exclusively, so ensure your token has sufficient scope.
• Complexity: The agent is best suited for low to medium-complexity issues. It may struggle with large-scale architectural refactors; always review its output on sensitive projects.
• Configuration: Maintain a strict blocklist to prevent the agent from attempting commits to protected or private company repositories.