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/MAJIAYU000/CLAUDE ARSENAL

majiayu000/claude-arsenal

1 skill · 749 installs · 201 stars · GitHub

Install

npx skills add https://github.com/majiayu000/claude-arsenal

Skills in this repo

1Github Trendinggithub-trending is a research skill for solo builders who treat GitHub Trending as a signal layer, not a quality ranking. It directs agents to pull clean JSON via the bundled fetch_trending.py script (with filters for time range, language, and developers), then apply documented dimensions—stars today, forks, maintainer health, README substance, and cross-checks like Hacker News or star-history curves—to separate marketing spikes from durable projects. The extended reference adds optional GitHub Search API queries and self-hosted trending API alternatives for heavier workflows. Use when you need defensible pick lists for newsletter posts, competitive scans, or “what should I build next” sessions without hallucinated repo metadata. Complexity is intermediate because you must interpret signals, not just run a script. Pair with deeper research skills when validating whether a trending repo solves a paying problem.749installs