Loading...
Loading...
Found 2,126 Skills
Use when a claim depends on an agent taking a real action.
peer-review a plan, design, or implementation, find the one critical risk, list other gaps, propose a fix for the critical risk, and update the plan. Triggers: peer review a plan, review an implementation, assess a design, check a proposal for gaps.
Iterate on RAG systems with structured evals instead of eyeballing. This skill should be used when the user is tuning a RAG pipeline — changing retrieval prompts, swapping models, adjusting chunking, or debugging poor answers — and wants a cheap, ranked set of experiments with cost tracking and structured feedback on the stack. Also use when the user asks "how do I know if my RAG is working?", "this RAG eval is burning money", or "what should I try next on retrieval?".
Analyze story genre types, extract creative elements and story features. Suitable for identifying genre positioning, refining creativity, and analyzing market audiences
Expert in designing high-level enterprise solutions. Specializes in TOGAF adaptation, trade-off analysis, and aligning technology with business strategy.
Value investing screen via Longbridge — scan A-share / HK / US stocks for fundamentally strong but undervalued companies based on PE, PB, dividend yield, ROE, and margin of safety. Suitable for value investing strategy. Triggers: "低估值", "价值投资", "低PE", "低PB", "便宜股票", "安全边际", "高股息低估值", "被低估", "低估值", "價值投資", "低PE", "低PB", "便宜股票", "安全邊際", "高股息低估值", "value investing", "undervalued stocks", "low PE", "low PB", "margin of safety", "value screen", "cheap stocks", "bargain stocks".
Write professional investment memorandums for VC, PE, or public market investments. Structure thesis, risks, and recommendations clearly.
PostHog feature flags for Elixir applications
Review designs, products, and features with Steve Jobs' standards: ruthless simplicity, focus, and end-to-end excellence. Use when the user mentions "Steve Jobs review", "design review", "product review", "what would Steve do", "insanely great", "this feels too complicated", "too many features", "product taste", "saying no", or "is this good enough to ship". Also trigger when critiquing a UI, feature, or roadmap for focus and simplicity, cutting scope to the essential, or pressure-testing the whole experience from first run to daily use. Covers the simplicity audit, the no list, design-is-how-it-works, end-to-end ownership, demo culture, and a Jobs-style review protocol with binary verdicts. For visual design fundamentals, see refactoring-ui. For usability audits, see ux-heuristics. For detail polish, see microinteractions.
Analyze candidate algorithms for time/space complexity, scalability limits, and resource-budget fit (CPU, memory, I/O, concurrency). Use when feasibility depends on input growth or latency/memory constraints and quantitative bounds are required before implementation; do not use for persistence schema or deployment topology decisions.
Create a handoff summary for Claude Code.
Score whether a news event is worth newsjacking, or whether a user's pitch idea is actually newsworthy to journalists. Uses calibrated anchors, hard anti-inflation rules, standing checks, timing windows, and brand-safety kill switches.