Total 58,173 skills
Showing 12 of 58173 skills
Conventions for authoring and maintaining GitHub Actions workflows. Pin each action to its latest version, read the Node version from .node-version (else latest LTS), and set up pnpm via the setup-pnpm action instead of corepack. Use when creating a workflow, adding or editing jobs or steps, or updating action versions in an existing workflow.
Apply the same orchestration as `/efficient-fable` to any high-cost frontier model: delegate research, coding, and testing to cheaper subagents while keeping planning, synthesis, and final review with the expensive model.
Create, edit, replicate, and iteratively refine editable research and technical diagrams in diagrams.net/draw.io (.drawio XML) from prompts, papers, repositories, screenshots, or existing diagrams. Use when asked to generate a scientific figure, paper method diagram, ML/system architecture diagram, draw.io file, reference figure reproduction, browser screenshot feedback loop, Windows-safe draw.io preview, or layout fixes for text overlap, arrows, colors, icons, fonts, and component alignment.
Export Blender scenes to glTF/GLB (web/AR), FBX (game engines), OBJ (universal), USD (VFX pipelines), STL (3D printing). Includes per-format settings, embed/unpack textures, axis conversion, polygon optimization (Decimate), and target-platform validation. Use whenever the user asks to "export this", "save as glTF / FBX / OBJ / STL / USD", "package for Unity / Unreal / Three.js / web / AR / 3D print", or any output format conversion. Make sure to use this skill even if the user does not say "export" — also covers "package this for the web", "make it work in Unity", "send to Unreal", "save for 3D printing".
Opt-in evidence-first causal diagnosis for bugs, browser or app/device failures, flaky behavior, and performance regressions. Activate only when the user explicitly invokes `$diagnose` or explicitly asks to use the named diagnose skill. Do not activate merely because the user mentions a bug, asks why something failed, requests debugging or a fix, or describes unexpected behavior. Once explicitly invoked, locate likely causes, instrument relevant boundaries with extensive structured logging, reproduce the issue, analyze the collected logs, rank causes with confidence scores, and pursue 100% operational confidence while probes can increase confidence.
Identify which area of the mirror world the current event falls into (Controllable Domain/Blind Domain/Probabilistic Domain/Risk Domain), adopt corresponding survival strategies, and avoid using the deterministic rules of the left-side world to face the uncertain problems of the right-side world. It is suitable for formulating strategies for investment decisions, entrepreneurial choices, and career transitions, as well as retrospective analysis of "why did the execution according to plan fail?". It is not applicable to pure skill improvement and deliberate practice scenarios (which naturally belong to the Controllable Domain). Key trigger signals: "Why isn't hard work paying off?", "Is this matter based on strength or luck?", "How should I deal with uncertainty?", "How to improve the success rate?"
Remove the two seals of the brain (negative words and negative emotions) and restore rational thinking ability. It applies to scenarios where the brain "crashes" and cannot think when facing pressure, setbacks, or conflicts, as well as long-term mindset optimization. Use this skill when you are trapped in a self-denial cycle of "I can't", "I can't do it", "There's no way", or overwhelmed by emotions such as anger, anxiety, or fear. It is not applicable to mental health problems requiring in-depth psychotherapy (e.g., depression and anxiety disorders require professional medical treatment), nor to pure knowledge learning bottlenecks (that is a method problem, not a seal problem). Key trigger signals: "I can't/I can't do it", "I'm furious/I'm so anxious", "My mind is blank", "The more I think, the more annoyed I get", "I can't control myself".
Use the 'Dialysis Prism' framework to penetrate the surface of problems and identify their root causes. Resolve persistent recurring issues through three steps: calibrating Goal B, reconstructing Method A, and eliminating Variable C. It applies to scenarios where the same problem keeps recurring despite various attempted solutions, as well as analytical scenarios that require precise problem definition before resolution. Use this skill when you find that 'patchwork' solutions are ineffective. It is not suitable for scenarios in entirely new fields with no historical methods to reference, nor for purely uncertain events (which fall under the probability/risk domain and require the use of mirror-world). Key trigger signals: 'Why does this problem happen again?', 'Why can't we solve it for good?', 'I've tried so many methods but none work', 'What exactly is the root cause of this problem?'
Analyze complex systems from elements to relationships, from parts to the whole, and from static to dynamic perspectives. Suitable for scenarios where problems recur, where a single change affects the entire system, and where treating symptoms doesn't work. When you find that 'the harder you work, the worse it gets' or 'problems keep recurring', you need to switch to systematic thinking to find root solutions. Not applicable to simple single-cause problems or emergency scenarios requiring quick action. Key trigger signals: 'Why does this problem keep recurring?', 'Fixing A broke B instead', 'Feeling stuck in a loop'.
Find the perfect gaming monitor on Newegg by asking the user about their needs and returning the top matching monitors with parsed specs (size, resolution, refresh rate, panel type, response time) and direct purchase links. Use this skill whenever users want help choosing or finding a gaming monitor — even if they don't mention Newegg by name. Always trigger on phrases like: "help me find a gaming monitor", "what monitor should I buy for gaming", "recommend a 144Hz/240Hz monitor", "best monitor for FPS games", "I need a monitor under $X", "OLED gaming monitor recommendation", "curved ultrawide monitor for gaming", "我想买个电竞显示器", "推荐一个游戏显示器", "帮我找显示器", "144Hz显示器推荐", or any question about choosing or comparing gaming monitors for purchase. This skill handles the full flow: gathering requirements → searching Newegg → parsing specs → showing ranked results with clickable buy links.
Show license information for all project dependencies. Use when checking license compliance, reviewing license compatibility, or auditing for copyleft or missing licenses.
Write, split, rename, or repair an agent skill so it activates when it should and can be proved rather than believed: a new skill, a description that never fires or fires on everything, a rule that has grown two decisions, an index that routes nothing an agent can see, a file too dense to read in one pass, or a check suite nobody has watched fail. Covers the activation surface, the routing gate, rule anatomy, page shape, naming, portability, and the invariant and mutation scripts. Use when the user says "write a skill", "this skill never triggers", "split this skill", "standardise these skills", or "how do I check this skill". Not for authoring product documentation, and not for deciding whether a task needs a skill at all.