Loading...
Loading...
Found 12 Skills
Track deep work sessions locally (start/stop/status) and generate a GitHub-contribution-graph style minutes-per-day heatmap for sharing (e.g., via Telegram). Use when the user says things like “start deep work”, “stop deep work”, “am I in a session?”, “show my deep work graph”, or asks to review deep work history.
This skill should be used when the user asks to "create a pull request", "create PR", "open PR", "update a pull request", "update PR", "create an issue", "file an issue", "create a GitHub issue", "create a Claude Code issue", "report a bug in Claude Code", "create a Codex issue", "report a bug in Codex CLI", "create a Sablier issue", "file an issue in sablier-labs", "create a discussion", "start a GitHub discussion", "yeet a PR", "yeet an issue", "yeet a discussion", or mentions GitHub contribution workflows.
GitHub Open Source Contribution Assistant Skill: Find active projects based on target companies and positions, prioritize scanning for opportunities like typos, READMEs, Markdown files, broken links, and formatting issues. First display candidates and modification plans, complete verification, then perform fork, push, and submit PR only after explicit confirmation from the user. After the PR is merged, transform the contribution graph into resume materials usable by /asu. This skill is triggered when the user inputs "/contributor", wants to make their first contribution, looks for small open-source tasks, or intends to include PRs in their resume.
Summarize weekly GitHub contributions for writing weekly reports
Expert guidance for contributing to and using the Awesome Claude Code repository, a curated collection of Claude Code skills, agents, hooks, and resources.
One-click contribution flow for Open Design (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship my OD skill, ship my OD design system, translate OD docs, report an OD bug, od-contribute.
Scout issues for OSS Contribution
Strategic guide for becoming an effective GitHub contributor. Covers opportunity discovery, project selection, high-quality PR creation, and reputation building. Use when looking to contribute to open-source projects, building GitHub presence, or learning contribution best practices.
Research and extract an engineer's coding style, patterns, and best practices from their GitHub contributions. Creates structured knowledge base for replicating their expertise.
Contribute to HITSZ OpenAuto (HOA) — the HITSZ course-sharing project. Use when the user wants to upload course materials, edit a course page, update grade composition, add a new course or course-code mapping, or write a blog post on hoa.moe.
Keep the project tables in mmontes11/contributions current: scrape mmontes11's GitHub star lists, compute the delta against the README's tracked tables, score only the new repos against the repo's #scoring rubric, rebuild only the touched category tables, and commit a small diff directly to main. Use whenever the user wants to refresh, update, or re-score the contributions tracking — "update the contributions tables", "re-run the contributions scrape", "refresh mmontes11/contributions", "score the new repos in the contributions repo" — and for the scheduled runs driven by the Contributions autopilot.
Evaluate, prepare, and review contributions to GitHub repositories the user does not own, including discussions, issues, private vulnerability reports, and pull requests. Use it when incorporating feedback or findings into a contribution, preparing the next pull request in a contribution series, or making user-requested revisions to an existing pull request, including maintainer feedback after submission. Do not use for routine work in the user’s own repositories or ongoing monitoring after submission.