Total 57,484 skills
Showing 12 of 57484 skills
Audit load-bearing paper claims against evidence in results, tables, figures, experiments, or citations. Use for claim audits, overclaiming checks, first or state-of-the-art claims, significant-result wording, prose-table number mismatches, and camera-ready or rebuttal evidence checks.
Parses a conference Call for Papers (CFP) URL into a machine-checkable requirements card - deadlines with timezone (AoE vs local), per-track page limits including/excluding references, single/double/triple-blind level, exact LaTeX template invocation, LLM/AI-use policy, rebuttal format, and submission system (OpenReview, CMT, EasyChair, HotCRP, PCS) - emitted as a year-versioned venue-profile YAML conforming to venues/schema.yml. Use when the user shares a CFP or author-instructions URL, asks what a venue's submission requirements, deadlines, page limits, or anonymity rules are, or wants a venue profile under venues/conferences/ created or refreshed for a new submission cycle.
Aligns a draft to a target writing voice — the author's own previous papers, a target venue's published style, or both — so it reads as consistent, native to the venue, and unmistakably the author's. Use when a researcher says "make this match my other papers", "use my usual writing style", "make it sound like my group's work", "match the style of this venue", "align terminology with my prior work", or "make my co-authored draft read consistently". Extracts a measurable style signature (terminology, sentence rhythm, hedging, connective habits, structure) from a corpus the author supplies, diffs the draft against it, and drives a section-by-section alignment that never changes a technical claim, number, or citation. Only the author's own papers and open-access venue exemplars are used; nothing copyrighted is bundled. Trigger words - match my style, my writing voice, sound like my papers, venue style, consistent terminology, align voice, my group's style.
Builds a ranked venue shortlist for a research paper. Use when the user asks where to submit, which conference or journal to target, venue selection, track selection, or mentions CORE rank, h5-index, acceptance rate, CCF class, or submission deadlines. Maps the paper's topic and contribution type (method, system, dataset, demo, vision, industrial, survey) to venue-track pairs scored on topic fit, track fit, prestige signals, and deadline proximity computed from the machine-readable venues/ profiles — with mandatory re-verification of deadlines and page limits against each live CFP before the user relies on them.
Interactively elicits and stores the author's paper positioning so every other skill in this repo behaves context-awarely. Use when a researcher says "set up my paper profile", "ask me about my paper", "what verticals", "configure for my paper", "remember my positioning/style", or is starting a new paper and wants the toolkit tuned before drafting. Asks with sensible options about vertical/emphasis, contribution type, audience and venue tier, risk appetite, and writing preferences, then writes .paper-memory/profile.yml in the paper working directory. Explains how downstream skills consume it for benchmark-paper weighting, simulate-reviewers persona calibration, polish-prose/match-style register, and tailor-to-venue framing. Bundles a stdlib script profile_io.py that reads/writes/validates the file and emits a blank template. Local-only, never uploaded; advisory copilot, never submits.
Creates a new venue-profile YAML for venues/conferences/ from a conference CFP URL, validates it against venues/schema.yml, and preps the contribution PR. Use when the user wants to add a venue, contribute or refresh a venue profile, encode a conference's submission requirements (deadlines, page limits, blind level, template invocation, rebuttal format, submission system) as machine-readable YAML, copy a profile forward to a new year, or validate a profile before opening a pull request. Covers scaffolding the file, extracting facts from the live CFP, the DBLP/Semantic Scholar/Crossref alias table, the mandatory verified provenance block, schema validation, and PR-readiness checks.
Checks a draft for plagiarism, self-plagiarism, text recycling, and uncited near-quotes using several detection methods, and reports overlapping passages so the author can fix them before reviewers or an integrity check do. Use when a researcher says "check for plagiarism", "plagiarism check", "did I copy too much", "self-plagiarism", "text recycling", "am I reusing too much of my own paper", "check originality", "is this too close to the source", or "did I paraphrase closely enough". Compares the draft against sources the user provides (their own prior papers, co-author drafts, suspected sources, or papers fetched on demand), detects internal duplication, and surfaces distinctive phrases to search externally. Honest about scope - it is not iThenticate/Turnitin and has no private publisher corpus; it catches overlap against given sources and publicly findable phrases. Trigger words - plagiarism, self-plagiarism, text recycling, originality, copied, overlap, too close to source, duplicate text.
Renders the paper-workspace (outputs + lifecycle progress) into a single self-contained HTML dashboard the author can open in a browser, and refreshes it on request. Use when a researcher says "show me an HTML view", "give me a dashboard", "can I see my progress in a browser", "visualize what's been done", "make an HTML report", or "update the dashboard". Offered as an option whenever a visual overview would help (it is opt-in, not generated unprompted), and re-run after each significant change so the page stays current. The output is one local dashboard.html with inline CSS — no network, no external assets, light/dark aware — listing every generated artifact by stage with clickable links and a recent-activity timeline. Trigger words - html, dashboard, browser view, visualize progress, html report, update the html.
Iterative, confirmation-driven workflow for building Factorial Code processes and modules end to end — plan-and-confirm, discovery scripts, incremental implementation validated with the run_code MCP tool, exposing processes as MCP tools, plus security and error-handling practices. Use when asked to build, automate, or integrate something on Factorial Code (fcode) and you need the recommended working method.
ALWAYS use this skill BEFORE ANY git commit, push, merge, or PR submission — a MANDATORY pre-commit pass that cleans the staged diff (dead code, duplication, leftover debris), even when the user does not ask for it. Also use on explicit cleanup requests that go beyond the current diff — "clean this up before we commit", "remove the dead code", "dedupe and simplify, then submit" — even when phrased casually. No exception for trivial or single-file commits; only formatting-only changes may skip.
Use this skill when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI, configuration, and observability surfaces.
Build integrations with the Factorial HR API using the official TypeScript (@factorialco/api-client) and Python (factorial-api-client) SDKs. Use when authenticating, calling endpoints, paginating list results, subscribing to webhooks, or typing webhook handler payloads against the Factorial API.