Oz Skills
Fifteen skills from Warp: CI repair, pull requests, accessibility and SEO audits, web app testing and issue triage
- 823 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- `ci-fix` pushes changes to a repository branch through GitHub
- `create-pull-request` opens a pull request on your behalf through `gh`
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/oz-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- `ci-fix` pushes changes to a repository branch through GitHub
- `create-pull-request` opens a pull request on your behalf through `gh`
This is third-party code. Review the repository files before installing.
What it does
Oz Skills collects fifteen ready skills in `.agents/skills/`, one folder per skill. The agent picks such a folder up itself when the task matches the description in `SKILL.md`. Developers get `ci-fix`, which reads GitHub Actions logs and pushes a minimal fix to a separate branch, `create-pull-request` with commit analysis and pull request creation through `gh`, `github-bug-report-triage` and `github-issue-dedupe` for sorting issues, `docs-update` and `terraform-style-check`. Web projects have `web-accessibility-audit` with WCAG and ARIA references, `web-performance-audit`, `seo-aeo-audit` and `webapp-testing` with Python examples. The rest cover one-off jobs: `mcp-builder` for creating MCP servers, `dbt-model-index`, `analysis-artifacts`, `scheduler` and `slack-qa-investigate`.
Who it is for. Teams working with Warp and Oz agents who want ready skills for CI, pull requests and audits instead of writing them from scratch.
Good fit when
- A GitHub Actions build went red and you need the cause diagnosed with a minimal fix on a separate branch
- Changes are ready and the agent must prepare the branch, commits and pull request description by project rules
- A stream of bug reports arrives in the tracker, many of them duplicates
- Before a release the pages need an accessibility pass based on WCAG and ARIA
- An MCP server has to be built to best practices on Node or Python
Not a fit when
- You need one specific skill: it is easier to copy only its folder from the set
- The project lives outside GitHub, but `ci-fix` and `create-pull-request` rely on Actions and `gh`
- The team has strict pull request conventions that differ from the skill template
Example request
Check why the latest CI run failed, find the cause from the logs and put a minimal fix on a separate branchLimitations
The author does not describe the `npx skills add warpdotdev/oz-skills` command: it is generic for repositories with SKILL.md, while the README says to copy the folder by hand. The skills are written for Warp and Oz agents and should be tested separately in other agents. `ci-fix` and `create-pull-request` need an authenticated GitHub CLI and write access to the repository. `webapp-testing` runs Python scripts and starts a local server. The last commit in the repository was made in August 2026.
How to disable. Delete the folder of the skill from `.agents/skills/` in the project or from `~/.agents/skills/` for a global install.
FAQ
Where do I put Oz skills for one project and for all projects?
For one project copy the skill folder into `.agents/skills/` inside it, for all projects into `~/.agents/skills/`. The agent finds the skill on the next request, no restart needed.
What does ci-fix do when a build fails?
It reads GitHub Actions runs and logs, finds the cause and makes a minimal fix. The result goes to a separate branch and no pull request is created: `create-pull-request` prepares it.
Which skills help a website rather than code?
For pages use `web-accessibility-audit` with the `run-eslint.sh` script, `web-performance-audit` and `seo-aeo-audit`. The last one includes JSON-LD templates and scripts for Lighthouse, PageSpeed and Search Console export.
Is there a skill for creating an MCP server?
Yes, `mcp-builder` with a best practices guide, Node and Python examples and a section on evaluating a server. The folder carries its own license, so check the terms before reuse.
Do the skills work outside Warp?
The SKILL.md format is shared across agents, but the set was built for Warp. In Claude Code or Codex a skill moves by copying its folder, and its behavior is worth checking on one task.
Discussion
No questions or reviews yet.
Related
Skillscommon-skills by Warp
common-skills
Warp skills for team development: specs, PR descriptions and reviews, failed CI diagnosis and merge conflict resolution
Nine JS Mastery skills take a change through phases: from idea and spec to verification, tests, release texts and a docs sync
Dozens of mizchi's agent skills: frontend audits, AWS, Cloudflare, SQL, Playwright and OpenTelemetry, installed one by one
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
A set of skills from real work: npm supply-chain audit, CLI building, Obsidian plugin release and an AGENTS.md hierarchy
A set of independent skills against drift in large codebases: hard-cut, root-cause tracing, lean testing and CI right-sizing.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Oz Skills (this card) | yes | 823 | |
| Vercel skills for agents | no | 33,572 | a Vercel set for web development, with no CI, pull requests or issue triage |
| Agent Skills by Addy Osmani | no | 113,521 | a set of engineering practices by Addy Osmani, while Oz Skills is tied to GitHub and Warp |
README in short
The README explains what agent skills are, where they live and how Warp agents pick them up automatically. Then come the folder copy steps, a link to contribution rules and a description of the format.
README badge
Original SKILL.md
--- name: ci-fix description: Diagnose and fix GitHub Actions CI failures. Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch. Use when CI is failing, red, broken, or needs diagnosis. license: MIT --- # CI Fix Diagnose CI failures and implement fixes with minimal, targeted diffs. Pushes fixes to a dedicated branch without creating PRs. ## Prerequisites Verify GitHub CLI authentication before proceeding: ```bash gh auth status ``` If not authenticated, instruct the user to run `gh auth login` first. ## Workflow ### 1. Locate the Failing Run Determine the failing workflow run. If working on a PR branch: ```bash gh pr view --json statusCheckRollup --jq '.statusCheckRollup[] | select(.conclusion == "FAILURE")' ``` If working from a branch or run ID: ```bash gh run list --branch <branch> --status failure --limit 5 gh run view <run-id> --verbose ``` ### 2. Extract Failure Logs Pull logs from failed steps to identify the root cause: ```bash gh run view <run-id> --log-failed ``` For deeper inspection: ```bash gh run view <run-id> --log --job <job-id> gh run download <run-id> -D .artifacts/<run-id>