tools
Utility commands — commit, compile, validate-bib, journal, context-status, deploy, learn. Replaces individual utility skills.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill tools --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Tools Utility subcommands for project maintenance and infrastructure. **Input:** `$ARGUMENTS` — subcommand followed by any arguments. --- ## Subcommands ### `/tools commit [message]` — Git Commit Stage changes, create commit, optionally create PR and merge. - Run git status to identify changes - Stage relevant files (never stage .env or credentials) - Create commit with descriptive message - If
What does the tools skill do?
Utility commands — commit, compile, validate-bib, journal, context-status, deploy, learn. Replaces individual utility skills.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill tools --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.