Security First

Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations

Routes any Feishu/Lark/Doubao operation, including recording lookup by date (按日期找会议录音), through the version-matched lark-cli domain guide embedded in the installed CLI, then executes and verifies the task.

Read status and send commands to Samsung SmartThings devices: lights, locks, thermostats, sirens, garage doors. Trigger phrases: smartthings, samsung smart home, unlock the door, smartthings thermostat.

Control Tesla vehicles through the official Tesla Fleet API: lock/unlock, remote start, charge control, preconditioning, honk, trunk. Trigger phrases: tesla car, tesla vehicle, lock my tesla, precondition tesla, tesla charge.

Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test.

Watch a brand's own product footage (screen recording, product film), pick the moment that proves each line with the user, and render those picks as a product layer — free, local.

Quick capture of raw thoughts with intelligent domain classification and competitive intelligence extraction

Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).

Stake creator coins into Pantheon vaults on Base and Robinhood Chain, view staking positions, and claim monthly rewards

Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.

Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to ju…

Use when auditing an ACL submission before an ACL Rolling Review cycle deadline, covering long/short paper page budgets, the mandatory Limitations section, Responsible NLP checklist, anonymized PDFs and supplements, preprint declarations, dual-submission rules, resubmission linking, and ARR desk-rej…

Use when the causal identification argument is the bottleneck for an American Economic Journal: Applied Economics (AEJ: Applied) manuscript — RCT, difference-in-differences/event study, regression discontinuity, IV, or shift-share.

Use when an American Economic Journal: Applied Economics (AEJ: Applied) manuscript's headline estimate must be shown to survive specification, sample, and inference choices before submission or in an R&R.

Use when building or revising the exhibits of an American Economic Journal: Applied Economics (AEJ: Applied) manuscript so the main causal result is legible in one table or figure and respects AEA house presentation norms.

Use when the credibility of the causal evaluation of a policy is the bottleneck for an AEJ: Economic Policy manuscript — DID/event study, IV, RDD/bunching, or RCT of a program.

Use when an AEJ: Economic Policy manuscript's headline policy estimate needs to be shown stable and credible against specification, sample, inference, and identification threats.

Use when building or revising exhibits for an AEJ: Economic Policy manuscript so they meet AEA house style and carry the policy message — no significance asterisks, a self-contained headline exhibit, and figures that show the policy effect with uncertainty.

Use when the empirical identification of a macro shock or dynamic causal effect is the bottleneck for an American Economic Journal: Macroeconomics (AEJ: Macro) manuscript — SVAR, local projections, narrative, high-frequency/proxy-VAR, or micro-data macro designs.

Use when the headline result of an American Economic Journal: Macroeconomics (AEJ: Macro) manuscript must be shown stable across specification, sample, identification, and tuning choices.

Use when the question is what makes the result tight or what the data identify for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript — covering both (a) structural/empirical-IO and experimental identification and (b) for pure theory, which assumptions drive the result and how robu…

Use when extensions, edge cases, or applied robustness checks are missing for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript — covering theory extensions (relaxed assumptions, alternative concepts, perturbations) and applied/experimental robustness.

Use when the model setup, equilibrium concept, or proof architecture is the bottleneck for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript — the central skill for a theory-first paper.

Use when the identification argument is the bottleneck for an American Economic Review: Insights (AER: Insights) short-format manuscript — causal identification in an empirical design, parameter identification in a structural model, or treatment-effect identification in an experiment.

Use when appraising the cumulative evidence and ensuring balance in an Academy of Management Annals (Annals) review — weighing conflicting findings by credibility, steelmanning rival schools, and handling the author's own work even-handedly.

Use when systematically gathering, coding, and synthesizing a management/organization literature for an Academy of Management Annals (Annals) review — the search-and-coverage methodology and the choice of narrative vs. systematic vs. bibliometric integration.

Use when responding to an Academy of Management Annals (Annals) proposal decision or full-review referee letter — framework/attitude asks, coverage gaps, balance complaints, and accessibility.

Use when judging whether a management/organization literature is an Academy of Management Annals (Annals)-scale review topic — mature, important, fragmented, and integrable into a new framework — rather than a narrow review.