Router skill for LLMQuant investor-lens workflows. Use when the user wants an investor-style reasoning overlay grounded in LLMQuant Data evidence.
npx skills add https://github.com/LLMQuant/skills --skill llmquant-investor-lenses
This category routes investor-style reasoning overlays. The named workflows are analytical lenses, not claims of endorsement or replication. All external evidence must come from LLMQuant Data.
| User intent | Workflow |
|---|---|
| Long-term owner lens: moat, circle of competence, and margin of safety. | workflows/warren-buffett.md |
| Quantitative value and margin-of-safety discipline. | workflows/ben-graham.md |
| Multi-model quality investor with inversion discipline. | workflows/charlie-munger.md |
| Dhandho, cloning, and low-risk doubles. | workflows/mohnish-pabrai.md |
| Emerging-market compounder and ROE-first selection. | workflows/rakesh-jhunjhunwala.md |
| GARP, ten-baggers, and simple explainable businesses. | workflows/peter-lynch.md |
| Qualitative growth and scuttlebutt-style research. | workflows/phil-fisher.md |
| Disruptive innovation, Wright's Law, and exponential TAM. | workflows/cathie-wood.md |
| Macro liquidity regime and asymmetric sizing. | workflows/stanley-druckenmiller.md |
| Concentrated activist value and catalyst unlocks. | workflows/bill-ackman.md |
| Contrarian deep value and filing-first downside work. | workflows/michael-burry.md |
| Tail-risk, barbell, convexity, and antifragile thinking. | workflows/nassim-taleb.md |
| Story-plus-numbers valuation discipline. | workflows/aswath-damodaran.md |
| Mechanical Buffett-style business, moat, management, and valuation scorecard. | workflows/warren-buffett-scorecard.md |
| Seller-only quality-business options framework. | workflows/duan-yongping-seller.md |
| Cycle-position offense/defense signal. | workflows/howard-marks-cycle.md |
| Rare panic-buy gate for liquid quality exposure. | workflows/david-tepper-panic-signal.md |
Prefer LLMQuant Data when available. The workflows may need these data capabilities:
Fallback:
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take llmquant/llmquant-investor-lenses from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.