Loading...
Loading...
Found 2,510 Skills
Scoring formulas and analytical frameworks for GitHub workflow agents. Covers repository health scoring (0-100, A-F grades), priority scoring for issues/PRs/discussions, confidence levels for analytics findings, delta tracking (Fixed/New/Persistent/Regressed), velocity metrics, contributor metrics, bottleneck detection, and trend classification. Use when computing scores, tracking remediation progress, building prioritized dashboards, or detecting workflow bottlenecks.
Authenticate to GitHub and fix auth problems — the shared primitive every other github-* skill relies on. Use this BEFORE any create/query when GitHub auth is uncertain, and whenever a GitHub API call misbehaves: a call returns 401 or 403, "gh not logged in" / token missing, results come back empty or from the wrong repo. Covers the two supported methods (gh CLI via `gh auth token`, or GH_TOKEN env var), a one-line PowerShell verify snippet against the repo API, and a 401/403/wrong-repo troubleshooting table. Invoke when someone says "I'm getting a 401 from GitHub", "github-create-issues says no token", "gh auth failing", or "check my GitHub login before we run".
Automated factory for converting GitHub repositories into specialized AI skills. Use this skill when the user provides a GitHub URL and wants to "package", "wrap", or "create a skill" from it. It automatically fetches repository details, latest commit hashes, and generates a standardized skill structure with enhanced metadata suitable for lifecycle management.
This skill should be used when users need to interact with GitHub via the gh CLI. It covers repository management (create, delete, clone, fork), CI/CD workflows (GitHub Actions), Issues, Pull Requests, Releases, and other GitHub operations. Triggers on requests mentioning GitHub, repos, PRs, issues, actions, or workflows.
Automate GitHub operations. Use this skill when you need to manage repositories, create PRs, handle Issues, automate CI/CD, or conduct code reviews.
Exploration and Analysis of GitHub Trending. It is used to discover popular open-source projects, technology trends, and developer preferences, helping to understand the interest trends of the technical community.
GitHub Actions YAML with embedded output contract: security-first, minimal permissions, version pinning. For CI, release, PR checks. Differs from generic templates by spec compliance and auditability.
Standard flow from any task source (link or description) to creating a PR: resolve task, create branch and TODO.md, wait for fixes, create PR against origin only. Use find-skills to discover data-source query methods; after confirmation save to global config so the discovery step can be skipped next time. Use when the user provides a task link/description, asks to 'follow GitHub workflow', or 'create PR from task'.
Create a formal specification for an existing GitHub Actions CI/CD workflow, optimized for AI consumption and workflow maintenance.
Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries.
Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
When the user wants to use GitHub for SEO, parasite SEO, GEO, or create curated lists. Also use when the user mentions "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "repository name," "About section," "GitHub description," "GitHub topics," "GitHub Pages," "GitHub gist," "curated list," or "navigation list."