Latest Agent Skills

Use when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE TVCG camera-ready, the Graphics Replicability Stamp, and presentation, with backward-planning offsets for a visualization paper and honest handling of the annual cycle and the second-round revision window.

Use when planning a UAI cycle end to end, from venue-fit confirmation through the winter submission deadline, the spring review and author-response phases, the June decision, the July PMLR camera-ready, and the August conference, as one backward-planned calendar with named owners for anonymity, evidence, and packaging tasks.

Use to build Science's data, code, and materials availability — mandatory deposition in approved repositories, accession numbers, a compliant data-availability statement, and materials/reagent sharing.

RSS Workflow

Use to confirm clinical ethics and research-integrity requirements for an NEJM submission — IRB/ethics-committee approval and informed consent per the Declaration of Helsinki, ICMJE conflict-of-interest disclosures and authorship criteria, the role-of-the-funding-source statement, and the ICMJE data-sharing statement.

Use when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal capacity planning, the Resubmit-to-next-cycle loop, ADS evidence lead times, and ACM e-rights/TAPS camera-ready scheduling for SIGKDD.

Use when planning an ACM IMC campaign end to end, covering the choice between the two annual deadlines, backward planning from the target cutoff, the registration step, the One-Shot-Revision path across deadlines, availability shepherding, the camera-ready and dataset release, and the Replicability Track calendar.

Use to plan an ACM/IEEE HRI campaign backward from the full-paper deadline through the abstract-then-paper two-step, the rebuttal, the program-committee meeting, camera-ready, and the March conference, coordinating the parallel alt.HRI, Late-Breaking Reports, video, and Student Design deadlines.

Use when planning an ESEC/FSE project timeline from venue fit through paper registration, submission, the journal-style Major Revision round, artifact evaluation, PACMSE camera-ready, and presentation, with backward-planning offsets for an empirical-SE paper and honest handling of the single-annual-deadline cycle and cycle-hopping.

Use to plan a full ACM/IEEE Design Automation Conference (DAC) Research-Manuscript campaign backward from the mid-to-late-November manuscript deadline through the two-stage abstract-then-manuscript submission on Softconf, the winter review, the March notification, the April camera-ready and copyright for the ACM Digital Library, and the July conference in Long Beach — with the Engineering-Track and Late-Breaking-Results side calendars.

Use when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk buffers for each stage.

Use when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.

Use when planning an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) campaign end to end — running the year backward from the early-June deadline through the two review rounds, the rebuttal, conditional-acceptance shepherding, the post-acceptance artifact evaluation, and the ACM Open Access camera-ready for the November Hong Kong conference.

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 both IEEE Xplore and the ACM Digital Library.

Use when planning an ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR deadline, the review-response-meta-review timeline, commitment decisions, resubmission loops to later cycles, and camera-ready through ACL Anthology publication.

Use before any writing to stress-test whether a result clears Science's (AAAS) desk-reject filter — broad significance and general interest across disciplines. Decides Science vs Science Advances vs a specialist journal before you invest in prose.

Use to choose the PNAS submission track — Direct Submission (standard, editor-assigned, peer reviewed) vs Contributed Submission (an NAS member communicates their own paper). Covers eligibility, the editor/member role, the discontinued and legacy tracks, and how to pick. Unique to PNAS.

Use to build PNAS's Data Availability Statement and deposition plan — mandatory deposition of data in an approved repository at submission, accession numbers/DOIs, public + archived code, and materials sharing. "Available on request" is not sufficient for primary data.

Use to build Cell's data and code deposition plan and the Data and Code Availability statement that lives inside STAR Methods Resource Availability — approved repositories, accessions/DOIs at submission, and Cell's three-bullet availability format with Mendeley Data as Elsevier's default.

Use before any writing begins to stress-test whether a result clears PNAS's bar — high quality and broad significance to a general scientific readership — and to make the realistic call between PNAS, Science/Nature, and a specialist field journal.

Use this first, before any writing, to stress-test whether a clinical study clears NEJM's bar — practice-changing clinical impact, methodological rigor, and generalizability. Decides NEJM vs Lancet/JAMA vs a specialty journal.

Use when triaging a study before any writing — stress-tests whether it clears Cell's bar (a complete, mechanistic, hypothesis-driven story with multiple converging lines of evidence) or belongs at a sibling. Use this first to decide Cell vs Molecular Cell vs Cell Reports vs Cell Reports Medicine before investing in framing or figures.

Mobile game development principles. Touch input, battery, performance, app stores.

Multiplayer game development principles. Architecture, networking, synchronization.

Game design principles. GDD structure, balancing, player psychology, progression.

Game audio principles. Sound design, music integration, adaptive audio systems.

Web browser game development principles. Framework selection, WebGPU, optimization, PWA.

PC and console game development principles. Engine selection, platform features, optimization strategies.

Game art principles. Visual style selection, asset pipeline, animation workflow.

3D game development principles. Rendering, shaders, physics, cameras.

2D game development principles. Sprites, tilemaps, physics, camera.

Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.

VR/AR development principles. Comfort, interaction, performance requirements.

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.

Performance profiling principles. Measurement, analysis, and optimization techniques.

Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.

Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.

Code review guidelines covering code quality, security, and best practices.

Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.

4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.

React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.

Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

Manage and compress conversation context in long sessions. Detect when context is growing large, summarize completed work phases, archive old findings while preserving key decisions. Prevents context degradation.

PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.

Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.

Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.

Lint and Validate Skill

Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.

Token-efficient code review using Tree-sitter AST graphs and MCP. Reduces AI assistant token usage by 6.8–49x by computing blast radius of changes instead of reading entire codebases. Uses SQLite graph database for structural analysis.

Testing patterns and principles. Unit, integration, mocking strategies.

SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles.

Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.

Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).

Game development orchestrator. Routes to platform-specific skills based on project needs.

Advanced multi-agent orchestration with parallel workers, synthesis protocols, and coordinator lifecycle. Use when complex tasks require multiple agents working in parallel with intelligent result synthesis.

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.

Apply operations across multiple files simultaneously. Pattern-based bulk modifications, search-and-replace across codebases, consistent changes to many files at once.

Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.

Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.