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/DILAZ/SECURITY REVIEW SKILL

dilaz/security-review-skill

1 skill · 1 installs · 7 stars · GitHub

Install

npx skills add https://github.com/dilaz/security-review-skill

Skills in this repo

1Security Reviewsecurity-review is an agent skill for solo builders who cannot afford “maybe vulnerable” noise before they ship SaaS, APIs, or CLI tools that touch user data. It encodes a strict workflow: start with automated scanners, deepen with manual code review focused on input handling, subprocesses, filesystem access, and outbound requests, and treat every suspected issue as unproven until you write and run a proof-of-concept exploit. That Iron Law keeps your agent from flooding you with theoretical CVE chatter and instead produces a short list of demonstrated risks with severity labels. It pairs naturally with code review skills for logic bugs but goes further into attacker mindset. Use it when hardening a feature branch, responding to a security ask, or validating a dependency-heavy integration before launch—not for everyday refactors with no trust boundary.1installs