Loading...
Loading...
Found 2,521 Skills
ALWAYS LOAD THIS SKILL WHEN RESEARCHING AN UPSTREAM PACKAGE OR HOSTED REPOSITORY SUCH AS GITHUB OR GITLAB FOR SOURCE CODE, ISSUES, REFS, RELEASES, OR COMMIT HISTORY. Do not assume web-only research is enough before reading this skill.
Triage, redact, clean up, and resolve OpenClaw GitHub Secret Scanning alerts in issues or PRs.
Generate beautiful Excalidraw diagrams from natural language. Diagrams that "argue visually" — built-in Playwright visual validation loop, brand-customizable palette, and 3.2k+ GitHub stars. By coleam00.
Pre-build reality check for AI coding agents — scan GitHub, HN, npm, PyPI, Product Hunt to validate ideas before building
Compare React Doctor diagnostics for a GitHub pull request (PR) with Daytona. Use when asked to run parity, check a PR for diagnostic regressions, compare a PR with its base, or report added and removed diagnostics.
Audit the OpenSSF Scorecard rating for py-lintro. Use when asked to check the scorecard, understand the rating, or find what's missing. Specific to github.com/lgtm-hq/py-lintro.
🇺🇸 Open-Source Marketing & GitHub Stars Growth System — Decision framework for each growth stage. Pre-launch readiness → Show HN / Reddit / Product Hunt launch → 6-month growth loop. README rules, KOL outreach, dev-content matrix (dev.to / Zenn), anti-star-farming. Built from taking AFFiNE 0 → 60K stars. 🇨🇳 开源营销与 GitHub Star 增长系统 — 每个增长阶段的决策框架。Pre-launch 就绪 → Show HN / Reddit / Product Hunt 发布 → 6 个月增长循环。README 规则、KOL 合作、开发者内容矩阵（dev.to / Zenn）、防刷 star。提炼自 AFFiNE 0 → 60K star 实战。 🇯🇵 オープンソースマーケティング＆GitHub スター成長システム — 各成長段階の意思決定フレームワーク。Pre-launch → Show HN / Reddit / Product Hunt → 6ヶ月成長ループ。READMEルール、KOL連携、開発者コンテンツマトリックス。 🇰🇷 오픈소스 마케팅 & GitHub 스타 성장 시스템 — 각 성장 단계별 의사결정 프레임워크. 사전 출시 → Show HN / Reddit / Product Hunt → 6개월 성장 루프. README 규칙, KOL 아웃리치, 개발자 콘텐츠 매트릭스. Triggers: "open source marketing" | "GitHub stars" | "star growth" | "Show HN" | "Hacker News launch" | "OSS launch" | "developer marketing" | "Reddit launch" | "dev.to" | "open source growth" | "开源营销" | "GitHub star 增长" | "开源发布" | "Show HN 怎么发" | "开发者营销" | "オープンソース" | "오픈소스 성장"
Prepare a conventional branch, write or review a pull/merge request title and body, then push and create or update the GitHub PR. Use when work is ready for review or PR/MR copy needs drafting or review.
Resolve GitHub PR review feedback with source-backed triage, fixes, autogoal plan state, focused proof, replies, and thread resolution.
Open a ready-for-review GitHub pull request for completed local changes, including any needed commit and push.
Manage GitHub repositories: create/settings, split, combine, monorepo moves, architecture review, CI harden/simplify, and secrets (Pulumi ESC by default). Use when the user says repos, `/repos <command>`, wants to carve or join repos, redesign monorepo layout, harden workflows, or set up secrets without long-lived GitHub Actions secrets. Mutating GitHub/Pulumi/cloud requires explicit approval.
You MUST use this before running a project-scoped GitHub CLI command (gh pr, issue, repo, api, release, run) against github.com, again before every later gh command in the same session, after a gh command fails with an access error such as "Could not resolve to a Repository", and when asked to check or switch the gh account for the current project. It switches gh to the already logged-in account named by GH_ACC in the project's .env/.env and reports the switch in one line. Not for plain git or SSH operations, gh help or version output, logging in, or hosts other than github.com.