Loading...
Loading...
Found 3,748 Skills
A step-by-step practice tool for LeetCode medium-difficulty interview questions. It is triggered when users want to practice algorithm problems, brush up on LeetCode, prepare for technical interviews, or say "Give me a problem", "Next problem", "Generate scaffold", "Start practicing". It supports categorized practice by problem type (DP, Linked List, Tree, Graph, Sliding Window, Two Pointers, Hash Table, Binary Search, Stack, Heap, Backtracking, Interval, String, Union Find), generates Python scaffolds with test cases for each problem, tracks learning progress via Markdown tables, and guides users to think independently before providing solutions. It supports the goal of 3 problems per day, counts progress via `git diff README.md` and submits to Git.
This skill should be used when a user wants to create, draft, or plan a GitHub Epic issue — for example "write an epic", "I want to define a new initiative", "scope out this strategic project", "turn this idea into an epic", "plan work that spans multiple features", or "start from a bounded context". Also use when the user asks to define domain outcomes, capture a large initiative before breaking it into features, or describe work in terms of business goals rather than technical tasks.
Companion CLIs for Runpod workflows — HuggingFace, GitHub, Docker, and AWS.
Use when a GitHub Pull Request needs review-thread reply and resolve handling, findings ingestion, and a mandatory final gate in one PR-scoped session.
Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform maintainer-style PR decision making before merge or closure.
Ship a new dtctl release — bump version, write changelog entries, run tests, commit, tag, push, and write GitHub release notes. Use this skill whenever the user says "release", "ship it", "cut a release", "new version", "bump version", "publish", or asks about the dtctl release process. Also use when the user wants to update CHANGELOG.md for a release or write GitHub release notes.
Automate the full release lifecycle — version bump, changelog, README update, git tag, GitHub release, and PyPI/npm publishing. Use this skill whenever the user wants to cut a release, bump a version, tag and push, create a GitHub release, generate release notes or a changelog, publish to PyPI or npm, or asks what changed since the last release. Even if the user just says ship it, make a release, or tag this version — this skill should handle it. Don't use for routine commit/push, opening PRs, or publishing to VS Code Marketplace/App Store (use the dedicated skills).
s-skills 설치 후 MCP 서버(Linear/Slack/Notion)와 GitHub CLI를 대화형으로 설정하는 스킬. 사용 중인 도구만 골라 설정하고, 이미 돼 있으면 스킵, 안 돼 있으면 단계별 안내·검증까지 전부 끌고 간다. Use when asked "셋업", "setup", "처음 설정", "s-skills 설치했어요", or after installing s-skills.
Payhip platform help — digital downloads, courses, memberships, coaching, store builder, marketing tools, API. Use when setting up a Payhip store or product, choosing between Payhip Free vs Plus vs Pro plan, configuring Payhip coupons or affiliate program, connecting Payhip to an email service provider, embedding Payhip on an existing website, troubleshooting Payhip checkout or payment issues, or managing Payhip webhooks and license keys. Do NOT use for general digital product strategy without a Payhip context (use /sales-digital-products).
Generate a visual diff review page (ArchitectureGrid for impacted modules + CodeDiff for hunks + Callouts for risks) from a git range, PR URL, or pasted diff. Use whenever the user asks for a PR review, diff summary, change impact analysis, or pastes `git diff` output. Requires the `hyperscribe` skill (renderer engine).
Detect new or modified skills in .agents/skills/ by comparing git hashes against ai-skills, snapshot for rollback, review, publish to ai-skills, install locally, and cherry-pick lockfile to TARGET. Replaces /elevate-skill.
Build a retrospective or forward-looking work timeline from git commits, project docs, user notes, or chat records, then output a Markdown and/or HTML report with a Gantt chart or timeline visualization. Use when the user wants to review past work across one or more projects, explain time allocation to a mentor, summarize what was done in a period, or plan the next phase with a timeline.