Loading...
Loading...
Found 1,915 Skills
Review Skill definition quality. Use when user asks to "review skill", "check skill quality", "validate skill", "lint skill", "review my skill", or wants to check if a Skill follows best practices. For execution trace analysis, use when user explicitly mentions "analyze execution", "review trace", or "evaluate execution process". Do NOT use for runtime debugging (use agent-debug skill), code review (use code-review skill), or general file validation.
Test trading strategies on historical data to evaluate performance, risks, and profitability.
Design and manage reference data systems — security master, client master, account master, identifier mapping, pricing data, and governance. Use when building or evaluating a security master database, mapping identifiers across systems (CUSIP to ISIN, SEDOL to FIGI), designing client master models for onboarding or KYC, defining account master attributes across custodians, implementing pricing validation with vendor hierarchy, establishing reference data governance and stewardship, handling identifier changes from corporate actions, or troubleshooting data quality issues traced to stale prices or missing identifiers. Trigger on: security master, CUSIP, ISIN, SEDOL, FIGI, client master, account master, pricing data, reference data, golden source, MDM, master data, identifier mapping, data governance, pricing validation.
Agent harness architecture — structure a project's agent context across layers for effective AI-assisted development. Covers CLAUDE.md, skills, design docs, hooks, and all artifacts that shape how an agent understands and operates in a codebase. Use when setting up or improving a project's agent configuration, when agent context feels bloated or disorganized, when onboarding a new project for AI-assisted development, or when the agent keeps losing architectural awareness mid-task. Trigger on phrases like "set up claude", "improve CLAUDE.md", "agent keeps forgetting", "context is too long", "harness setup", "organize agent context", "how should I structure my prompts". Supports arguments: `/harness audit` to evaluate an existing project's context architecture, `/harness init` to set up harness from scratch.
Apply network economics to analyze markets with network effects, critical mass dynamics, and platform competition. Use this skill when the user needs to evaluate tipping points, lock-in risks, switching costs, or standards wars, especially in technology platforms and two-sided markets.
Apply auction theory to compare the four canonical auction formats and assess revenue equivalence. Use this skill when the user needs to choose an auction format, evaluate bidding strategies, or determine when revenue equivalence breaks down due to risk aversion, asymmetry, or correlated values.
Evaluate backlink quality using Domain Authority, Domain Rating, and trust metrics. Use this skill when the user needs to assess link profile health, identify toxic backlinks, or plan link building strategy — even if they say 'check my backlinks', 'link building', or 'domain authority analysis'.
Analyze market structures across perfect competition, monopolistic competition, oligopoly, and monopoly to predict firm behavior and market outcomes. Use this skill when the user needs to classify a market's competitive structure, predict pricing behavior, evaluate antitrust implications, or understand why an industry behaves the way it does — even if they say 'why can they charge so much', 'is this market competitive', or 'will prices come down'.
Apply Moore's business ecosystem framework to analyze how firms co-evolve through four stages (birth, expansion, authority, renewal) and occupy different ecosystem roles. Use this skill when the user needs to map ecosystem dynamics in a platform or industry, evaluate keystone vs dominator strategies, assess ecosystem health, or when they ask 'what stage is this ecosystem in', 'how should we position in this ecosystem', or 'why is this ecosystem declining despite having a dominant player'.
Respond to review comments on a PR after evaluation and fixes
Calculate comprehensive ROI for AI implementation projects. Takes current costs, manual process time, team size, and hourly rates. Generates detailed roi-analysis.md with executive summary, cost-benefit tables, sensitivity analysis, break-even timeline, and comparison scenarios. Use when evaluating AI investments, building business cases, or justifying automation spend.
Invoke this when users react disproportionately intensely to losing (or about to lose) something, or feel an urgent need to "break even" and fail to cut losses after a loss. Typical trigger signals: sunk cost trap, gambler's doubling down, irrational bidding in auctions, inability to abandon failed projects with heavy resource investment. Not applicable to general investment valuation (use value-assessment) or herd behavior (use misjudgment-checklist).