OK Skills – Re‑usable AI‑agent “skills” for Codex, Claude Code, Cursor, OpenClaw and friends

What it is – A curated collection of 31 skill directories that can be dropped into the ~/.agents/skills/ok‑skills folder (or the equivalent Autohand Code location). Each skill is a self‑contained set of instructions (SKILL.md) and any helper scripts that an AI‑coding‑assistant can invoke. The repo also ships a CLAUDE_AGENTS.md playbook that can be merged into a tool’s CLAUDE.md / AGENTS.md file, giving the agent a ready‑made menu of capabilities.

Who it helps – Developers who already use an AI‑coding‑agent (Codex, Claude Code, Cursor, OpenClaw, Autohand Code, Trae, etc.) and want a library of battle‑tested, plug‑and‑play actions instead of writing ad‑hoc prompts each time. It is also useful for teams that maintain a shared AGENTS.md workflow and need portable, version‑controlled skill definitions.

How to get started

mkdir -p ~/.agents/skills
cd ~/.agents/skills
git clone https://github.com/mxyhi/ok-skills.git ok-skills

or clone into the Autohand Code skill folder (~/.autohand/skills or .autohand/skills). After cloning the directory layout already matches what the agents expect:

~/.agents/skills/ok-skills/
  CLAUDE_AGENTS.md
  planning-with-files/SKILL.md
  find-docs/SKILL.md
  agent-browser/SKILL.md
  …

Add the skill names to your AGENTS.md (or CLAUDE.md) under a Skills section, e.g.:

## Skills
- planning-with-files: use for complex, multi‑step tasks
- find-docs: fetch up‑to‑date library docs
- agent-browser: automate browsers, take screenshots, scrape pages

Then you can simply ask the agent:

“Use planning‑with‑files before refactoring this module.” “Use find‑docs to get the latest SDK docs.” “Use agent‑browser to reproduce this UI bug.”

What’s inside – The skills are grouped by typical use‑cases:

• Research & Docs – find-docs, exa-search, get-api-docs, ax.
• Planning & Prompting – planning-with-files, autoresearch, diagnosing-bugs, karpathy-guidelines, tdd.
• Automation & QA – agent-browser, kimi-webbridge, browser-trace, opencli.
• Frontend & Design – ai-elements, huashu-design, imagegen-frontend‑web, gpt-taste, better‑icons, diagram‑design.
• Utilities & Authoring – various helpers for icon lookup, diagram generation, etc.

Each skill’s SKILL.md contains:

• A short description and when to invoke it.
• Any required external tools (e.g., gh authentication, Chrome/Playwright for browser work, pip install playwright).
• Trigger rules that can be copied into your global agent config.

Why it matters – AI‑coding agents are only as useful as the tooling they can call. By providing a standardized, version‑controlled set of skills, ok‑skills lets teams share best‑practice workflows (e.g., “plan‑with‑files → fetch docs → run browser automation”) without reinventing the prompt each time. The repo also tracks upstream sources for each skill, so updates can be pulled from the original projects while keeping the local layout stable.

Prerequisites – Most skills assume you have:

• The target AI‑coding agent installed (Codex, Claude Code, etc.).
• A recent git and, for many browser‑related skills, a Chrome/Chromium environment with the Chrome DevTools Protocol (CDP) available.
• Optional CLIs (gh, exa, Context7, etc.) as noted in individual SKILL.md files.

---

All details are taken directly from the repository’s README; no additional features are inferred.