Explore

Use when the user asks about research themes, topic distribution, BERTopic clustering, topic overview, topic papers, topic merges, or HTML topic visualizations.

Use when the user wants a technical report, topic report, research briefing, structured investigation, evidence synthesis, recommendations, or final report packaging.

Use when the user wants to read a paper or inspect metadata, abstract, conclusion, full text, figures, or detail levels L1 through L4.

Use when incrementally reviewing and repairing low-quality metadata after enrich, especially non-standard documents that need title, author, or year correction while skipping already reviewed records via .scrubbed.

Use when evaluating, adding, or upgrading ScholarAIO support for a scientific computing tool, especially integration-gate review, official docs ingestion, toolref integration, lightweight skill design, and end-to-end CLI verification.

Use when serving scientific CLI tasks through ScholarAIO, especially when the agent should prefer scholaraio toolref, handle partial coverage safely, or avoid turning user work into documentation maintenance.

Use when the user receives peer review comments and wants a rebuttal, response letter, point-by-point reply, or evidence-backed revision response.

Use when the user wants to identify research gaps, open questions, unexplored areas, cross-paper limitations, or future directions from workspace literature.

Use when the user wants to normalize paper directory names to Author-Year-Title format after metadata correction or audit cleanup.

Use when working on first-principles materials calculations with Quantum ESPRESSO, including SCF, band structures, DOS, phonons, electron-phonon coupling, Fermi surfaces, or charge density.

Use when the user says a paper, review, report, or LaTeX deliverable is final and wants it archived under published/ or exposed through the static published-paper site.

Use when the user needs an academic poster, conference poster, poster-style visual summary, section planning, figure-text balance, or poster packaging workflow.

Use when the user has a patent publication number, patent URL, or patent-search result and wants the PDF fetched into the configured patent inbox.

Use when the user wants help drafting or revising a research paper section, including Introduction, Related Work, Method, Results, Discussion, or Conclusion.

Use when the user wants guided reading, deep reading, or structured analysis of a single paper, starting from fuzzy keywords or a research question.

Use when working on CFD cases with OpenFOAM, including solver selection, dictionary setup, mesh workflows, turbulence models, or flow and heat-transfer verification.

Use when the user explicitly asks for Nature Skills, nature-skills, Nature style, Nature-style, Nature Communications, Nature-family, CNS, high-impact journal, or Springer Nature workflows, including Nature figure work, polishing, writing, reviewer critique, high-impact journal major revision response, Nature/CNS citations, Nature data-sharing workflows, paper readers, reviewer response, paper-to-PPT, submission checklist, or Nature-specific academic-search workflows.

Use when the user asks about LLM token usage, API call timing, runtime metrics, cost signals, or performance statistics.

Use when working on classical materials simulations with LAMMPS, including potential selection, shock or deformation setups, thermodynamic runs, or structure analysis for solids and nanomaterials.

Use when the user wants to analyze research behavior, search hot keywords, most-read papers, reading trends, active workspaces, or unread semantic neighbors.

Use when the user wants to process new papers, patents, theses, documents, or proceedings from inbox queues into the knowledge base, run the ingest pipeline, or rebuild indexes.

Use when the user wants to rebuild or refresh ScholarAIO keyword, full-text, FTS5, FAISS, or semantic search indexes after data or metadata changes.

Use when the user wants to import papers from Endnote XML/RIS, Zotero Web API or local SQLite, attach PDFs, match PDFs to records, or supplement records with PDF content.

Use when working on biomolecular molecular dynamics with GROMACS, including system setup, equilibration, production runs, trajectory analysis, or MM/PBSA-style post-processing.

Use when the user asks about citation relationships, references, citing papers, shared references, bibliographic overlap, or graph-style paper connections.

Use when the user needs BibTeX, RIS, Markdown reference lists, filtered citation exports, custom citation styles, or a Markdown-to-DOCX export for sharing.

Use when the user wants to survey a journal or field, fetch papers from OpenAlex, cluster topics, build exploration embeddings, or search named explore libraries under data/libraries/explore.

Use when the user wants LLM-based metadata enrichment, table-of-contents extraction, L3 conclusion extraction, or abstract backfilling for library papers.

Use when the user wants diagrams, flowcharts, architecture visuals, data relationships, timelines, concept maps, Mermaid, Graphviz, drawio, or polished paper figures generated from structured text or IR.

Use when the user wants to create or inspect DOCX, PPTX, or XLSX files, generate a downloadable Office deliverable, or verify its structure and layout warnings with scholaraio document inspect.

Use when the user asks about highly cited papers, citation rankings, or updating citation counts from external APIs.

Use when the user wants to verify citations in AI-generated or human-written text against the local knowledge base and catch hallucinated, wrong, or missing references.

Use when working on bioinformatics workflows such as alignment, variant calling, phylogenetics, or protein-structure analysis, especially across BLAST, minimap2, samtools, bcftools, MAFFT, IQ-TREE, or ESMFold.

Use when the user wants to back up or restore ScholarAIO data through configured rsync targets, inspect backup plans, or run a dry-run before transferring files.

Use when the user wants to check paper-library data quality, diagnose missing metadata, filename issues, DOI duplicates, title mismatches, or repairable metadata problems.

Use when the user wants to browse arXiv preprints, search arXiv directly, fetch a PDF by arXiv ID or URL, or send a preprint into the ScholarAIO ingest pipeline.

Use when the user needs help choosing or organizing an academic-writing workflow by deliverable, stage, or format, including review articles, guided reading, paper sections, PPT or slides, posters, and technical reports.

Search and analyze your own session logs (older/parent conversations) using jq.

Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).

This skill should be used when the user needs to automate multi-step website tasks. Activates for browser automation, web scraping, UI testing, or building AI agents. Provides complete action manuals with step-by-step instructions and verified selectors.

Use before opening a PR to audit the changes for stale comments, unused imports, missing tests, and inconsistencies with neighboring code.

Use before connecting a new MCP server to your agent — produces a structured security review covering source, permissions, tools, network, and approvals.

Use after a session to promote useful episodic notes from logs/episodic/ into distilled, dated entries in MEMORY.md and memory/semantic/.

Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output when live inspection is practical. Use this skill instead of modifying source code with temporary logs, print statements, or console output.

Hand over your current coding session so the user can continue the conversation on their phone or another device via any IM channel connected to VibeAround. Use when the user says "/vibearound handover", "hand over this session", "continue on my phone", or similar session transfer requests.

Resolve your current session ID for use with other VibeAround tools. Called by other skills that need session context (e.g. va-preview, vibearound handover).

Initialize and wait for VibeAround subagents in a multi-agent coding turn. Use when the user's message starts with "subagent=", especially "subagent=parallel".

Harness-agnostic version of `/implement`. Drives a single workshop ticket through the SWE→Tester loop in ONE conversation, with the role prompts bundled as `agents/software-engineer.md` and `agents/tester.md` instead of being launched as subagents. Resolves the ticket from `implement_yourself/tasks/`, creates an `implementing/from-scratch` branch (a fixed default — not derived from the ticket; subsequent tickets stack on top), adopts the software-engineer role to implement, then switches to the tester role to verify (logic tickets only). Loops on FAIL up to 3 times, moves the file to `tasks/done/`, then commits directly with `git commit -m`. Stops after one ticket. Trigger when the user types `/implement-universal`, asks to "implement task NNN without subagents", or is running in a harness (Cursor, Windsurf, plain Claude API client, etc.) that doesn't support Claude Code's `Task` tool.

Generate a LinkedIn post using the LinkedIn Writer MCP server. Use this skill whenever the user wants to write a LinkedIn post, create social media content, draft a post from research, or generate a post with an image. Triggers on: 'write a post', 'create a LinkedIn post', 'draft a post about', 'turn this into a post', 'generate a post', or any request involving LinkedIn content creation. Also use when the user has a guideline.md and research.md ready.

End-to-end workflow: research a topic and then write a LinkedIn post about it. Use this skill whenever the user wants the full pipeline — from a topic idea to a finished LinkedIn post. Triggers on: 'research and write a post about', 'create a LinkedIn post about [topic]', 'I want to post about', 'write about [topic] for LinkedIn', or any request that implies both researching a subject and producing a LinkedIn post from it. This is the go-to skill when the user gives you a topic and expects a finished post.

Documents Streamlit CLI commands for running apps, managing configuration, and diagnostics. Use when starting Streamlit apps, configuring runtime options, or troubleshooting CLI issues.

**[REQUIRED]** Use for ALL Streamlit tasks: creating, editing, debugging, beautifying, styling, theming, optimizing, or deploying Streamlit applications. Also required for building custom components (inline or packaged), using st.components.v2, or any HTML/JS/CSS component work. Triggers: streamlit, st., dashboard, app.py, beautify, style, CSS, color, background, theme, button, widget styling, custom component, st.components, packaged component, pyproject.toml, asset_dir, CCv2, HTML/JS component.

Operates as an autonomous software engineer, capable of writing code, running tests, and managing git repositories.

Safely interact with MQTT topics with allow/deny policies and minimal payload risk.

Safely operate Home Assistant by resolving targets first and validating state before writes.

Triage inbox into “needs reply”, “FYI”, “urgent”, and “safe to archive”, with a short plan for each.

Produce a daily news brief (AI/security/dev) with links, key takeaways, and action items.

Organizes repository documentation and keeps new docs in the correct location.

Check whether Claude Code, Claude Agent SDK, and Codex SDK have new versions on npm. Use when the user asks to check for SDK/CLI updates, e.g. "check sdk updates", "check claude code update", "有沒有更新", "檢查 SDK 版本".

View and update your job application tracker. See all applications, filter by status, update progress, and get statistics on your search. Use when someone says 'show my applications', 'how is my job search going', 'update status', or 'tracker'.