skillboardUpdated every 6 hours
skillboardUse gh for GitHub issues, PR status, CI/logs, comments, reviews, releases, and API queries.
When to use Use this skill when the user asks anything about GitHub: issues, pull requests, CI runs, releases, comments, code review, or organizational metadata. Prefer the CLI over web URLs — handles auth, pagination, and structured output natively. Common commands When NOT to use The user's repo is on a non GitHub forge (GitLab, Gitea, Bitbucket). Use the appropriate CLI instead. Operations that require admin permissions the agent doesn't have.
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/real · pinned to the source commit
git clone https://github.com/openclaw/openclaw.git
cd openclaw
git checkout b1e27db51ce36bc26669f6a00d7990908a481ff6
mkdir -p ".claude/skills/real"
cp -r "extensions/oc-path/src/oc-path/tests/fixtures/real" ".claude/skills/real"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit b1e27db51ce3. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.