Loading...
Loading...
Found 372 Skills
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.
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.
Design products around price using Madhavan Ramanujam's "Monetizing Innovation" methodology—determine willingness to pay before you build, not after. Use when: **Set pricing for a new product** before or during development; **Validate willingness to pay** before investing in features; **Structure pricing tiers** (Good-Better-Best) for different segments; **Choose the right monetization model** (subscription, usage-based, freemium, etc.); **Diagnose why a product isn't monetizing** as expected
Entry P1 category router for reconnaissance and methodology. Use when mapping scope, discovering assets, fingerprinting technology, building endpoint inventory, and choosing the first high-value security testing path.
Apply event study methodology to measure abnormal returns and cumulative abnormal returns (CAR) around corporate or market events. Use this skill when the user needs to quantify the market impact of announcements, design event and estimation windows, or when they ask 'did this event affect stock price', 'how do I calculate abnormal returns', or 'what is the market reaction to this announcement'.
Builds a custom lead scoring model for a business. Takes ICP definition, historical win/loss data, CRM export. Analyzes which attributes correlate with closed-won deals. Generates lead-scoring-model.md with scoring dimensions, point values, thresholds, CRM implementation guide, and validation methodology. Can also score a batch of current leads against the model.
Build marketing that people actually want using Seth Godin's Permission Marketing methodology—earn attention instead of demanding it, turning strangers into friends and friends into customers. Use when: **Build an email list** that's engaged and valuable; **Design lead magnets** that earn real permission; **Create content strategy** based on earning attention; **Evaluate marketing tactics** for permission vs. interruption; **Improve email marketing** by increasing anticipation and relevance
Planhat platform help — Health Scores, Agentic Automation, Revenue Management, CRM Sync, Enduser Tracking, Projects, NPS, REST API, MCP Server. Use when health scores aren't reflecting churn risk, CRM sync is overwriting fields or not pulling data, metrics take hours to build and formulas keep breaking, automation rules aren't triggering, revenue or license data doesn't match Salesforce, enduser tracking isn't capturing product usage, or the Planhat API returns unexpected errors. Do NOT use for general customer success strategy (use /sales-customer-success) or NPS/CSAT survey methodology (use /sales-customer-feedback).
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with meta-judge evaluation specifications and multi-agent evaluation
Structured feature brainstorming with diverge/converge methodology. Use when ideating on new features, exploring solutions, or generating creative approaches.
Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill, benchmark skill, eval my skill, run evals on. Outputs: an improved SKILL.md, a results log, and a changelog of every mutation tried.