Loading...
Loading...
Found 39 Skills
Generate and publish blog posts from any project to kelegele/agent-blog. ZERO DEPENDENCIES — does NOT require Node.js, pnpm, git, or any local build tools. Works with only a browser and a GitHub token. Triggers on: "写篇博客", "blog this", "发博文", "publish blog", "把项目写成文章", "写篇文章", "blog it", "post article", "新文章", "new blog post", "blog this project", "发一篇博文", "写一篇博文", "blog post about this", "edit blog post", "修改文章", "更新博文", "edit article". Collects project context, collaborates on outline, writes Markdown with correct frontmatter, validates article format, generates a standalone HTML preview by reading live blog source, manages draft/review/publish flow. Pushes to kelegele/agent-blog main branch. Vercel auto-deploys on push. Use this skill whenever the user expresses intent to write about their current work as a blog post.
Full GitHub API integration — 26 tools for repos, issues, PRs, branches, commits, releases, Actions, files, gists, and codebase indexing.
GitHub API operations - repositories, issues, pull requests, actions, code security, discussions, gists, and more. Use for GitHub-related tasks like managing PRs, issues, searching code, and monitoring workflows.
GitHub data collection patterns for workflow agents. Covers search query construction by intent, date range handling, repository scope narrowing, preferences.md integration, cross-repo intelligence, parallel stream collection model, and auto-recovery for empty results. Use when building agents that search GitHub for issues, PRs, discussions, releases, security alerts, or CI status.
GitHub via Composio API. Use when: (1) Reading repository contents, README, or downloading repos (2) Creating, updating, or listing issues (3) Creating, listing, or merging pull requests (4) Listing repositories or branches DO NOT use `gh` CLI - it will fail with auth errors. Use Composio HTTP API only.
Pick a random contributor from a GitHub repository using the GitHub API or repository pages (no auth required for public repos).
This is used to review comments on an active pull request and decide whether to accept, iterate, or reject the changes suggested in each comment.
Create, triage, label, assign GitHub issues via gh or REST.
Work with Git repositories from the command line.
Triage unresolved PR review comments, produce a severity-ordered fix plan, then resolve or fix each issue with subagents. Use when addressing PR feedback before merge.
GitHub CLI operations via `gh` for issues, pull requests, CI/Actions, releases, repos, search, gists, and the REST/GraphQL API. Structured output with `--json` and `--jq` for parsing. Covers `gh issue create/list/view/edit/close`, `gh pr create/review/merge/checks`, `gh run list/view/rerun/watch`, `gh release create`, `gh search repos/issues/prs/code`, `gh api` for REST and GraphQL queries, and `gh gist` operations. Includes error handling for HTTP 401/403/404/422/429, scope troubleshooting, and rate limit management. Trigger phrases: "create an issue", "file a bug", "open a ticket", "submit a PR", "raise a pull request", "check pipeline", "view test results", "CI failing", "why did CI fail", "check CI status", "merge a PR", "manage releases", "query the GitHub API", "search repositories", "triage workflows", "automate GitHub operations". Also triggers when the user pastes a GitHub URL.
Emulated GitHub REST API for local development and testing. Use when the user needs to interact with GitHub API endpoints locally, test GitHub integrations, emulate repos/issues/PRs, set up GitHub OAuth flows, configure GitHub Apps, test webhooks, or work with actions/checks without hitting the real GitHub API. Triggers include "GitHub API", "emulate GitHub", "mock GitHub", "test GitHub OAuth", "GitHub App JWT", "local GitHub", or any task requiring a local GitHub API.