sfrangulov

@sfrangulov source repo

9 skills
0 followers
17 hours ago last updated

▌
MCP Graveyard · sfrangulov
Audit which MCP server tools your Claude Code sessions actually invoke. Use when the user wants to find dead MCP servers (configured but never called), hallucinated MCP tool calls, or per-project MCP usage. Triggers on "which MCP servers don't I use?", "clean up MCP config", "remove unused MCP servers", "audit MCP tools". Runs locally; reads ~/.claude session JSONL logs and ~/.claude.json. No network calls.

0
installs
▌
Skill Graveyard · sfrangulov
Audit which Claude Code skills you actually invoke. Use when the user wants to find dead/unused skills, hallucinated skill invocations, per-project skill stats, or token cost of installed skill metadata. Triggers on "what skills don't I use?", "clean up my skills", "why didn't this skill work?", "audit skills". Runs locally; reads ~/.claude session JSONL logs. No network calls.

0
installs
▌
Memory Graveyard · sfrangulov
Audit which entries in your project's MEMORY.md Claude actually reads. Use when the user wants to find dead memory entries, broken pointers in MEMORY.md, orphan memory files, or surface entries that fall below the system-prompt truncation cutoff. Triggers on "audit MEMORY.md", "dead memory entries", "broken memory pointers", "memory hygiene", "unused memory", "memory truncation". Runs locally; reads ~/.claude/projects session JSONL logs and memory directories. No network calls.

0
installs
▌
Book To Skills · sfrangulov bundle
Distill a book, long-video transcript, podcast, course, or interview into a coherent set of executable agent skills. Use when the user asks to "distill this book into skills", "turn this video/podcast/course into agent skills", or wants the frameworks, principles, and methodologies in long-form content extracted into atomic, reusable skills an agent can invoke in real situations. NOT for plain summarization, book reviews, or role-playing the author.

0
installs
▌
Research Pipeline · sfrangulov bundle
Disciplined multi-source research pipeline that produces a verifiable, citation-backed report — orchestrated subagents, source-discipline, content-addressed snapshots, a deterministic→judge verification funnel, and a mandatory adversarial fact-check pass. Use when a deep-research document (best-practices canon, technology evaluation, claims that downstream code or decisions will lean on) must be source-grounded, fact-checked, and reproducible across sessions or machines — not a quick lookup. Explicit-invocation only.

0
installs
▌
Demo Video Pipeline · sfrangulov bundle
End-to-end automated pipeline for recording polished 30-90s demo videos of React or HTML web apps. Universal keyboard-driven zoom hook with cinematic scenes → Playwright headless recording → Remotion overlay graphics (intro, callouts, count-up numbers, pulse highlights) → ElevenLabs voiceover with frame-perfect timings → final mp4 with audio mixing and ducking. Use whenever the user wants to record a product walkthrough, marketing video, screencast with voiceover, demo for LinkedIn, YouTube or product launch, executive presentation, sales video, onboarding video, feature announcement, or any short polished video showing a web UI. Triggers on phrases like "record a demo", "make a screencast", "video for landing page", "product hunt video", "show this UI in a video", "walkthrough video", "demo with voiceover", "screen recording with zooms and callouts".

0
installs
▌
Oss Product Selection · sfrangulov bundle
Picks the next open-source product to ship when the goal is personal brand growth, not revenue. Trigger whenever the user is deciding which OSS tool, npm CLI, dev utility, or side project to build next — including phrases like "what should I open-source next", "picking my next product", "OSS portfolio strategy", "expanding my portfolio", "choose my next side project for brand", "help me decide between tool ideas", "is this a good idea to ship", "viral dev tool ideation", "indie hacker product selection", or when they describe an existing portfolio and ask what to add. Trigger even when the user does not say "OSS" — any time they weigh multiple build ideas for brand, audience, or career reasons qualifies. Runs 7 phases with hard gates — constraints, asset inventory, broad ideation, competitive/platform/pain/hype scans, two-axis brand-vs-product scoring, naming, reality check and spec. Prevents premature ideation, skipped competitive research, naming collisions, and the platform shipping a native equivalent.

0
installs
▌
Consulting Problem Solving · sfrangulov bundle
**Consulting Problem Solving Framework**: An interactive, user-led approach to solving complex business and organizational problems using structured consulting methodology. You act as a consulting associate; the user acts as the consulting partner who drives decisions. Walks through problem definition, MECE structuring, prioritization, work planning, analysis, synthesis, recommendations, and communication — with the user providing input, making choices, and reviewing deliverables at every step before moving forward. Produces deliverables at each stage — markdown working docs, spreadsheets for data analysis, and final slide content (.md) or approved content for a vertical document. This skill owns content and structure only — visual rendering, styling, and deck/document generation are handled by downstream builder skills. All final prose is polished using an integrated Strunk & White writing style guide. Use this skill whenever the user mentions: strategy consulting, problem solving framework, issue tree, MECE

0
installs
▌
Consulting Problem Solving Ru · sfrangulov bundle
**Русская версия Consulting Problem Solving Framework** — интерактивное решение бизнес- и организационных задач: ты ассоциат, пользователь — партнёр. 8 шагов с артефактами и явным утверждением: проблема, MECE-дерево, приоритизация, план работ, анализ, синтез, рекомендации, коммуникация по Strunk & White. Термины: стратегический консалтинг, дерево проблемы, issue tree, MECE, гипотезо-ориентированный подход, пирамида Минто, 80/20, case interview, структурное мышление. Роли: «я CEO/основатель/директор, у меня проблема с…», «готовлюсь к совету директоров», «нужна стратегическая сессия». Симптомы: падает выручка/маржа/LFL, теряем клиентов или долю рынка, не понимаем куда инвестировать, как приоритизировать инициативы, выходить ли в новый сегмент. Формулировки: «помоги структурно подумать», «разложи задачу», «как бы консультант подошёл», «нужен структурный подход к X». Используй на запросы, требующие структурного аналитического решения с артефактами — даже если фреймворк не назван явно.

0
installs

9 published skills