viktor-milev
UserA small library of Claude skills, built for real analytical work and validated before publishing.
Categories
Indexed Skills (4)
prompt-optimizer
Rigorous mode prompt optimizer — audits a polished prompt, decides output architecture (single-turn vs. chained multi-stage), and rewrites it to elicit state-of-the-art output from Claude. Triages every input into OUT OF PURVIEW / BORDERLINE / IN PURVIEW; rigorous optimization (architecture decision, 9-dim diagnostic, archetype detection, capability activation) applies ONLY to IN PURVIEW. When chain signals fire, produces a chain deliverable (README + Project orchestrator + per-stage prompts) instead of a single-turn prompt. Simple prompts return substantially unchanged with a triage note. Use when the user asks to optimize, audit, score, diagnose, sharpen, or level up a prompt; trigger phrases include "optimize this prompt", "PO this", "run this through the optimizer", "sharpen this prompt". For messy dictated or flow-state input, a separate flow-mode counterpart exists. Do NOT trigger when the user wants the prompt EXECUTED rather than optimized.
prompt-optimizer-flow
Flow mode prompt optimizer — transforms rough, dictated, or stream-of-consciousness thoughts into a state-of-the-art Claude keystone prompt in seconds, without breaking the user's flow. Produces a finished, paste-ready prompt with no placeholders or template variables. Skips diagnostic theater, infers intent aggressively from messy input. Use whenever the user pastes or dictates messy unstructured input and wants it turned into a polished prompt fast. Trigger phrases include "quick prompt", "dictating", "rough thoughts", "thinking out loud", "PO this fast", "flow mode", "PO flow", "make this a prompt", "turn this into a prompt", "draft a prompt for", "starting a new chat about". Also trigger on dictation artifacts (rambling, self-corrections, "um", "uh", "actually wait") or when starting a new chat and needing a starter prompt. For polished prompts needing rigorous evaluation, use prompt-optimizer instead. Do NOT trigger when the user wants the prompt EXECUTED.
prompt-architect
Classifies a task against a 10-bucket taxonomy, decides output architecture (single-turn vs. chained multi-stage), and produces a technique-grounded v1 draft prompt. Verdicts are SINGLE-TURN, SINGLE-TURN (CEILING) with a strain note, or CHAIN producing a README + Project orchestrator + per-stage prompts. Use when you describe a non-trivial task but have no prompt written yet. Trigger phrases include "help me prompt this", "set up a prompt for", "draft a prompt for", "how should I ask Claude to", "architect a prompt for", "I'm about to start work on X — help me frame it". Also trigger for multi-step analytical tasks (research, knowledge document, design, decision support) where no draft exists. Do NOT trigger when a draft prompt already exists — that's prompt-optimizer. Do NOT trigger for tasks already covered by a dedicated domain-specific skill — route to that skill instead.
investment-council
Pressure-test an investment thesis, trade, position, or mispricing claim through a council of five orthogonal advisors — Bear, Bull, Base Rate Skeptic, Market Structure Analyst, Risk Manager — who analyze independently, peer-review anonymously, and return a verdict tuned to DECISION (take/size this position) vs ANALYSIS (is this asset mispriced). Trigger on "council this trade/position/thesis/investment," "investment council," "pressure-test/war-room/stress-test this position," and on capital-at-risk asks like "should I buy/sell/short X," "is X mispriced/cheap/a good trade," "what's wrong with this thesis," "sanity-check this trade," "help me size this." For single securities, funds, portfolios, and mispricing claims. NOT for macro commentary without a position, portfolio construction, or fund-manager due diligence.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.