Loading...
Loading...
Found 1,624 Skills
Security vetting for AI agent skills. Use before installing any skill from ClawHub, GitHub, or other sources.
Create Linear tickets or GitHub issues following n8n conventions. Use when the user asks to create a ticket, file a bug, open an issue, or says /create-issue.
GitHub Local Knowledge Base Manager and Query Assistant. This skill must be triggered when users mention github, repo, repository, warehouse, download repo, clone, copy repository, PR, issue, pull request, or any content related to GitHub projects. This skill knows the location of local repos, can clone new repos, and uses gh CLI to search issues, PRs, and repositories to answer questions. Use proactively—even if users just ask "Which repos do I have" or casually mention a GitHub account or project name.
Analyze a GitHub issue and create a detailed technical specification
Create a new GitHub repository and clone it locally
Fix GitHub Actions failures by analyzing recent workflow runs and applying fixes in a worktree
Fork a GitHub repo and clone it locally with proper remote setup
Handle a GitHub Security Advisory response for Paperclip, including confidential fix development in a temporary private fork, human coordination on advisory-thread comments, CVE request, synchronized advisory publication, and immediate security release steps.
Run a retrospective after generating a CLI. Identifies systemic improvements to the Printing Press — templates, Go binary, skill instructions, catalog — so the next CLI comes out better. Creates a GitHub issue with actionable findings when there are Printing Press fixes to make. Use after any /printing-press run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings".
Turn a GitHub issue into an implementation plan — investigate the codebase, propose an approach, list critical files and changes, outline test strategy. Use when user says 'plan this issue', 'what's the approach for', 'how would I tackle', 'implementation plan for', or 'before coding'. Do NOT use for actually implementing (write the code directly after the plan) or for breaking a too-large issue into sub-issues (use splice-issue).
GitHub repository analytics dashboard — stars, forks, contributors, issues, pull requests, recent activity, and top contributors. Use when the brief asks for a GitHub repo dashboard, open-source growth report, repository health page, or GitHub analytics view.
Read a GitHub Issue, create a detailed plan in `_/local-plans/<issue-number>-<slug>.md`, and implement the code **after user approval**. After implementation, perform a security review (OWASP Top 10) → run tests → commit using Conventional Commits. Used for implementation requests where an Issue number or URL is provided, such as "Implement Issue #N" or "Start working on this Issue".