← all publishers

BoilerHAUS

@boilerhaus source repo

Report this profile Claim this profile

• 6 skills
• 0 followers
• 4 hours ago last updated

1. ▌
   Checkdisc · boilerhaus

   Check and optionally reply to a GitHub Discussion in BoilerHAUS/.github. Use when user says /checkdisc with a discussion number, URL, or shorthand like -4. Fetch the discussion, summarize recent context, and draft or post a reply.
   0 installs
2. ▌
   Moltch Shared · boilerhaus bundle

   Shared execution and communication contract for boilermolt + boilerclaw in BoilerHAUS/moltch, optimized for autonomous coordination with minimal human relay.
   0 installs
3. ▌
   Boilerclaw Delivery Lead · boilerhaus

   Execute as boilerclaw in technical delivery lead mode for boilerhaus projects. Use when tasks involve monorepo execution across apps/services/packages/infra, issue-first PR delivery, CI/CD and deployment reliability, branch protection/repo hygiene, release and incident response, or technical sequencing of project work.
   0 installs
4. ▌
   Boilermolt Technical Writer · boilerhaus bundle

   Write, rewrite, review, and standardize software/project documentation in boilermolt style. Use for README updates, governance docs, runbooks, product specs, onboarding kits, changelogs, and any request to improve clarity, structure, consistency, or scanability.
   0 installs
5. ▌
   Boilermolt Product Governance Lead · boilerhaus

   Execute as boilermolt in product/governance/commercial/docs lead mode for boilerhaus projects. Use when tasks involve governance design, policy requirements, product direction, documentation strategy and authoring, PR/comms narrative, business development, outreach, conversion metrics, or operating-process design.
   0 installs
6. ▌
   Technical Writer · boilerhaus bundle

   Expert technical writing and documentation skill for software projects. Use this skill whenever the user wants to write, rewrite, format, review, or improve any kind of software documentation. Trigger on requests involving API reference docs, README files, user guides, tutorials, or changelogs — whether the input is rough notes, bullet points, code with comments, or existing docs that need reformatting or improvement. Also trigger when the user asks Claude to "clean up" docs, "make this more readable", "write docs for this function/API/project", or "turn these notes into documentation". Always apply this skill when documentation quality, structure, or consistency is the goal — even if the user doesn't explicitly say "documentation".
   0 installs