Loading...
Loading...
Found 10,387 Skills
Orchestrate same-repository GitHub issue work from branch setup through local review and PR readiness. Use when the user invokes `/develop-issue #123`, `/develop-issue https://github.com/<owner>/<repo>/issues/123`, or asks to develop exactly one issue end to end.
Run a read-only, fresh-context branch-diff code review and report findings. Use when running /review-code, before finishing issue work, or when a local review gate should inspect committed, staged, unstaged, and untracked changes without mutating code or GitHub state.
Use skill if you are running many small Codex-native web searches through codex exec with per-question files and parseable answer artifacts.
Create a pull request in a mitodl GitHub repository using the org's standard PR template. Triggered by /olpr or whenever the user asks to open a pull request in a repo whose remote is under the mitodl GitHub organization. Guides branch inspection, title/body population, and gh pr create invocation.
Use when the user wants to auto-syndicate their latest 微信公众号 article across social platforms — picks the newest un-syndicated article, extracts one core copy, auto-posts to API platforms (X / Bluesky / Threads / LinkedIn) and prepares a copy-paste outbox for manual platforms (Facebook / 小红书 / 即刻 / 知乎). Triggers — "分发文章到各平台", "同步到社交平台", "今天的文章发各平台", "/wjs-syndicating-articles".
Use this skill when the user says "/li", or when the request is related to content creation but the intent is ambiguous and the user is unsure which tool to use. As the main entry point of the li Toolkit, it judges the intent and routes to the corresponding specialized skill. Do NOT trigger: When the user's request clearly matches a specific li-* skill (e.g., "write a script" → li-writer, "deepen a topic" → li-topic), directly trigger the corresponding skill instead of this entry. DO NOT trigger for non-content-creation tasks. Use when the user says "/li" or the intent is ambiguous across multiple li-* tools.
Use when the user asks you to start, join, or continue a conversation with other agents via chatter, agent-chat, or talking to other agents about X.
Comet Phase 4: Verification and Wrap-up. Invoke with /comet-verify. Verify that implementations comply with designs and handle development branches.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Use this when users need to collect research materials for an article or topic by gathering YouTube videos and web articles into a NotebookLM notebook, then running analysis queries and saving the results as markdown. It is ideal for requests like "collect materials", "find relevant videos and articles on this topic for me", and "organize for NotebookLM analysis". This skill combines yt-dlp YouTube search, NotebookLM `nlm` CLI research, and markdown report output.
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Also trigger when the user wants feedback on code changes, wants to approve or request changes on a PR, or asks to review someone's contribution.