Skills.
Give your AI a better way to work.
A skill is a set of written instructions that teaches an AI how to do one job the way it should be done: review a pull request, plan a migration, write the release notes.
Install one here and it travels with your account into Claude, Claude Code, Cursor and every other client you sign in with.
Category: Dev tools
17,418 results · page 99 of 581
- View details
aejpol-referee-strategySkillDev tools
Use when anticipating how AEJ: Economic Policy referees and editors will read a manuscript, before submission or before an R&R, to pre-empt the objections that sink policy-evaluation papers. Maps likely pushback to fixes and calibrates expectations; it does not write the response letter (see aejpol-
Ready to connect★ 1k
- View details
aejpol-replication-packageSkillDev tools
Use when assembling the data and code deposit for an AEJ: Economic Policy manuscript to satisfy the AEA Data and Code Availability Policy and the AEA Data Editor's pre-publication reproducibility check. Builds the openICPSR deposit, README, and restricted-data access paths; it does not run the analy
Ready to connect★ 1k
- View details
aejpol-submissionSkillDev tools
Use when running the final pre-submission preflight for AEJ: Economic Policy via the AEA online submission system — single-blind review front matter, JEL codes, submission and publication fees, format, the Data and Code Availability Statement, and disclosure. Final checks; it does not draft content.
Ready to connect★ 1k
- View details
aejpol-workflowSkillDev tools
Use when deciding which aejpol-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for an AEJ: Economic Policy manuscript. Routes — it does not replace — the specialized skills.
Ready to connect★ 1k
- View details
aeri-literature-positioningSkillDev tools
Use when positioning the contribution of an American Economic Review: Insights (AER: Insights) short-format manuscript against the closest published work in one or two tight paragraphs. Stakes the gap concisely; it does not write the full literature review (there is no room for one).
Ready to connect★ 1k
- View details
aeri-rebuttalSkillDev tools
Use when responding to an American Economic Review: Insights (AER: Insights) conditional-accept decision — addressing the editor's letter within the short window, usually without a second referee round. Drafts a concise, decisive response and revision plan; it does not redo the analysis (see aeri-ro
Ready to connect★ 1k
- View details
aeri-replication-packageSkillDev tools
Use when assembling the data and code deposit for an American Economic Review: Insights (AER: Insights) short-format manuscript to pass the AEA Data and Code Availability Policy and the AEA Data Editor's pre-publication reproducibility check. Builds the package and README; it does not run the analys
Ready to connect★ 1k
- View details
aeri-submissionSkillDev tools
Use when running the final pre-submission preflight for American Economic Review: Insights (AER: Insights) via the AEA/ScholarOne submission system — the word-count and exhibit-count gates, abstract limit, fees, author metadata, declarations, and the AEA Data and Code Availability Policy. Final chec
Ready to connect★ 1k
- View details
aeri-tables-figuresSkillDev tools
Use when building or trimming the exhibits of an American Economic Review: Insights (AER: Insights) short-format manuscript to the hard five-exhibit budget, one page each, no significance asterisks. Designs the minimum exhibit set; it does not run the analysis behind them.
Ready to connect★ 1k
- View details
aeri-topic-selectionSkillDev tools
Use when deciding whether a project is the ONE crisp, important, well-identified insight that an American Economic Review: Insights (AER: Insights) short-format manuscript requires, rather than a multi-result paper for AER or a field paper for the AEJ family. Tests single-insight fit; it does not ru
Ready to connect★ 1k
- View details
aeri-workflowSkillDev tools
Use when deciding which aeri-* sub-skill to invoke next, or when sequencing work on a short-format manuscript from topic selection through the conditional-accept response for an American Economic Review: Insights (AER: Insights) submission. Routes — it does not replace — the specialized skills.
Ready to connect★ 1k
- View details
aeri-writing-styleSkillDev tools
Use when revising an American Economic Review: Insights (AER: Insights) short-format manuscript to lead with the result, fit the hard word cap (7,000 words minus 200 per exhibit), and write the ≤100-word abstract. Enforces the length budget and the lead-with-the-result arc; it does not change the an
Ready to connect★ 1k
- View details
aistats-author-responseSkillDev tools
Use when drafting AISTATS author responses or author-reviewer discussion replies under OpenReview, covering text-only discussion, no-link guidance, no revised-paper upload, anonymity requirements, statistician-reviewer pushback patterns, and decision-focused clarification strategy for theory-plus-ex
Ready to connect★ 1k
- View details
aistats-camera-readySkillDev tools
Use when preparing accepted AISTATS papers for PMLR camera-ready submission, covering the 9-page final body, two-column layout reflow, author de-anonymization, proceedings forms, metadata, final appendix handling, registration, in-person presentation obligations, and public artifact release.
Ready to connect★ 1k
- View details
aistats-related-workSkillDev tools
Use when positioning an AISTATS submission against AI, machine-learning, statistics, and uncertainty literature, including arXiv preprints, workshop versions, concurrent submissions, prior conference versions, PMLR archival status, and the two-community citation coverage that AISTATS reviewers expec
Ready to connect★ 1k
- View details
aistats-review-processSkillDev tools
Use when explaining or planning around AISTATS peer review, OpenReview review release, author-reviewer discussion, reviewer volunteer expectations, reviewer confidentiality, decision criteria, meta-review dynamics, the statistician-heavy reviewer pool, and PMLR proceedings outcomes.
Ready to connect★ 1k
- View details
aistats-submissionSkillDev tools
Use when auditing an AISTATS submission for OpenReview readiness, abstract/full-paper deadlines, the 8-page submission body, double-blind anonymity, supplementary material, reproducibility checklist, dual-submission policy, reviewer volunteer requirements, desk-reject triggers, and final-week submis
Ready to connect★ 1k
- View details
aistats-supplementarySkillDev tools
Use when preparing AISTATS supplementary material, appendices, proof details, code/data archives, simulation scripts, additional tables, and anonymized artifacts under deadline, size, anonymity, and reviewer-discretion constraints, including how to split a theory-plus-experiments paper between body
Ready to connect★ 1k
- View details
aistats-topic-selectionSkillDev tools
Use when deciding whether a project is a strong AISTATS fit, comparing AISTATS with NeurIPS, ICML, ICLR, UAI, COLT, JMLR, statistics journals, or application venues, identifying the statistical primitive of the contribution, and sharpening the AI-statistics framing before writing begins.
Ready to connect★ 1k
- View details
aistats-workflowSkillDev tools
Use when planning an AISTATS project timeline from venue fit through abstract submission, full-paper upload, supplementary material, review release, author-reviewer discussion, decision, camera-ready, PMLR publication, registration, presentation, and artifact release, with backward-planning offsets
Ready to connect★ 1k
- View details
aistats-writing-styleSkillDev tools
Use when revising an AISTATS paper for concise AI-statistics framing, theorem-and-experiment clarity, 8-page two-column compression, double-blind wording, reproducibility clarity, statistically careful claims, and assumption-labeling discipline that survives statistician reviewers.
Ready to connect★ 1k
- View details
ase-artifact-evaluationSkillDev tools
Use when preparing an accepted ASE (IEEE/ACM Automated Software Engineering) paper's tool and data for the Artifact Evaluation track, targeting the ACM Artifacts Available and Artifacts Reusable badges on the track's own deadline, with the badge shown on the paper's front page in both IEEE Xplore an
Ready to connect★ 1k
- View details
ase-author-responseSkillDev tools
Use when drafting ASE (IEEE/ACM Automated Software Engineering) author responses, covering the double-anonymous rebuttal that must first survive the early-rejection gate and — distinctively — the criteria-bound revision-round summary-of-changes that maps every stated revision criterion to a concrete
Ready to connect★ 1k
- View details
ase-camera-readySkillDev tools
Use when preparing the ASE (IEEE/ACM Automated Software Engineering) camera-ready after acceptance or a successful revision, covering systematic de-anonymization, the extra content page, the mandatory Data Availability finalization, the correct IEEE/ACM template and metadata, permanentized artifact
Ready to connect★ 1k
- View details
ase-related-workSkillDev tools
Use when writing the related-work and positioning of an ASE (IEEE/ACM Automated Software Engineering) paper, covering the automated-SE literature lanes, delta-first positioning against prior tools/techniques, fair head-to-head framing, and double-anonymous self-citation.
Ready to connect★ 1k
- View details
ase-review-processSkillDev tools
Use when reasoning about how an ASE (IEEE/ACM Automated Software Engineering) research submission is evaluated, covering double-anonymous review, the early-rejection stage before rebuttal, the Accept / Revision / Reject outcomes, the criteria-bound revision round, and how ASE's process differs from
Ready to connect★ 1k
- View details
ase-submissionSkillDev tools
Use when auditing an ASE (IEEE/ACM Automated Software Engineering) research-track submission for HotCRP readiness, covering the ACM acmart sigconf template and the 10+2 page budget, double-anonymous review, the mandatory Data Availability Statement, the early-rejection stage before rebuttal, and des
Ready to connect★ 1k
- View details
ase-supplementarySkillDev tools
Use when deciding what belongs in the 10-page ASE (IEEE/ACM Automated Software Engineering) paper body versus the artifact and supplementary material, splitting content by decision-criticality so nothing that decides acceptance lives outside the reviewed pages under the 10+2 budget.
Ready to connect★ 1k
- View details
ase-topic-selectionSkillDev tools
Use when deciding whether a software-engineering project belongs at ASE (IEEE/ACM Automated Software Engineering) or should be routed to ICSE, ESEC/FSE, ISSTA, a PL venue, or an SE journal, and when distinguishing ASE by its automation-centric contribution shape, its tool/technique emphasis, and its
Ready to connect★ 1k
- View details
ase-workflowSkillDev tools
Use when planning an ASE (IEEE/ACM Automated Software Engineering) research-track campaign backward from the deadline, through abstract registration, the double-anonymous submission, the early-rejection gate, rebuttal, the criteria-bound revision round, artifact evaluation, and the camera-ready in b
Ready to connect★ 1k
What is a skill?
A skill is plain text, usually a SKILL.md file and the scripts it refers to, written for an AI rather than for a person. It carries the steps, the house rules and the examples a good answer needs, so you stop pasting the same briefing into every new chat.
55,111 of the 55,543 skills listed here can be served through ahel today, and they come from public repositories. Each one has its own page with the instructions themselves on it, so you can read what a skill will tell your AI to do before you install it.
Install one and every AI you use gets it
Installing a skill adds it to your gateway and turns it on in the same step. Claude Code surfaces it as a slash command; any client can read the full instructions with the skill_read tool.
Nothing is copied into a project folder. The instructions are served from your account, so the same skill is there in every AI you connect, and turning it off removes it from all of them at once.