Loading...
Loading...
Found 10,876 Skills
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Huawei Ascend NPU natural language management skill, supporting both local direct connection and SSH remote modes. Provides comprehensive npu-smi command capabilities including device queries, configuration management, firmware upgrade, vNPU virtualization, certificate management, and compute power testing (FLOPS). Enables remote management and monitoring of Ascend NPU devices with real-time metrics tracking. Use this skill when the user wants to: (1) query NPU device status and health, (2) monitor temperature, power, memory/HBM utilization, (3) configure ECC settings and fan modes, (4) perform firmware upgrades, (5) manage vNPU virtualization, (6) run compute power tests, (7) check certificate information. Trigger: user mentionsnpu', 'ascend', 'NPU', 'Ascend', 'temperature', 'power', 'HBM', 'firmware', 'upgrade', 'vNPU', 'virtualization', 'certificate', 'FLOPS', 'compute', 'health', 'memory', 'utilization', 'ECC', 'fan', '昇腾', '昇腾卡', '昇腾状态', '显存', '算力', '设备查询', 'NPU监控'"
Design and build data presentations — slide decks, board and investor decks, QBRs, analytics readouts, launch and sales decks, conference talks, and interactive web decks — that hold up in a room, in an inbox, and on a phone. Use whenever the user wants slides or a presentation: "make a deck", "turn this into slides", "board deck", "pitch deck", "QBR", "readout", "all-hands", "present these results", "PowerPoint", "pptx", "Google Slides", "keynote", "talk", "webinar", "speaker notes", "slidedoc", "reveal.js", or an interactive/HTML deck — even if they only say "put this in slides" or "we're presenting this Thursday". Covers storyline, slide layout and type specs, staged chart reveals, presenter mechanics, accessibility, and the build path (self-contained HTML, .pptx, Google Slides, or a spec). Composes with dreambase-data-stories, dreambase-visualization-design, dreambase-echarts, and any brand guide, design.md, or .potx the user supplies.
Check a citation against the registry of record instead of recalling it. Use this to verify that a DOI or a reference actually exists, to get the real title, authors, journal, year, licence, funders and citation counts behind a DOI, to find the DOI for a half-remembered paper title, to audit a bibliography or reference list before it ships, to resolve an ORCID iD to a researcher's employments, educations and recent publications, and to tell two same-named authors apart. Reach for it whenever an invented citation is the way the task fails — a fabricated reference reads exactly like a real one, with a plausible journal, plausible authors and a DOI of the right shape, and only the registry separates them. Crossref holds what publishers deposited and ORCID holds what researchers claim; neither is recallable from training data. Browsing, searching and dry runs cost nothing and need no wallet; a real call costs $0.003 to $0.004 in USDC on Base, with no signup, no API key and no gas.
Brand Registry enrollment guide — eligibility, application, benefits, A+ Content access, brand protection tools
Filter an existing audience or lead list against your ICP and split it into ready-to-sequence segments. Use when someone already has a list of people — an audience in their sales tool, a CSV or CRM export, event or webinar attendees, registrants, a Sales Navigator import, a newsletter or community export — and wants to know who is worth contacting. Triggers on: 'filter this audience against my ICP', 'who in this list matches my ICP', 'clean up this lead list', 'score these leads', 'qualify my signups', 'segment this audience', 'is my audience on-ICP', 'filter my webinar attendees', 'split this audience by ICP fit', 'remove the bad leads'. For SDRs, BDRs, RevOps, growth, demand gen and founders doing list qualification, ICP refinement, post-event follow-up or audience cleanup. Checks whether the data can support the ICP before filtering, sorts every lead into ICP match / needs review / no match, strips out your own team and competitors, and never silently drops anyone. Maintained by La Growth Machine.
Example-first AI development guide for Hile @hile/* packages. Use when building or editing Node.js/TypeScript services with @hile/core, @hile/http, @hile/http-next, @hile/rsc, @hile/model, @hile/context, @hile/typeorm, @hile/ioredis, @hile/cache, @hile/message-*, @hile/micro, @hile/reloader, Redis reliability packages, @hile/schedule, or create-hile.
Use interfaces and dependency injection to decouple code; bind implementations in the container
Store and serve files via Storage; set visibility, generate URLs, and handle streaming safely
Analyze candidate models before adapter implementation. Determine model implementation source (transformers or model-local), structural features, layer-by-layer loading requirements, and MoE fused weight risks. Use this skill when the user wants to: (1) assess model adaptation feasibility before creating msModelSlim adapters, (2) analyze model structure and type classification, (3) evaluate MoE compatibility for quantization. Trigger: user mentions "model analysis", "msModelSlim", "adapter", "transformers", "MoE", "layer-by-layer", "model assessment", "feasibility", "模型分析", "适配可行性", "模型评估", "MoE分析"
Conduct a structured business-logic interview for a new feature, asking questions iteratively until shared understanding is reached, then save a clean spec doc to `docs/<feature-slug>-business-logic.md`. The skill always writes the spec to disk and always stops there — it never continues into implementation planning. Use during planning — before any code or file paths are discussed — whenever the user wants to add a feature, change a flow, or scope new behavior. Trigger on phrases like "I want to add X", "let's plan a new feature", "we need to support Y", "I'm thinking about a feature for Z", "scope out…", "let's figure out what should happen when…", or any time the user describes a new capability and the next move is clarifying *what* it should do (not *how* to build it). Triggers even if the user doesn't say "plan mode" or "business logic" — if a feature is being scoped, this is the right skill. Refuses to discuss code, file paths, schemas, libraries, or implementation; redirects back to user behavior and business rules. Output is a saved markdown spec; running the implementation-planning skill afterward is a separate, user-initiated step.
Create tiny no-text Milvus-style sticker memes for technical marketing, WeChat-style article moments, community posts, and developer-group reactions. Use when the user wants an original meme/sticker with an abstract Milvus bird/eagle mascot, strong exaggerated emotion, internet-native sticker energy, light-blue accents without making the whole character blue, and deterministic small-size exports such as 512, 240, 120, or 50 px.