Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when assembling the data and code replication package for a The World Bank Economic Review (WBER) manuscript to meet WBER's condition-of-publication data/code release, the data availability statement with a DOI repository link, and the realities of restricted developing-country data. Builds the deposit and README; it does not run the analysis or write the paper.
Use when building the open-science and reproducibility story for an ASE (IEEE/ACM Automated Software Engineering) submission, covering the mandatory Data Availability Statement, anonymized-but-runnable tools, tool and subject-system provenance pinning, cached LLM outputs, and staging for the ACM Available/Reusable artifact badges.
Use to prepare code and data materials for a Journal of Econometrics (JoE) submission under Elsevier's data-citation and availability norms, including reproducible Monte Carlo and the [dataset] reference tag. Reflects that JoE has no mandatory central replication archive — replication is encouraged, not universally mandated.
MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start with the project's copyright/authorship header (file overview + exact author line). Use automatically whenever writing a new file or editing an existing one; do not wait to be asked. Covers JS/TS/TSX/CJS/MJS, Python, shell, and CSS. Includes the audit script to verify repo-wide compliance.
Review and advance the next easy-to-merge pull request in this repository, then continue to the next simplest PR. Use when the user wants Codex to list open PRs, pick the most trivial low-risk PR, establish or reuse a clean baseline on the default branch, collapse the rebased PR into a single commit on top of that branch, rerun tests and benchmarks when needed, summarize findings for approval, and then either merge, close, or request changes / clarification with the user's approval.
This skill should be used when the user asks to "publish to winget", "update winget", "submit to winget", "winget release", "create winget PR", or mentions publishing Dev Proxy to the Windows Package Manager. Handles creating manifest files, computing installer hashes, and submitting a pull request to the winget-pkgs repository.
This skill should be used when the user asks to "upgrade Dev Proxy version", "bump Dev Proxy to a new version", "update version to X.Y.Z", "release new Dev Proxy version", or mentions version upgrades in the Dev Proxy repository. Handles copying schema folders and updating version strings across csproj, config, installer, and source files.
Design and document new features with GitHub issue, low-level design (LLD), expert review, and testing plan. Creates structured documentation in .scratchpad/ with issue spec, technical design with diagrams and pseudo-code, multi-persona expert review, and a testing plan covering functional (curl and registry_management.py), backwards-compatibility, UX, ECS/terraform, and E2E API tests. Supports starting from a user description OR an existing GitHub issue URL. Folder naming: issue-{number}/ for existing issues, {feature-name}/ for new features.
MoE expert-parallel communication overlap in Megatron Bridge. Covers dispatch/combine overlap, flex dispatcher backends, and expert wgrad scheduling.
Guide for adding support for new LLM or VLM models in Megatron-Bridge. Covers bridge, provider, recipe, tests, docs, and examples.