← all publishers

hailneed

@hailneed source repo

Report this profile Claim this profile

• 7 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Fit · hailneed

   Rank what is worth building from a radar report — cross each complaint theme with verified-revenue proof (TrustMRR) and, when available, the developer's own persona card from devpersona (stack, strengths, risk patterns) to produce a founder–opportunity fit ranking with MVP scope and first-10-users source. Use when the user asks which idea to build, what would pay, "ne inşa etmeliyim", "hangisi para eder", "bana uygun fırsat", "rank these opportunities", or runs /painradar:fit. Requires a radar report from painradar:scan and runs it first if missing. Not for the complaint report itself — that is painradar:scan. Not for marketing — that is painradar:launch.
   0
   installs
2. ▌
   Scan · hailneed bundle

   Run a complaint radar for a topic, niche or audience — fetch public evidence (Hacker News, GitHub Issues, App Store reviews; Reddit only if explicitly enabled), cluster it into 3–7 ranked themes with a transparent Signal score, and write an evidence-backed report with solution paths and content ideas. Use when the user asks what people complain about, wants pain points, hot topics or unmet needs for a niche, says "run the radar", "şikayet radarı çalıştır", "insanlar neyden şikayetçi", "pain points for X", or runs /painradar:scan <topic>. Not for ranking what to build — that is painradar:fit. Not for launch/marketing plans — that is painradar:launch.
   0
   installs
3. ▌
   Launch · hailneed bundle

   Build an evidence-based launch and marketing flow for a product, repo or chosen opportunity — channel selection with stated reasons, posting rules for Reddit / Hacker News / Product Hunt, an SEO comparison-page plan, a TrustMRR listing step, a 30-day calendar and 3 content briefs grounded in the radar evidence. Use when the user asks how to market or launch, where the first customers come from, "pazarlama akışı", "lansman planı", "nasıl duyururum", "go-to-market", "launch plan", or runs /painradar:launch [repo | idea]. Uses the latest radar/fit reports when present; asks one question when the product is unclear. Not for finding pain points — that is painradar:scan.
   0
   installs
4. ▌
   Lint · hailneed bundle

   Check skills and plugins for the mistakes that stop them working — missing or weak frontmatter, descriptions that never trigger, bodies too long to follow, broken references, unsafe paths, over-broad tool permissions and missing trigger evals. Works on a repo you are developing or on every skill installed across Claude Code, Codex CLI and Gemini CLI. Use when the user asks to review or check a skill, says a skill is not working, asks why a skill never activates, is about to publish a plugin, says "skill'imi kontrol et", "lint my skills", "bu skill neden çalışmıyor", or runs /skillbench:lint [path]. Not for measuring whether a skill actually fired in real sessions — that is skillbench:coverage. Not for finding two skills that compete for the same request — that is skillbench:collide.
   0
   installs
5. ▌
   Collide · hailneed

   Find skills that compete for the same request and copies that have drifted apart — score how much each pair of descriptions overlaps, name the shared terms that blur the boundary, and flag skills duplicated across Claude Code, Codex CLI and Gemini CLI whose contents are no longer identical. Use when the wrong skill keeps opening, when a new skill stops an old one from triggering, before adding a skill next to a similar one, when the same skill is mirrored into several agents, when the user says "yanlış skill açılıyor", "bunlar çakışıyor mu", "which skills overlap", or runs /skillbench:collide. Not for checking how a single skill is written — that is skillbench:lint. Not for counting real activations — that is skillbench:coverage.
   0
   installs
6. ▌
   Coverage · hailneed

   Measure which skills actually fire in real work — count real activations from local Claude Code session history, show how often each skill was used, in which projects and how recently, and list the ones that have never fired at all. Use when the user asks whether their skills are being used, which skills are worth keeping, why a skill never activates in practice, wants to prune or prioritise their skill set, says "hangi skill'ler kullanılıyor", "bu skill hiç açılıyor mu", "are my skills actually used", or runs /skillbench:coverage. Not for checking how a skill is written — that is skillbench:lint. Not for finding skills that compete with each other — that is skillbench:collide.
   0
   installs
7. ▌
   Wrong Name On Purpose · hailneed

   This skill does a thing.
   0
   installs