Skip to content

Skillselionwith God's help

By phase

IdeaResearch & spot demand
ValidateScope & prototype
BuildFrontend, backend, MCP
ShipTest, review, deploy
LaunchDistribution, SEO, ASO
GrowAnalytics & retention
OperateMonitoring & uptime

By type

Skills
Marketplaces
MCP servers
Workflows

Skills Marketplaces MCP Learn Brief

Browse all tools →By phase

Idea Validate Build Ship Launch Grow Operate

Explore

Skills
Marketplaces
MCP
Learn
Brief

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

Email address

unsubscribe anytime.

Skillselion

An independent, curated directory of AI-coding tools for solo builders - skills, MCP servers, marketplaces and workflows for Claude Code, Codex and Cursor, organized by the indie build journey from idea to operate.

ResourcesBrowse Skills Browse MCP Servers Browse Marketplaces Browse Workflows Best-of shortlists Glossary State of AI Skills 2026 Weekly Brief

CommunityAbout Learn Feedback Privacy Policy Terms Cookie Policy Accessibility Cookie settings

Last updated June 10, 2026 · © 2026 Skillselion. Skillselion is an independent project and is not affiliated with Anthropic, OpenAI, Cursor, Claude, Claude Code, or Codex.

Skills/MICROSOFT/POWERTOYS

microsoft/powertoys

1 skill · 104 installs · 134k stars · GitHub

Install

npx skills add https://github.com/microsoft/powertoys

Skills in this repo

1Release Note GenerationRelease-note-generation is an agent skill aimed at solo and indie maintainers who need dependable changelog prose when they cut a version. It fits the Ship phase when you are closing a milestone and must explain what changed in language customers and contributors actually read, without spending an evening rewriting commit subjects by hand. Use it after feature work is merged and before you publish binaries or push store metadata, so marketing snippets, support docs, and the release body stay aligned. The skill is oriented toward utility and desktop-style repos such as the PowerToys ecosystem pattern—teams that still treat a tagged release as the unit of trust. It does not replace semantic versioning policy or automated commit categorization; it helps the agent draft and refine the narrative layer once the technical diff is known. Pair it with your existing CI notes or conventional-commit history as input, then edit for tone. Prism catalogs it so builders browsing Release Management can find a focused generator instead of generic chat summarization.104installs