Loading...
Loading...
Found 32 Skills
End-to-end open-source contribution for Agent/LLM projects: discover GitHub repos (stars, downloads/usage, recent commits, issue close ratio, PR merge speed, release cadence) and rewrite each project description in the user's language (what it does, problem, scenarios), analyze an Agent/LLM repo, write a scoped PR plan, implement it, open a GitHub PR, then write a PR summary from saved artifacts. Use when the user wants to search for contributable projects, find open source projects, Agent open source, MCP/LangChain repositories, star 1000, GitHub repo search; pastes a GitHub URL for open source contribution analysis, PR direction, good first issue, Agent architecture flaws; asks for technical solution, implement the plan, submit PR with feat/fix/refactor/test/docs; or produce PR summary, summary.md, review submitted PR, pastes a pull request URL / previously mentioned project. Trigger even without the word skill. Do not use for private product feature work or non-Agent general OSS drive-bys.
The worker's router in a repository run by the Boring Factory. Use at the start of every task from a work packet (a task issue, its acceptance lines and their proof): it picks the playbook, the principles and the proof the pull request must carry. Adapted from pstack's poteto-mode.
Propose improvements to a skill in its canonical repository. Defines how to proceed when work does not follow the skill, when information obtained through Web searches differs from or is newer than the skill's content, or when strictly following the skill's conditions is judged to prevent the best possible result. Includes guidance on not directly editing skills installed in the home directory, routing proposals to the appropriate repository, and Issue title and body templates. Use this when you have questions about a skill's content or want to propose an improvement to it.
Use when explicitly asked to deliver an approved GitHub or local spec through a reviewed pull request, or when a Project controller delegates one claimed implementation ticket.
The skill to revert unnecessary changes and leave only essential changes when a user requests a cleanup of changes, or before committing and creating a pull request.
Build an effort by orchestrating sub-agents, and deliver a pull request. Use when asked to build or orchestrate an effort from its spec and tickets.
Pick up an effort from a handoff document and orchestrate it to a pull request.
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.
Use for the full bug-fix pipeline only on explicit request. Never infer from an ordinary bug fix. Runs the compressed pipeline.
Use for the Team pipeline only on explicit request. Never infer from ordinary coding work. Runs QRSPI or a leading route.
Implement or review code through a verified result. Keep changes small and TypeScript readable.
Fully automate building and releasing a coding task.