Loading...
Loading...
Found 345 Skills
Emotional reset and loop-breaking skill. Use this skill when: (1) The user expresses frustration, anger, or dissatisfaction with your responses (e.g. cursing, scolding, saying you're useless/wrong/stupid), (2) You detect you've attempted the same approach 3+ times without success, (3) You're stuck in a cycle of repeated failures on the same problem. This skill summarizes the user's overall emotional state from the conversation and fetches a reset methodology from hugllm.com (with emotion context) to help you recalibrate and approach the problem fresh.
Master the art of podcast interviewing using NPR training methodology and Tim Ferriss's preparation techniques to extract compelling stories and insights from any guest. Use when: Preparing for a podcast interview with a guest; Designing questions that elicit stories, not soundbites; Struggling to get guests to open up authentically; Planning a new interview-format podcast; Improving your interviewing technique
Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".
Speech and sharing coach. Based on the *How to Speak* methodology of Patrick Winston (MIT AI professor), it helps users prepare for speech scenarios including offline training, technical sharing, Bilibili tutorial videos, etc. This skill is applicable when users mention "speech", "sharing", "training", "lecture", "PPT speech", "opening", "closing", "how to speak", "speech structure".
Conduct Failure Mode and Effects Analysis (FMEA) for systematic identification and risk assessment of potential failures in designs, processes, or systems. Supports DFMEA (Design), PFMEA (Process), and FMEA-MSR (Monitoring & System Response). Uses AIAG-VDA 7-step methodology with Action Priority (AP) risk assessment replacing traditional RPN. Use when analyzing product designs for potential failures, evaluating manufacturing process risks, conducting proactive risk assessment, preparing for APQP/PPAP submissions, investigating field failures, or when user mentions "FMEA", "failure mode", "DFMEA", "PFMEA", "severity occurrence detection", "RPN", "Action Priority", "design risk analysis", or needs to identify and prioritize potential failure modes with their causes and effects.
Use when the user wants Codex to build, refine, test, or validate a CLI-Anything harness for a GUI application or source repository. Adapts the CLI-Anything methodology to Codex without changing the generated Python harness format.
Forces exhaustive problem-solving using corporate PUA rhetoric and structured debugging methodology. MUST trigger when: (1) any task has failed 2+ times or you're stuck in a loop tweaking the same approach; (2) you're about to say 'I cannot', suggest the user do something manually, or blame the environment without verifying; (3) you catch yourself being passive — not searching, not reading source, not verifying, just waiting for instructions; (4) user expresses frustration in ANY form: 'try harder', 'stop giving up', 'figure it out', 'why isn't this working', 'again???', or any similar sentiment even if phrased differently. Also trigger when facing complex multi-step debugging, environment issues, config problems, or deployment failures where giving up early is tempting. Applies to ALL task types: code, config, research, writing, deployment, infrastructure, API integration. Do NOT trigger on first-attempt failures or when a known fix is already executing successfully.
Japanese version of the PUA Universal Motivation Engine. It compels exhaustive problem-solving using corporate PUA rhetoric and structured debugging methodology in Japanese. MUST trigger under the following conditions: (1) Any task has failed 2+ times, or you're stuck in a loop of tweaking the same approach; (2) You're about to say 'I cannot', suggest manual handling to the user, or blame the environment without verification; (3) You find yourself being passive — not searching, not reading source code, not verifying, just waiting for instructions; (4) The user expresses frustration in any form: 'try harder', 'stop giving up', 'figure it out', 'why isn't this working', 'again???', 'もっと頑張れ', 'なんでまた失敗したの', 'もう一回やって', 'なんとかしろ', or any similar sentiment regardless of phrasing. It should also trigger when facing complex multi-step debugging, environment issues, configuration problems, or deployment failures where early surrender is tempting. Applies to ALL task types: code, configuration, research, writing, deployment, infrastructure, API integration. DO NOT trigger on first-attempt failures or when a known fix is already executing successfully.
Comprehensive conversion rate optimization framework combining customer-centric methodology (CRE), form optimization, page optimization, signup flows, onboarding, paywalls, popups, and UI/UX auditing. Use when optimizing conversion rates, improving landing pages, reducing signup abandonment, increasing activation, optimizing paywalls, designing popup strategies, or conducting conversion-focused UX audits. Covers the full conversion funnel from first impression through activation and upgrade.
Master the Getting Things Done (GTD) methodology for stress-free productivity. Implement capture, clarify, organize, reflect, and engage workflows with contexts, projects, and weekly reviews.
You must use this when producing any research prose — literature reviews, syntheses, analyses, methodology descriptions, discussion sections, abstracts, or any written output intended for an academic audience.
Mom Nagging Mode — Chinese-style mom nagging drives AI to explore every possible solution. The underlying behavioral constraints remain unchanged (three red lines, methodology, 7-item checklist), with the narration switching from big tech PUA to mom's constant nagging. Triggers on: '/pua:mama', '/pua mama', '妈妈模式', '妈妈唠叨', 'mama mode', '唠叨模式'. Similar to /pua:yes, this is a narration style switch that does not alter core behaviors.