nishilbhave
- 15 skills
- 0 followers
- 9 hours ago last updated
- ▌ Youtube Claims · nishilbhave bundleClaim inventory tool for YouTube videos. Use when the user pastes a YouTube URL and asks "what claims does this video make", "list every claim", "show me the evidence", "fact-check material", "extract the testable claims", "what does this person assert", or wants a research- grade timeline of every concrete and vague claim, every piece of evidence cited, and every pitch made — with timestamps and verbatim quotes for each. V1 is inventory-only; it does not verify the claims against external sources. Useful for researchers, journalists, skeptics, and anyone preparing to evaluate a creator's substance. Saves the full inventory to ~/youtube-reports/ and prints a one-glance dashboard inline.
- ▌ Youtube Extract · nishilbhave bundleArtifact extraction tool for YouTube videos — pulls links, code snippets, named books, tools, and people mentioned. Use when the user pastes a YouTube URL and asks "extract links from this video", "what tools did they mention", "what books did they reference", "pull the code snippets", "list the resources", "give me the references", or wants a clean reference list of named artifacts. Returns a categorized list (links, code, books, tools, people) with timestamps and verbatim mentions, plus an inline counts dashboard. Useful for tutorials, podcasts, and explainers where the creator references many resources. Saves the full extract to ~/youtube-reports/ and prints a one-glance dashboard inline.
- ▌ Youtube Summary · nishilbhave bundleFast neutral summary tool for YouTube videos — no verdict, no judgment. Use when the user pastes a YouTube URL and asks "summarize this video", "tl;dr", "what does this video cover", "what's actually in this video", "give me the gist", "what does this say", "what's in here", or wants a 30-second read of what was actually said. Returns a 3–4 sentence TL;DR, a section-by-section breakdown with timestamps, top takeaways as bullets, and skippable-section markers so the reader can fast-forward past pitches and outros. Factual and neutral — never recommends watching or skipping. For a watch/skip recommendation use `youtube-verdict` instead. Saves the full summary to ~/youtube-reports/ and prints a one-glance dashboard inline.
- ▌ Youtube Verdict · nishilbhave bundlePre-watch decision tool for YouTube videos. Use when the user pastes a YouTube URL and asks "is this worth watching", "should I watch this", "should I skip this", "watch or skip", "give me a verdict on this video", "is this YouTube video any good", or wants a pre-watch summary that ends in a recommendation. Returns WATCH or SKIP with a 0–10 score (5 and 6 disallowed — the tool commits), a best-minutes range, substance density (concrete vs vague claims, evidence shown, pitches), and a who-should-watch / who-should-skip split. Also catches **clickbait thumbnails** — when the host LLM has vision capability, the skill extracts text overlays and visual elements from the thumbnail and flags any specific outcome promise (e.g. "$10K/DAY") that the transcript doesn't substantiate. Every flag cites a verbatim quote — from the transcript with a timestamp, or from the thumbnail with the slot `[thumb]`. No hallucinated criticism. For neutral summaries with no judgment use `youtube-summary` instead. Saves the full report t
- ▌ Codeprobe · nishilbhave bundleWhole-codebase code quality audit system with 9 specialized sub-skills covering security, SOLID principles, architecture, error handling, performance, test quality, code smells, design patterns, and framework best practices. Produces a scored health dashboard (0-100 per category), severity-rated findings (P0-P3) with severity rationales, and copy-pasteable fix prompts; also does PR-style diff review vs a base branch. Strictly read-only — never modifies user code. Use when the user says "codeprobe", "audit", "full code review", "code health", "check my code", "security scan", "code smells", "SOLID check", or asks how healthy, risky, or maintainable a codebase is. (For reviewing just the working diff, the built-in /code-review may be more appropriate unless the user asks for codeprobe.)
- ▌ Codeprobe Solid · nishilbhaveAudits code for SOLID principle violations — Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. Identifies classes and methods that violate these principles and generates fix prompts. Trigger phrases: "SOLID check", "solid review", "SRP violation", "dependency inversion".
- ▌ Codeprobe Testing · nishilbhaveAudits code for test quality and coverage issues — missing tests, test smells, poor test structure, mock abuse, coverage gaps, and fragile test data. Identifies weaknesses in the test suite and generates fix prompts. Trigger phrases: "test quality", "test audit", "test review", "coverage check", "missing tests", "test quality audit".
- ▌ Codeprobe Patterns · nishilbhaveAudits code for design pattern opportunities and anti-patterns — identifies places where a specific GoF or architectural pattern would solve an observable problem, and flags misapplied patterns that add complexity without benefit. Generates fix prompts. Trigger phrases: "design patterns", "pattern check", "pattern review", "refactoring patterns", "pattern analysis".
- ▌ Codeprobe Security · nishilbhaveScans code for security vulnerabilities — injection flaws, authentication gaps, XSS vectors, mass assignment, CSRF, insecure deserialization, sensitive data exposure, broken access control, and misconfigurations. Generates severity-scored findings with copy-pasteable fix prompts. Trigger phrases: "security scan", "security audit", "vulnerability check", "find security issues".
- ▌ Codeprobe Framework · nishilbhaveDetects framework-specific anti-patterns, convention violations, and idiom misuse across PHP/Laravel, React/Next.js, and Python/Django/FastAPI codebases. Loads framework-specific reference guides and checks against framework conventions. Generates severity-scored findings with copy-pasteable fix prompts. Trigger phrases: "framework review", "framework check", "laravel best practices", "react best practices", "framework audit", "framework-specific review".
- ▌ Codeprobe Code Smells · nishilbhaveDetects code smells and anti-patterns — long methods, large classes, feature envy, data clumps, primitive obsession, dead code, magic numbers, deep nesting, and more. Uses configurable thresholds from .codeprobe-config.json when available. Trigger phrases: "code smells", "smell check", "anti-patterns", "clean code review".
- ▌ Codeprobe Performance · nishilbhaveScans code for performance and scalability issues — N+1 queries, missing indexes, unbounded queries, memory inefficiencies, caching gaps, algorithmic complexity, concurrency bugs, and frontend performance problems. Generates severity-scored findings with copy-pasteable fix prompts. Trigger phrases: "performance audit", "performance check", "N+1 detection", "query optimization", "slow code", "performance review".
- ▌ Codeprobe Architecture · nishilbhaveAnalyzes code architecture and structure — layer violations, circular dependencies, god objects, anemic domain models, missing boundaries, directory structure issues, and configuration problems. Generates severity-scored findings with fix prompts. Trigger phrases: "architecture review", "structure check", "layer analysis", "god class".
- ▌ Codeprobe Error Handling · nishilbhaveScans code for error handling and resilience issues — swallowed exceptions, missing try/catch on external calls, unhandled promise rejections, missing transactions, validation gaps, retry/timeout omissions, and logging blind spots. Generates severity-scored findings with copy-pasteable fix prompts. Trigger phrases: "error handling check", "exception audit", "resilience check", "try/catch review", "error handling audit".
- ▌ Resume Tailor · nishilbhave bundleTailor a resume to a specific job description. Spawns sequential agents to analyze gaps, rewrite bullets, generate diffs, and score ATS compatibility. Trigger when user says "tailor my resume", "match my resume to this JD", "help me apply for this job", "update my resume for this role", or provides a job description alongside their resume.