Loading...
Loading...
Found 252 Skills
Toolkit for generating PowerToys release notes from GitHub milestone PRs or commit ranges. Use when asked to create release notes, summarize milestone PRs, generate changelog, prepare release documentation, request Copilot reviews for PRs, update README for a new release, manage PR milestones, or collect PRs between commits/tags. Supports PR collection by milestone or commit range, milestone assignment, grouping by label, summarization with external contributor attribution, and README version bumping.
The craft of communicating technical concepts clearly to developers. Developer communications isn't marketing—it's about building trust through transparency, accuracy, and genuine utility. The best devrel content helps developers solve real problems. This skill covers technical documentation, developer tutorials, API references, changelog writing, developer blog posts, and developer community engagement. Great developer communications treats developers as peers, not leads to convert. Use when "documentation, docs, tutorial, getting started, API reference, changelog, release notes, developer guide, devrel, developer relations, code examples, SDK docs, README, documentation, devrel, tutorials, api-docs, developer-experience, technical-writing, getting-started, changelogs" mentioned.
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
Turn git commits and diffs since an exact start date into a copy-pastable, non-technical client report grouped by feature. Use when the user wants a client update, accomplishment summary, weekly progress note, stakeholder recap, or high-level status report based on git history. Trigger on: client report from commits, summarize git diff since a date, weekly update from git log, non-technical accomplishments, stakeholder-ready changelog. Do NOT trigger for technical release notes, code review, or any request where the date is still ambiguous.
Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.
Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.
Creates Pull Requests for Prowler following the project template and conventions. Trigger: When working on pull request requirements or creation (PR template sections, PR title Conventional Commits check, changelog gate/no-changelog label), or when inspecting PR-related GitHub workflows like conventional-commit.yml, pr-check-changelog.yml, pr-conflict-checker.yml, labeler.yml, or CODEOWNERS.
SUPERSEDED by /brand-assets (brand-kit). Use /brand-assets for new projects. This skill remains for backward compatibility with projects not yet migrated to brand.yaml. Generate deterministic, template-based Open Graph cards with Satori. Use when: creating OG images for blog posts, product pages, changelogs, or comparison pages. Complements /og-hero-image (AI creative) with consistent, branded templates. Keywords: og image, open graph, satori, social card, meta image, twitter card.
Release preparation workflow - security audit → E2E tests → review → changelog → docs
Use this skill whenever Claude needs to fetch, read, extract, or analyze content from a web URL. Converts web pages into clean, token-efficient markdown using the markdown.new service instead of fetching raw HTML. Trigger when the user provides a URL and wants its content summarized, quoted, analyzed, compared, extracted, or processed. Also trigger when Claude needs to read documentation, blog posts, articles, wikis, release notes, changelogs, or any web-hosted text content. Even if the user just pastes a URL with no instruction, use this skill. Do NOT use for binary files, authenticated pages, or API endpoints returning JSON/XML.
Improve an existing prompt or skill with targeted, minimal-diff edits that preserve its core intent, and return the revised artifact plus a short changelog and tradeoffs note. Use this whenever the user wants to refine, sharpen, tighten, or upgrade an existing prompt or skill, asks to "make it better," or wants a small high-leverage edit instead of a full rewrite — even if they don't explicitly mention tuning.
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.