Total 57,514 skills
Showing 12 of 57514 skills
Write interactive planning documents as ForgeDoc markup, build them to a single self-contained HTML file, and read a pasted feedback bucket back. Use whenever you are asked to plan work, write a design doc, propose an approach, or collect decisions from a human reviewer.
Call use_skill as your FIRST and ONLY action when the user asks to DELETE, REMOVE, or GET RID OF an existing run configuration for Mule applications. Use this ONLY for deleting/removing configurations, NOT for creating or editing. Trigger phrases include "delete config", "remove config", "get rid of config", "delete all configs", "remove all my run configs", "clean up configs". When you call use_skill, it must be the only tool call in that response.
Use when building notifications with Courier across email, SMS, push, in-app inbox, Slack, Teams, and WhatsApp: sends, templates, Elemental, journeys, preferences, routing, CLI and MCP.
ALWAYS use this skill BEFORE writing or modifying ANY Windows/Win32, COM, or native interop code — any language calling Windows APIs (C/C++, Rust FFI, C#/P-Invoke, PowerShell). Enforces Unicode W-suffix APIs only, UTF-16/UTF-8 text discipline, documented failure-value checks (HRESULT, LSTATUS, GetLastError), and RAII ownership for handles, buffers, and COM allocations. MANDATORY even for trivial snippets.
Scores a draft against the measurable patterns of recent award-winning and top-cited papers at a target venue, producing a shareable venue-fit scorecard. Use when a researcher asks "score my paper", "how does my paper compare to best papers at SIGSPATIAL/NeurIPS/...", "is my paper good enough for this venue", "benchmark my draft against award winners", "rate my paper out of 10", or wants a readiness scorecard before submitting. Builds an exemplar corpus via study-exemplars, extracts comparable structural and rhetorical features from the draft, and reports a per-dimension scorecard plus an overall venue-fit index — explicitly a conformance measure (does the draft match the form of strong work at this venue), never a prediction of acceptance, award, or scientific quality. Trigger words - score my paper, rate my paper, benchmark, scorecard, compare to best papers, award winners, venue fit, am I ready to submit.
Builds a conference talk deck (Beamer or Marp markdown) from a paper draft - problem-first narrative, one claim per slide, figures reused straight from the paper's LaTeX source, sized to the real slot (12-20 minute full talk vs 5-minute lightning). Use when the user asks to make slides, build a presentation or talk deck for an accepted paper, turn a paper into a talk, prepare a conference presentation, fit a talk into N minutes, or check and trim an existing deck that is too long or too text-heavy. Inventories the paper's figures by in-text reference count, computes a minutes-and-slides budget per section, drafts the deck, and deterministically lints pacing, overfull slides, missing or unrenderable figures, and generic non-claim titles. Venue profiles give context only; the slot length must come from the venue's presenter instructions or acceptance email.
Diffs a paper draft against a machine-readable venue profile and produces a four-part tailoring plan - contribution reframing for the chosen track (research vs applications/industry vs demo vs short/vision), a page-budget cutting plan, a template/documentclass switch plan (acmart, IEEEtran, NeurIPS-style, llncs), and an anonymization sweep matched to the venue's blind level. Use when the user wants to adapt, retarget, resubmit, or port a paper to a different conference, journal, or track; fit a paper into a page limit ("cut to 10 pages"); switch LaTeX templates ("convert IEEEtran to acmart"); anonymize for double-blind review; or asks "make this fit SIGSPATIAL/NeurIPS/ICDE/KDD", "which track should this go to", or "retarget my rejected paper".
Runs a two-pass paper reflection loop with a Researcher pass and a Writer pass. Use when the user asks to reflect on a paper, improve a draft, run a research-agent and writer-agent review, critique the paper before submission, find both technical and writing issues, or produce a revision plan. The Researcher pass checks claims, citations, evidence, venue fit, missing related work, and reviewer risk; the Writer pass checks framing, structure, abstract, related work, prose, tables/figures, and response clarity. Outputs a merged action plan with evidence, priority, owner, and next skill to run.
Bridges an Overleaf project to the local skills so a paper kept on Overleaf can be checked, polished, and reviewed, then synced back. Use when a researcher says "my paper is on Overleaf", "sync my Overleaf project", "pull my paper from Overleaf", "run preflight on my Overleaf paper", "edit my Overleaf project locally", or "push my changes back to Overleaf". Walks the three real paths — Overleaf Git integration (clone as a local repo), GitHub synchronization, or download-as-ZIP for free accounts — gets the .tex into a local working copy the other skills operate on, and guides syncing changes back. Treats the Overleaf access token as a secret, never auto-pushes without confirmation, and re-verifies the current Overleaf method live since premium availability and steps change. Trigger words - overleaf, my paper is on overleaf, sync overleaf, pull from overleaf, push to overleaf, edit overleaf locally.
Goal-driven conductor for the whole idea-to-published-paper lifecycle. Takes a research idea plus experiments and a target ("submit to NeurIPS 2026", or "help me pick a venue") and runs a goal->plan->execute->verify->reflect loop. It plans the stages, invokes the right lifecycle skills in order (literature-review, write-abstract, preflight-check, simulate-reviewers, and the rest), checkpoints with the author before each stage, and re-verifies the live CFP via parse-cfp rather than trusting a cached profile. Use when a researcher says "take my idea to a submitted paper", "run the whole pipeline", "orchestrate the paper for venue X", "what's the plan from here", or "what's done and what's next". Copilot, not autonomous author. It stops to ask at every stage gate, never fabricates results or citations, and never submits. Trigger words - orchestrate, pipeline, end to end, whole paper, idea to submission.
Builds a structured literature review — survey of prior work, state of the art, related-work landscape — where every claim cites a verified reference. Use when the user says "literature review", "lit review", "survey the papers on X", "what's the state of the art", "synthesize prior work", or "organize these papers by theme". Composes sibling skills, search via find-papers (key-free DBLP/Crossref/Semantic Scholar/arXiv), full text via fetch-paper (legal open-access only), and citation checking via verify-citations. Tracks a screening corpus, extracts claims with section-level anchors, organizes by theme, and gates the final document with a deterministic checker so no claim ships uncited, unverified, or resting on a fabricated reference.
Writes, rewrites, and lints venue-aware paper abstracts and prepares abstract-registration packages. Enforces venue length norms (e.g. LNCS 150-250 words), generates the correct keywords block (ACM CCS Concepts, IEEE Index Terms, LNCS \keywords, or none for NeurIPS-style), structures the abstract as motivation-gap-approach-results-impact, and builds the abstract-registration card (title, abstract, authors, topics, conflicts/COI, deadline countdown) for venues with a separate abstract deadline. Use when the user asks to write, revise, shorten, lengthen, or polish an abstract; asks about abstract word limits, CCS concepts, index terms, or keywords; or needs to register an abstract / meet an abstract-registration deadline (NeurIPS, ICML, KDD, CVPR, CHI, SIGSPATIAL) before the full-paper deadline.