Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
A skill your agent uses when working on repository operations in this project, including build, test, lint, release, CI alignment, Makefile-driven checks, and operational packaging constraints.
Install Project Ops
$ npx skills add mudrii/openclaw-dashboard --skill project-ops -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mudrii/openclaw-dashboard project-ops --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mudrii/openclaw-dashboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/project-ops .claude/skills/project-ops && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "project-ops" agent skill from https://github.com/mudrii/openclaw-dashboard/tree/main/.codex/skills/project-ops into .claude/skills/project-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-ops", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mudrii/openclaw-dashboard/tree/main/.codex/skills/project-opsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mudrii/openclaw-dashboard --skill project-ops -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mudrii/openclaw-dashboard project-ops --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mudrii/openclaw-dashboard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/project-ops .agents/skills/project-ops && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "project-ops" agent skill from https://github.com/mudrii/openclaw-dashboard/tree/main/.codex/skills/project-ops into .agents/skills/project-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-ops", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mudrii/openclaw-dashboard --skill project-ops -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mudrii/openclaw-dashboard project-ops --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mudrii/openclaw-dashboard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/project-ops .cursor/skills/project-ops && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "project-ops" agent skill from https://github.com/mudrii/openclaw-dashboard/tree/main/.codex/skills/project-ops into .cursor/skills/project-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-ops", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mudrii/openclaw-dashboard.git --path .codex/skills/project-ops--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mudrii/openclaw-dashboard --skill project-ops -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mudrii/openclaw-dashboard project-ops --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mudrii/openclaw-dashboard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/project-ops .gemini/skills/project-ops && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "project-ops" agent skill from https://github.com/mudrii/openclaw-dashboard/tree/main/.codex/skills/project-ops into .gemini/skills/project-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-ops", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mudrii/openclaw-dashboard project-opsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mudrii/openclaw-dashboard --skill project-ops -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mudrii/openclaw-dashboard.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/project-ops .github/skills/project-ops && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "project-ops" agent skill from https://github.com/mudrii/openclaw-dashboard/tree/main/.codex/skills/project-ops into .github/skills/project-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-ops", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mudrii/openclaw-dashboard --skill project-ops -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mudrii/openclaw-dashboard project-ops --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mudrii/openclaw-dashboard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/project-ops .opencode/skills/project-ops && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "project-ops" agent skill from https://github.com/mudrii/openclaw-dashboard/tree/main/.codex/skills/project-ops into .opencode/skills/project-ops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-ops", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
project-ops- GitHub stars
- 457
- Token cost
- ~387 tokens
- SKILL.md length
- 181 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when working on repository operations in this project, including build, test, lint, release, CI alignment, Makefile-driven checks, and operational packaging constraints.
- Working on repository operations in this project
- SKILL.md covers Source Of Truth, Repository Expectations, Change Discipline and Review Focus
- Calls make
- Including build
What it does
Project Ops is an agent skill from mudrii/openclaw-dashboard. Use this skill when working on repository operations in this project, including build, test, lint, release, CI alignment, Makefile-driven checks, and operational packaging constraints.
Its SKILL.md is about 390 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting. The repository describes itself as: A beautiful, zero-dependency command center for OpenClaw AI agents. The licence is MIT.
When your agent uses it
- Working on repository operations in this project
- Including build
- Makefile-driven checks
- Operational packaging constraints
Example prompts
- “/project-ops”
What it can do on your machine
Read from SKILL.md and the folder at commit b63ac25. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
make
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Project Ops loads about 387 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 181 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mudrii/openclaw-dashboard at commit b63ac25, republished under its MIT licence (© mudrii). 181 words, ~387 tokens.
Download SKILL.mdSave it as
.claude/skills/project-ops/SKILL.md (or your agent's skills folder).- name
- project-ops
- description
- Use this skill when working on repository operations in this project, including build, test, lint, release, CI alignment, Makefile-driven checks, and operational packaging constraints.
Project Ops
This is the native Codex operations skill for this repository.
Use it when:
- changing build, test, lint, or check workflows
- editing
Makefileor CI workflows - reviewing release and packaging behavior
- validating commands agents should run in this repo
Source Of Truth
go.moddefines the Go toolchain level.Makefiledefines the preferred local command surface..github/workflows/defines CI expectations.- If these disagree with prose docs, follow code and workflow config first.
Repository Expectations
- Prefer
make build,make test,make lint,make check. - Keep local and CI command surfaces aligned.
- Do not invent commands that the repo does not expose.
- Preserve the zero-dependency bias unless a change explicitly requires otherwise.
- Treat release workflow changes as operational changes that need careful compatibility review.
Change Discipline
- Keep command names stable when possible.
- If command behavior changes, update docs in the same change.
- Prefer small operational changes with obvious rollback paths.
- Do not weaken checks casually to make a change pass.
Review Focus
- command drift between docs, Makefile, and CI
- hidden dependency additions
- missing vet/lint/test coverage in local or CI paths
- release workflow mismatches
© mudrii, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .codex/skills/project-ops of mudrii/openclaw-dashboard.
Open the folder on GitHubat commit b63ac25
Compare with similar skills
Project Ops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Project Ops this skillmudrii/openclaw-dashboard | 457 | — | ~387 | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.2k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Babysit PR To Pass CIsgl-project/sglang | 37k | 2 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Go Pedantrychromedp/chromedp | 13k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Kedro Babysitkedro-org/kedro | 11k | — | ~4k | Automated safety check: Pass | Custom licence |
Similar skills
Babysit PR To Pass CI
sgl-project/sglang
Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
Go Pedantry
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
Kedro Babysit
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
WooCommerce Markdown Guidelines
woocommerce/woocommerce
Rules for writing and editing markdown in the WooCommerce repository, with the project's markdownlint settings for headings, lists and code blocks.
More from mudrii/openclaw-dashboard
Go Rig
mudrii/openclaw-dashboard
A skill your agent uses when building, reviewing, or refactoring Go code that must follow strict design discipline — ATDD/TDD workflow, explicit dependency injection, package-boundary discipline…
Go Rig
mudrii/openclaw-dashboard
A skill your agent uses when building, reviewing, or refactoring Go code in this repository.
Frontend Dashboard
mudrii/openclaw-dashboard
A skill your agent uses when editing the embedded dashboard frontend in this repository.
Go Review
mudrii/openclaw-dashboard
A skill your agent uses when the task is to review Go code in this repository.
Related
Categories
Questions about Project Ops
What does Project Ops do?
A skill your agent uses when working on repository operations in this project, including build, test, lint, release, CI alignment, Makefile-driven checks, and operational packaging constraints. Project Ops is an agent skill from mudrii/openclaw-dashboard. Use this skill when working on repository operations in this project, including build, test, lint, release, CI alignment, Makefile-driven checks, and operational packaging constraints.
When should I use Project Ops?
Project Ops fits situations like: working on repository operations in this project; including build; makefile-driven checks; operational packaging constraints.
How do I install Project Ops in Claude Code?
Run `npx skills add mudrii/openclaw-dashboard --skill project-ops -a claude-code`. Or copy the skill folder (.codex/skills/project-ops in mudrii/openclaw-dashboard) into .claude/skills/project-ops in your project. Claude Code loads it when a task matches its description.
How do I install Project Ops in Codex?
Run `npx skills add mudrii/openclaw-dashboard --skill project-ops -a codex`. Or copy the skill folder (.codex/skills/project-ops in mudrii/openclaw-dashboard) into .agents/skills/project-ops in your project. Codex loads it when a task matches its description.
Can I use Project Ops in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mudrii/openclaw-dashboard --skill project-ops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-ops, .gemini/skills/project-ops, .github/skills/project-ops and .opencode/skills/project-ops in your project.
What does Project Ops need to run?
Going by SKILL.md and its folder, Project Ops needs the command-line tools its instructions call (make).
Does Project Ops access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Project Ops safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Project Ops use?
Project Ops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Project Ops use?
About 387 tokens (SKILL.md is roughly 1.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Project Ops?
Skills that share tags, products or a category with Project Ops: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.2k stars), Babysit PR To Pass CI (sgl-project/sglang, 37k stars), Rust Best Practices (farm-fe/farm, 5.6k stars) and Go Pedantry (chromedp/chromedp, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Project Ops?
mudrii (a GitHub user) maintains it in mudrii/openclaw-dashboard, which has 457 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 23, 2026.
Source: mudrii/openclaw-dashboard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.