101 skills · sorted by relevance
Check a research idea against recent literature and closely related papers. Receive a structured comparison of overlapping claims, distinct contributions, and risks, with separate assessments of originality and whether causal effects can be credibly established.
Review empirical economics papers using criteria modeled on leading journals. Examine causal reasoning, theoretical explanations, regression tables, figures, robustness, and contributions to prior research, then organize potential flaws by severity with concrete suggestions for revision.
Draft research funding proposals for NSF, NIH, DOE, DARPA, and Taiwan NSTC. Organize research aims, methods, expected contributions, budgets, and timelines around each agency’s review criteria and submission requirements, including revisions responding to reviewer feedback.
Coordinate multiple AI agents for research, development, testing, and system analysis. It guides role assignment, communication structures, parallel and sequential tasks, shared memory, progress monitoring, and recovery, bringing separate contributions into reports or coordinated development workflows.
Assess whether a multi-agent workflow justifies its coordination costs. Examine handoffs, lost context, and distinct contributions, then compare the setup with one capable agent to recommend keeping, simplifying, or restructuring it.
Research technology and advanced manufacturing investments by tracing supply chain bottlenecks, or inputs that are hard to expand. Compare companies using dated evidence, potential earnings contributions, and conditions that would change their research priority.
Develop paid advertising concepts, copy angles, and ideas for refreshing creative assets across platforms. Turn those ideas into measurable test briefs, including headline options and concepts for content styled around user contributions.
How to develop, modify, and extend the Claude Code codebase following its established programming style, patterns, and conventions. Use this skill whenever working on the claude-code source — adding tools, commands, utils, components, types, hooks, services, or fixing bugs. Also use when the user asks about claude-code architecture, coding standards, file organization, or wants to understand how the codebase works. This skill ensures all contributions match the existing codebase style exactly.
The English summary is being prepared. Showing the original description.
Resolve conflicts and merges when several branches are open against one repo at the same time — the hotspot files every change must touch (registry manifests, a single version field, shared tool config, one aggregated test module, tracked build output), union-vs-recompute-vs-rebuild as three different correct resolutions, generated artifacts that must never be merged, non-deterministic serialization that makes every branch conflict, renumbered identifiers that git cannot show you, and why a clean auto-merge is not a passing test. Use when rebasing or merging a long-lived branch, resolving conflict markers, reviewing a merge commit, deciding what a repo should commit vs generate, or setting up a repo that will take parallel contributions.
The English summary is being prepared. Showing the original description.
Use when determining author order on research manuscripts, assigning CRediT contributor roles for transparency, documenting individual contributions to collaborative projects, or resolving authorship disputes in multi-institutional research. Generates fair and transparent auth...
The English summary is being prepared. Showing the original description.
Drafts journal-ready cover letters for manuscript submission. Use when preparing a submission package, communicating the manuscript's contributions and journal fit to editors, or tailoring the novelty framing for a specific journal's scope. Also triggers on "write a cover letter for my paper", "draft a submission cover letter", "help me write to the editor", or "cover letter for [journal name]".
The English summary is being prepared. Showing the original description.
Draft and review contributions to existing MEX project knowledge in the repo wiki. Use when the user wants to capture a team decision, convention, or architecture note, propose an addition or correction for team review, or invokes /mex-inbox or $mex-inbox. Also supports existing Spec proposals. Keywords: mex, project memory, CLAUDE.md, team memory, drift, inbox. Do not activate for brainstorming alone, routine GROW upkeep, email inboxes, session logs, or handoffs.
The English summary is being prepared. Showing the original description.
Draft and review contributions to existing MEX project knowledge. Use when the user asks to capture a discussion or decision in project knowledge, propose an addition or correction for team review, or explicitly invokes /mex-inbox or $mex-inbox. Also supports existing Spec proposals. Do not activate for brainstorming alone, routine GROW upkeep, email inboxes, session logs, or handoffs.
The English summary is being prepared. Showing the original description.
Build and deliver a raise request that actually works — the evidence, the number, the timing, and the exact words — instead of hoping it gets noticed. Use when asked how do I ask for a raise, I deserve more money, prepare me to ask for a raise, or negotiate a pay increase at my job. Produces a value case built on your actual contributions and market rate, a specific target number with justification, the right timing and person, a script for the conversation, and responses to the likely pushbacks — turning 'I want more' into a business case your manager can say yes to.
The English summary is being prepared. Showing the original description.
Extract and score leads from GitHub repositories by analyzing stars, forks, issues, PRs, comments, and contributions. Produces unified multi-repo CSV with deduplicated user profiles. No paid API credits required.
The English summary is being prepared. Showing the original description.
Multi-agent board meeting protocol running a structured 6-phase deliberation with isolated C-suite contributions to prevent groupthink. Use when making major strategic decisions or resolving cross-functional disagreements.
The English summary is being prepared. Showing the original description.
Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal reproductions and issue drafts, to preparing, testing, and submitting a pull request that follows this repository's conventions. Use when the user says they found a bug, wants a feature, wrote a workaround worth upstreaming, or asks how to contribute, open an issue, or make a PR to retentioneering-tools.
The English summary is being prepared. Showing the original description.
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows. Use when extracting problem setting, object-method-condition logic, contributions, method pipeline, equations, datasets, baselines, metrics, ablations, limitations, replication details, citation role, related-work positioning, implementation notes, or reviewer-style assessment from a paper, PDF, abstract, or manuscript excerpt.
The English summary is being prepared. Showing the original description.
smina molecular docking CLI. AutoDock Vina fork with customizable scoring functions, native SDF/MOL2/PDB ligand input, autoboxing, local energy minimization, and per-atom score breakdowns. Pipeline: receptor PDBQT prep -> ligand prep (RDKit/OpenBabel) -> dock via autobox or explicit grid -> rescore/minimize with custom scoring -> rank poses by affinity. Choose smina over Vina when you need custom scoring terms (--custom_scoring), local optimization of an existing pose (--local_only), per-atom contributions (--atom_term_data), or SDF/MOL2 ligands without manual PDBQT conversion. For unknown binding sites use diffdock; for the Python-bindings/Vinardo workflow use autodock-vina-docking.
The English summary is being prepared. Showing the original description.
Turn vague or partially formed AI, computer-science, data-driven, and engineering-method research directions into evidence-grounded, falsifiable, paper-ready Research Idea Briefs through heuristic questioning, staged confirmation, literature positioning, novelty attack, and method-figure planning. Use when the user needs to clarify a research idea, formalize inputs/outputs/objectives/constraints, frame background and motivation, select 3-5 anchor papers, identify a defensible gap, derive 2-3 contributions, stress-test novelty, or design an input-to-output method framework and core-paper figure. Also trigger on requests such as 明确科研 idea、启发式梳理 idea、互动追问科研问题、梳理论文创新点、定义研究任务、找对标论文、把研究方向变成论文方案、画方法框架图. Do not use as the primary workflow for running experiments, exhaustive systematic reviews, drafting full manuscript sections, or polishing finished prose.
The English summary is being prepared. Showing the original description.
Source technical and professional talent by combining LinkedIn profiles, GitHub contributions, and company intelligence. Identifies candidates with specific skills, assesses expertise depth, and provides outreach context for recruiting teams.
The English summary is being prepared. Showing the original description.
Research GitHub user profiles including repositories, contributions, languages, stars, and activity patterns. Useful for developer talent sourcing, open-source community research, and technical due diligence on engineering teams.
The English summary is being prepared. Showing the original description.
Prepare a meeting-ready alternative-investments brief for a client, household, IRA, trust, or named account before a review — pulls the alts book from iCapital or Addepar (positions, NAV vs. commitment, called and unfunded amounts, contributions/distributions/subscriptions/redemptions, lockups, and the platform's own IRR/TVPI/DPI/RVPI) and sits it beside the liquid book and IPS target from the connected portfolio system (Orion Connect, Addepar, or Envestnet), then flags cash needed for capital calls, alts % vs. target, concentration, unfunded concentration, and stale as-of data. Cites the source platform on every figure and keeps disclosures on the page. Does not recommend funds, forecast NAVs/IRRs, or simulate allocation changes. Triggers on "alts brief", "/alts-brief", "prep the [client]'s alts review", "what's going on with [client]'s PE/private investments", "how's [client] doing on their alts", or any request to review a household's alternative investment positions before a meeting.
The English summary is being prepared. Showing the original description.
Implement and route HitKeep contributions through the repository-owned hk developer platform. Use for any HitKeep code, UI, API, database, analytics-feature, seed, screenshot, documentation, integration, or release-preparation change, as well as setup, local development, builds, smoke tests, and contributor workflow discovery.
The English summary is being prepared. Showing the original description.