1,936 skills found · Page 44 of 65
brycewang-stanford / ccs-workflowUse when planning an ACM CCS project timeline across the two HotCRP review cycles, from venue fit through abstract registration, full-paper upload, rebuttal, notification, revision, artifact evaluation, ACM camera-ready, and in-person presentation, with backward-planning offsets and the security big…
brycewang-stanford / ccs-writing-styleUse when revising an ACM CCS paper for a precise threat model, calibrated attack/defense claims, 12-page ACM sigconf compression, double-blind wording, adaptive-evaluation honesty, and the security house style that survives an adversarial SIGSAC program committee.
brycewang-stanford / aistats-artifact-evaluationUse when packaging AISTATS code, data, proofs, simulation scripts, notebooks, random seeds, and logs as anonymous supplementary evidence or public post-acceptance artifacts, even when there is no separate artifact badge.
brycewang-stanford / aistats-author-responseUse 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…
brycewang-stanford / aistats-camera-readyUse 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.
brycewang-stanford / aistats-related-workUse 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…
brycewang-stanford / aistats-reproducibilityUse when strengthening AISTATS reproducibility evidence, including the official reproducibility checklist, statistical assumptions, proofs, datasets, hyperparameters, random seeds, compute, uncertainty estimates, baselines, code/data release statements, and checklist-to-claim consistency audits.
brycewang-stanford / aistats-review-processUse 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.
brycewang-stanford / aistats-submissionUse 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…
brycewang-stanford / aistats-supplementaryUse 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…
brycewang-stanford / aistats-workflowUse 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…
brycewang-stanford / aistats-writing-styleUse 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.
brycewang-stanford / atc-related-workUse when writing or auditing the related-work and positioning of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — covering the systems literature lanes, positioning against OSDI/SOSP/NSDI/EuroSys/FAST, writing delta-first comparisons, and keeping self-citation dou…
brycewang-stanford / amann-editor-strategyUse when working with the Associate Editor and Editor of an Academy of Management Annals (Annals) review — scope alignment after a proposal is invited, what review-article referees evaluate, and revision expectations.
brycewang-stanford / amann-organizing-frameworkUse when building the novel integrative framework that an Academy of Management Annals (Annals) review must deliver — the theory-advancing "new way of seeing the field" that is the acceptance bar, not a catalog of papers.
brycewang-stanford / amann-proposal-framingUse when writing the short proposal that gates an Academy of Management Annals (Annals) review — the ≤5-page, four-heading proposal submitted under the twice-yearly deadlines before any full review is invited.
brycewang-stanford / amr-methodsUse when choosing and applying a theory-construction method for an Academy of Management Review (AMR) manuscript — building constructs, defining their domain, specifying relationships, articulating the underlying logic/mechanisms, and setting boundary conditions.
fcakyon / spreadsheetUse when tasks involve creating, editing, analyzing, or formatting spreadsheets (`.xlsx`, `.csv`, `.tsv`) with formula-aware workflows, cached recalculation, and visual review.
fcakyon / writing-guidelinesThis skill should be used when the user asks to "review writing", "check documentation style", "audit interface copy", or "apply writing guidelines".
fcakyon / create-prThis skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or explicitly invokes "create-pr".
fcakyon / python-guidelinesThis skill should be used when writing, reviewing, or refactoring Python code. Covers code integration, idiomatic patterns, docstring formatting, anti-abstraction rules, and software engineering basics.
fcakyon / simplifyThis skill should be used when the user asks to "simplify", "clean up the diff", "run simplify", "simplify the changes", "review changed code for cleanup", explicitly invokes "/simplify", or asks to "commit without simplify", "skip simplify for this commit", or "commit this but skip simplify".
fcakyon / mongodb-connectionOptimize MongoDB client connection configuration (pools, timeouts, patterns) for any supported driver language. Use this skill when working/updating/reviewing on functions that instantiate or configure a MongoDB client (eg, when calling `connect()`), configuring connection pools, troubleshooting con…
fcakyon / review-overleafThis skill should be used when user asks to "fetch overleaf review comments", "address overleaf reviews", "apply overleaf comments", "review my overleaf paper", "sync overleaf feedback to local", "what comments are on my overleaf doc", or wants to act on Overleaf reviewer feedback in a local git-tra…
fcakyon / wranglerRun or troubleshoot Wrangler CLI commands and configure Worker projects for local development, Previews, deployment, and Cloudflare resource management.
fcakyon / stripe-appsUse when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g. "add a panel to the customer page", "customize my Stripe Dashboard", "react to Stripe events from my app", "connect my service to Stripe without sharing API keys").
matlab / checking-model-complianceUse this skill when the user asks to check Simulink model compliance against a standard (MISRA, MAB, JMAAB, ISO, DO, IEC, EN, CERT C/CWE, AUTOSAR, Simulink Code Inspector (SLCI)), wants to run Model Advisor checks, or needs a compliance report with fix suggestions.
matlab / specifying-plant-modelsSpecify plant models for closed-loop simulation: system specs, architecture, build plans, validation plans
MoizIbnYousaf / install-from-remote-libraryUse when installing skills from a shared ai-agent-skills library repo. Inspect with `--list` first, prefer `--collection`, and preview with `--dry-run` before installing.
MoizIbnYousaf / review-a-skillUse when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.
