THE SKILLS COLLECTION
Your next useful skill.
Start with a task, then find a guide to install and use the Skill.
to-tickets
Split a plan into small, end-to-end tasks with acceptance criteria and explicit blocking dependencies.
Github
Read a PR’s draft, review and check status in OpenClaw, then follow the correct run when a check needs investigation.
to-spec
Turn requirements and technical decisions already settled in the conversation into a specification in the configured project tracker.
agent-browser
agent-browser organizes browser tasks around observing the page, selecting an element, acting and checking again. Install both the discovery skill and the CLI/browser runtime before expecting it to control a page.
skill-creator
Define triggers and outputs, then improve a skill through realistic tasks, baseline comparisons, and feedback.
expo-data-fetching
Handle Expo requests, caching, authentication, offline behavior, and failed saves with explicit loading states.
expo-router
Organize Expo screens with file-based routes, layouts, parameters, native stacks, and deep links.
implement-spec
Implement a ticketed spec in parallel and collect the work on one integration branch.
schema
Choose appropriate entities, generate JSON-LD from visible facts, and verify the deployed result.
site-architecture
Plan hierarchy, navigation, URLs, and internal links while accounting for existing pages during a redesign.
diagnosing-bugs
Build a repeatable signal for the exact failure, narrow the reproduction, test hypotheses and verify the fix.
improve-codebase-architecture
Survey costly code structure, present refactoring candidates visually and explore the option you choose.
resolving-merge-conflicts
Resolve an in-progress merge or rebase using the intent recorded in commits, pull requests and requirements, then run checks and finish the operation.
tdd
Agree where behavior will be observed, then alternate one failing test with the smallest implementation that passes it.
expo-dev-client
Choose and configure a native development build, separating native rebuilds from everyday JavaScript updates.
expo-upgrade
Align dependencies, handle native projects and deprecated APIs, and verify important behavior during an Expo SDK upgrade.
gh-address-comments
Collect comments and review threads on the current branch’s PR, then implement the changes you select. This guide covers the standalone version retained in a deprecated repository.
gh-fix-ci
Inspect failing PR checks and Actions logs, propose a repair and verify the change. This guide covers the standalone version retained in a deprecated repository.
playwright
Use Playwright CLI to navigate, fill forms and capture evidence from real website interactions. This guide covers the standalone version retained in a deprecated repository.
security-best-practices
Review Python, JavaScript/TypeScript and Go projects using language- and framework-specific security guidance. This guide covers the standalone version retained in a deprecated repository.
security-ownership-map
Map people to files from Git history and inspect maintenance concentration, handoff gaps and co-changing code. This guide covers the standalone version retained in a deprecated repository.
security-threat-model
Identify assets, entry points, trust boundaries and abuse paths from repository evidence. This guide covers the standalone version retained in a deprecated repository.
sentry
Use the sentry CLI for read-only issue and event investigation, scoped to the real project, environment and time window. This guide covers the standalone version retained in a deprecated repository.
vercel-react-best-practices
Review React and Next.js performance with waterfalls and bundle size ahead of smaller rendering optimizations.
vercel-react-native-skills
Review React Native lists, row stability, images, animations, and native navigation.
vercel-composition-patterns
Replace growing boolean options with explicit component variants and clear shared-state boundaries.
grill-with-docs
Clarify a design through an interview while capturing project terminology and important decisions for later development.
domain-modeling
Clarify ambiguous business concepts, capture settled terminology in CONTEXT.md and record meaningful architectural decisions.
code-review
Review a committed Git diff separately against repository standards and the feature specification.
webapp-testing
Use Python Playwright to check a local application and capture screenshots and browser errors.
web-artifacts-builder
Build a multi-component React artifact, then bundle it into a shareable HTML file.
mcp-builder
Develop an MCP server through API research, tool design, implementation checks, and realistic evaluations.
writing-plans
Convert an approved design into implementation tasks with file locations, interfaces, tests, and evidence.
verification-before-completion
Run the checks that support a completion claim and inspect their full results before reporting success.
using-git-worktrees
Detect existing worktrees, create or reuse an isolated checkout, and establish a test baseline.
test-driven-development
Develop a feature or fix through a failing test, minimal implementation, and refactoring while tests pass.
systematic-debugging
Investigate defects through reproduction, comparison, a single hypothesis, and regression verification.
receiving-code-review
Understand and verify review comments before implementing, clarifying, or challenging them with code evidence.
brainstorming
Choose an appropriate discovery path and turn a rough idea into an agreed design before implementation.