Loading...
Loading...
Found 267 Skills
Apply Hierarchical Linear Modeling (HLM) to analyze nested data structures with random intercepts and slopes, accounting for intra-class correlation and cross-level interactions. Use this skill when the user has students nested in schools, employees in firms, or repeated measures in individuals, needs to partition variance across levels, or when they ask 'how do I handle nested data', 'what is ICC', or 'do group-level factors moderate individual-level relationships'.
Apply the Fama-French three-factor model to decompose asset returns into market, size, and value factors. Use this skill when the user needs to explain cross-sectional return differences, evaluate fund performance beyond CAPM alpha, assess small-cap or value tilts in a portfolio, or when they ask 'why do small caps earn more', 'is value premium real', or 'what factors drive returns'.
Scan a Cargo workspace or package monorepo and refresh per-member `CLAUDE.md` files plus a thin root `CLAUDE.md`. User-only maintenance workflow for keeping workspace-local AI context accurate after refactors, member additions, export changes, or major architectural shifts.
[Hyper] Optimize an existing codebase through baseline-first experiments, binary evaluation, and one-mutation-at-a-time iteration. Use for codebase autoresearch, measured bottleneck reduction, benchmarked code optimization, and evidence-backed refactors.
Refactors specified code to improve clarity, reduce duplication, or align with the project's architectural patterns — without changing external behavior. Invoked when the user asks to refactor, clean up, simplify, or restructure code.
Use when planning, splitting, shrinking, or sequencing large features, refactors, migrations, or pull requests into small reviewable PRs or CLs. TRIGGER on "split this PR", "this diff is too large", "stacked PRs", "change sequence", "reviewable chunks", "migration plan", "how should I break this up?", or implementation scope too broad for one review. DO NOT TRIGGER for full code review, PR description writing, or tiny one-file edits that already form one self-contained change.
Handle Chainlink ACE (Automated Compliance Engine) work using the public smartcontractkit/chainlink-ace repository and official docs.chain.link ACE Platform docs. Use for audited ACE core contracts, managed Platform/Beta scope, Coordinator API, Reporting API, Policy Management, PolicyEngine, PolicyProtected, policy chains, custom policies, extractors, mappers, Cross-Chain Identity (CCIDs), credential registries, KYC/AML credentials, sanctions screening, regulated tokens, ERC-20 and ERC-3643 compliance token examples, upgrade guidance, and BUSL licensing. Trigger on any mention of ACE, Automated Compliance Engine, chainlink-ace, Chainlink compliance, policy enforcement, ERC-3643, or onchain compliance rules, even if the user does not explicitly say 'ACE'.
Use when PRFAQ, BRD, PRD, product brief, workflow, or equivalent initiative artifacts exist and you need to review them for planning gaps, unclear scope, weak priorities, missing actors, and backlog-blocking ambiguity before decomposing work. Supports `--quick-flow` for fast assumption-driven execution and `--full-flow` for question-driven verified execution. Explicit full or end-to-end spec refinement requests continue through the existing 18-stage refinement cascade.
Dispatch implementation tasks to agent teammates in git worktrees. Triggers: 'delegate', 'dispatch tasks', 'assign work', or /delegate. Spawns teammates, creates worktrees, monitors progress. Supports --fixes flag. Do NOT use for single-file changes or polish-track refactors.
Risk-scaled execution guardrails for repository-scoped code or configuration changes, bug fixes, debugging, refactors, code reviews, test changes, implementation plans that lead to code, and Git mutations. Skip conceptual explanations, contract-preserving prose-only edits, pure architecture design, and read-only repository status.
Refactors brittle snapshot tests into resilient, focused assertions. Provides strategies for reducing snapshot size, extracting meaningful assertions, and maintaining snapshots. Use for "snapshot testing", "snapshot refactoring", "brittle tests", or "assertion improvement".
Analyze character traits based on story text and generate detailed character biographies. Suitable for in-depth understanding of story character settings, providing references for actors to shape roles, and establishing character files for script creation