House Skills plugin
37signals skills in the dev, security, ai and recap plugins: review replies, GitHub Actions hardening, AGENTS.md files, digests.
- 102 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Scripts call GitHub through `gh`, reply in review threads and resolve them.
- The `dev` plugin installs hooks and runs loops of several agents.
Install
- Works in
Manual install
claude plugin marketplace add basecamp/claude-pluginsThen `claude plugin install dev` (or `security`, `ai`, `recap`).
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Scripts call GitHub through `gh`, reply in review threads and resolve them.
- The `dev` plugin installs hooks and runs loops of several agents.
This is third-party code. Review the repository files before installing.
What it does
The 37signals (Basecamp) team working skills come in four plugins. The `dev` plugin works through pull request review comments, replies in threads and resolves them, runs a plan, implement, review loop and sweeps a dependency corpus for one class of latent bug. The `security` plugin fixes zizmor warnings in GitHub Actions and judges changes to sign-in, sessions, two-factor checks and recovery. The `ai` plugin writes and slims `AGENTS.md` files, creates `install.md` and helps build new skills with eval loops. The `recap` plugin gathers activity from Basecamp, git and GitHub into day-cached digests. The `dev` plugin also ships a `pr-worker` subagent that runs one phase of a pull request from a brief and hands off to a fresh agent.
Who it is for. Teams that develop on GitHub and want ready procedures for review, CI hardening and agent instructions.
Good fit when
- A pull request has dozens of comments and each must be fixed, answered in its thread and marked resolved.
- A GitHub Actions workflow raised zizmor warnings and actions must be pinned by hash.
- An `AGENTS.md` file has bloated and it is time to decide what stays in always-on context.
- A team work digest from git, GitHub and Basecamp is needed by Friday.
Not a fit when
- One specific skill is wanted; plugins install in whole groups.
- The project is not on GitHub; some skills rely on `gh`.
- Heavy skills such as the plan, implement, review loop must not run without your request.
Example request
Go through all review comments on pull request 1234: fix them, reply in the threads and mark them resolved, then show what remains open.Limitations
The skills reflect 37signals team processes and assume GitHub and, for digests, Basecamp. Two skills, `ralph-lisa-loop` and `consult-outside-expert`, start only on explicit request: the review loop runs several agents and spends many tokens. The skill on memory leaks in Ruby C extensions is highly specialized. Scripts use `gh` and `jq`, and the `dev` plugin installs hooks, so inspect `hooks.json` before installing. The license is MIT.
How to disable. Run `claude plugin uninstall dev` (and the other plugins) or delete skills installed through `npx skills` from the agent directory.
FAQ
How do I install the plugins in Claude Code?
Run `claude plugin marketplace add basecamp/claude-plugins`, then `claude plugin install dev`. Instead of `dev` you can take `security`, `ai` or `recap`.
How do I install the skills without Claude Code?
With `npx skills add basecamp/house-skills`: skills install as separate folders, while the `pr-worker` subagent stays in the `dev` plugin only.
What does `harden-github-actions` do?
It works through zizmor warnings in workflows, pins actions to SHA, limits permissions and fixes rules such as template injection and cache poisoning.
What is the `recap` skill for?
It gathers per-day activity from Basecamp, git and GitHub into cacheable JSON atoms and writes a digest for the reader. Sources plug in as separate skills.
Why does `skills/` hold duplicate folders?
The real files live in `plugins/<plugin>/skills/`, while the top-level `skills/` directory holds symlinks for a unified view.
Discussion
No questions or reviews yet.
Related
PluginsA skills library for Claude Code, Cursor and Codex: team code review, TDD, stacked PRs and repository readiness scoring
Brooklyn skills: 25 portable agent skills for pull requests, triage, cleanup, UI checks and research
Nine JS Mastery skills take a change through phases: from idea and spec to verification, tests, release texts and a docs sync
Builder Skills
Skills for agents
A set of small skills from Builder.io for agent work habits: visual plans and diff recaps, docs-first checks, cross-agent review and clean status updates
iuhoay/skills collects agent skills: Vanilla Rails, Linear, stacked pull requests, plan challenging and tidy changes.
Seven Go skills from the creator of Cobra and Hugo: idiomatic style, CLI design, releases, Wails, file operations and afero tests
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| House Skills (this card) | no | 102 | |
| 37signals Rails Skills | no | 732 | unofficial skills on Rails style from open 37signals code; this is the team official set for review, CI and digests |
| Basecamp CLI | yes | 299 | the official Basecamp CLI with Claude Code plugins; this holds development and security skills with Basecamp as a digest source |
README in short
The repository publishes internal 37signals procedures as portable skills. The structure is checked by the `validate-structure` and `validate-heavyweight-skill-activation` scripts, and `address-pr-reviews` has test fixtures.