Builds background-gap-objective logic for biomedical manuscript introductions with clear study positioning and disciplined narrative structure.

Converts a biomedical study storyline into a graphical abstract and, when direct image capability is available, generates the graphical abstract directly; otherwise it falls back to prompts, Mermaid flowcharts, or designer-facing briefs.

Writes Specific Aims pages for grant applications. Use when drafting or revising the Specific Aims page (NIH R01/R21/R03), NSF Project Summary, or equivalent for any major funding agency. Also triggers on "write my specific aims", "help me draft specific aims for NIH", "what should a specific aims page include", "NSF project summary", "write my grant aims", or "how do I structure an R01".

Writes complete, publication-grade figure legends that can stand on their own. Use when writing or revising figure legends for any scientific figure — bar charts, line graphs, scatter plots, box plots, heatmaps, survival curves, flow cytometry plots, western blots, microscopy images, or schematic diagrams. Also triggers on "write a figure legend for", "help me describe this figure", "my figure needs a legend", "write Figure 1 legend", or "what should a figure legend include".

Composes a Discussion around key findings, mechanisms, clinical relevance, and limitations. Use when writing or improving a Discussion section for any biomedical manuscript — including interpreting results, connecting to prior literature, addressing unexpected findings, framing limitations, and writing the conclusion. Also triggers on "write my discussion", "help me discuss my findings", "how do I compare to prior studies", "write the limitations paragraph", or "draft a discussion for my paper".

Drafts journal-ready cover letters for manuscript submission. Use when preparing a submission package, communicating the manuscript's contributions and journal fit to editors, or tailoring the novelty framing for a specific journal's scope. Also triggers on "write a cover letter for my paper", "draft a submission cover letter", "help me write to the editor", or "cover letter for [journal name]".

Checks consistency across title, abstract, methods, results, figures, tables, and supplements to identify internal contradictions and version drift in biomedical manuscripts.

Condenses a full study into conference-submission abstract format. Use when adapting a manuscript abstract or study summary to meet a specific conference's word limit, structured format (Background/Methods/Results/Conclusion), character limits, or required section headings. Also triggers on "adapt my abstract for [conference]", "shorten my abstract to 250 words", "reformat for ASCO/ASGCT/SfN/AACR", "I need a conference abstract", or "cut my abstract to fit the word limit".

Calibrates manuscript claim strength so wording matches the actual evidence level, study design, and validation status.

Turns reviewer comments into structured, professional point-by-point responses linked to manuscript revisions, clarifications, rebuttals, and additional analyses.

Run a submission-readiness preflight on a manuscript before arXiv upload. Use when the user is preparing an arXiv submission, asks to check a paper before uploading, mentions hallucinated or fake references, leftover LLM meta-comments / prompts in text, placeholder data (TODO, TBD, XX%), AI-use disclosure, scholarly integrity, research integrity, or arXiv moderation risk — even if they don't say "preflight". Also trigger on phrases like "check my paper before arXiv", "verify my references", "scan for AI artifacts", "scan for LLM residue", "is my submission ready", or "review .tex/.bib before submit".

JSON input and output schemas for all perplexity-cli commands (search, ask, chat). Use when constructing --json payloads or parsing command output programmatically.

Agent recipes, piping patterns, scripting idioms, and common workflows for perplexity-cli. Use when constructing multi-step queries, piping output, or integrating into agent workflows.

Model selection guide for perplexity-cli ask and chat commands. Use when choosing between sonar, sonar-pro, sonar-reasoning, and sonar-deep-research.

Full command syntax, all flags, and worked examples for perplexity-cli search, ask, and chat commands.

Use this skill when the user asks to write, generate, run, fix, or migrate unit tests in a Node.js or TypeScript repository that has @vitronai/themis installed (or when the user explicitly mentions Themis). Covers test authoring with intent(...) and test(...), running the suite via `npx themis test`, reading agent-readable failure output, and incremental migration from Jest or Vitest.

Use this skill when the user asks to write, generate, run, fix, or migrate unit tests in a Node.js or TypeScript repository that has @vitronai/themis installed (or when the user explicitly mentions Themis). Covers test authoring with intent(...) and test(...), running the suite via `npx themis test`, reading agent-readable failure output, and incremental migration from Jest or Vitest.

Drive a real browser with plain English via Alethia — the patent-pending zero-IPC agent-driven testing runtime. Use when the user asks to smoke-test a local app, run an accessibility (WCAG) or security (NIST SP 800-53) audit, prove the EA1 safety gate works, bootstrap test coverage on an unknown page, run parallel multi-page checks, or export a cryptographically signed evidence pack. Requires the @vitronai/alethia MCP server to be configured. Trigger patterns include "test this page," "verify the login flow," "audit accessibility," "compliance audit," "run WCAG/NIST," "check that deletes are blocked," and similar.

Generates Express REST APIs.

Interactive cross-feature navigation architect for Nicolify. Audits all routes and sidebar entries, maps user journeys across studios, detects orphaned features and dead-end flows, proposes navigation improvements with ASCII diagrams, generates clickable multi-page HTML prototypes on localhost:8888, and outputs FLOW-SPEC.md plus per-screen UI-SPEC updates for implementation agents. Use when the user asks about navigation coherence, user flows, journey mapping, orphaned features, dead-end screens, sidebar reorganization, cross-studio navigation, or feature discoverability. Triggers: 'flujo de usuario', 'navegación', 'journey', 'user flow', 'sidebar', 'rutas huérfanas', 'orphaned routes', 'dead end', 'flow audit', 'navigation audit', 'ux-flow', 'flow architect', 'cómo llega el usuario', 'discoverability', 'no encuentro', 'dónde está', 'reorganizar navegación', 'cross-feature flow', 'audita la navegación', 'mapa de rutas', 'flujos de la app'.