Total 50,893 skills, Tools & Utilities has 8296 skills
Showing 12 of 8296 skills
Route durable graph-building requests into one honest mode: assistant-native install, local Python build, incremental refresh, graph query follow-up, or a graphify-style structural fallback for markdown-heavy corpora. Use when the user wants `GRAPH_REPORT.md`, `graph.json`, `graph.html`, repo/corpus relationship tracing, mixed code+docs+asset graphing, or graph-backed architecture understanding that should persist across sessions. Route simple locate/reference work to `codebase-search`, narrative knowledge-base work to `llm-wiki`, and project-memory handoff to `opencontext`.
Search PubMed for scientific literature, including published clinical trials. Fetch abstracts and full text. Link published research to biological databases (gene, protein, nucleotide, PubChem) to discover associations between papers and specific compounds or genes. Verify medical spelling, match raw citations, and cache result sets for bulk processing. Interfaces NCBI E-utilities and PMC BioC APIs.
Performs 3D structural searches of proteins against various databases (PDB, AlphaFold, CATH, MGnify, etc.) using the Foldseek API. Use ONLY when the user provides a physical 3D coordinate file (.cif, .mmcif, or .pdb) and wants to find structurally similar proteins. Do NOT use if the user only provides a protein sequence, gene name, or UniProt ID.
Guides technical support engineering—customer ticket investigation, reproduction, log and API analysis, root-cause isolation, workaround communication, engineering escalation with evidence, and knowledge-base fixes for product bugs and integration issues. Use when debugging a customer-reported issue, writing a repro for engineering, analyzing API errors, drafting technical replies, or improving support runbooks—not for CS program design, renewals, or billing ops (customer-ops-specialist), production incident command (incident-management-engineer), building product features (fullstack-software-engineer), or company-wide crisis statements and launch announcements (communication-lead), or exec/VIP and community escalation program design (community-executive-escalations-program-manager). Product how-to, macros, and ticket triage without deep debugging: product-support-specialist.
Portfolio-level risk controls, drawdown management, exposure limits, and circuit breakers for crypto trading
A qualitative research assistant tool based on Braun & Clarke's Reflexive Thematic Analysis framework. Supports two input modes: (1) Provide raw interview text directly → The skill completes initial TA coding for each document, then proceeds to theme identification after summarization; (2) Provide existing initial coding pool → Directly enter the process of clustering, review, and naming suggestions. Outputs a structured candidate theme table, clearly marking codes with ambiguous boundaries and naming suggestions to be decided by researchers. This skill is triggered when users mention terms such as "thematic analysis", "theme coding", "help me cluster codes", "extract themes from codes", "Braun Clarke", "candidate themes", "how to categorize these codes into themes", "help me check the theme structure", "conduct thematic analysis on interviews". Note the difference from grounded-coding: grounded-coding focuses on category construction and theoretical relationships for procedural grounded theory; thematic-analysis focuses on semantic theme identification following the Braun & Clarke approach, outputting theme structures rather than theoretical propositions.
Help set up and troubleshoot rendering for task files and glossary files. Use when the user asks about PlantUML, AsciiDoc, VS Code, JetBrains, preview rendering, Java, or Graphviz needed to review rendered task or glossary files.
Fulfillment setup — Fulfilled by TikTok, self-fulfillment, shipping templates, return policies
Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate share-ready outputs.
This skill should be activated when the user requests to "deepen a topic", "analyze a topic", "help me write an outline", "will this topic go viral", "help me diagnose a topic", "is this topic worth pursuing", or "how to improve this topic". Even if the user only shares a topic and asks for opinions, you should proactively initiate the diagnosis process instead of providing a simple response. Driven by the cognitive hijacking theory, it features four modules: Perspective Collision (challenging the topic's premise), Topic Diagnosis (graded using 🛵🚗✈️), Outline Design (emotional peak planning), and Style Validation (alignment with li-writer style). It generates a comprehensive deepening report and saves it as a file. Do NOT trigger this skill for: merely recording topics (use li-recorder), directly writing scripts (use li-writer). Use when the user wants to "develop a topic", "analyze topic potential", "write an outline", "will this topic go viral", or needs full topic diagnosis + outline design. Trigger even if the user just shares a topic and asks for opinions.
Organizes research notes into a structured wiki knowledge base with wikilinks ([[slug]] syntax), cross-references, and an auto-generated index. Use when the user asks to build a wiki, organize notes into a knowledge base, create an index, or sync notes into a structured format.
Analytics dashboard and inventory management toolkit for Roblox Murder Mystery 2 game data tracking and optimization