Loading...
Loading...
Found 1,954 Skills
Fundamental design principles based on Don Norman's "The Design of Everyday Things". Use when you need to: (1) design affordances and signifiers into interfaces, (2) analyze why products are confusing, (3) apply constraints to prevent errors, (4) design clear feedback mechanisms, (5) bridge gulfs of execution and evaluation, (6) create intuitive conceptual models, (7) apply human-centered design, (8) understand why users make errors and design fault-tolerant systems.
Strategic clinical trial design feasibility assessment using ToolUniverse. Evaluates patient population sizing, biomarker prevalence, endpoint selection, comparator analysis, safety monitoring, and regulatory pathways. Creates comprehensive feasibility reports with evidence grading, enrollment projections, and trial design recommendations. Use when planning Phase 1/2 trials, assessing trial feasibility, or designing biomarker-driven studies.
Recognize breakthrough moments, blocking resolutions, and design decisions worth preserving. Detect high-value insights that save future time. Suggest distillation at valuable moments, not routine work.
Guide to effective Claude Code skill authoring using TDD methodology and persuasion principles. Use when creating new skills, improving compliance, or validating quality before deployment. Do not use for evaluating existing skills (use skills-eval) or analyzing architecture (use modular-skills). Follow the Iron Law: write a failing test before writing any skill.
Write ML experiment code with iterative improvement. Generate training/evaluation pipelines, debug errors, and optimize results through code reflection. Use when implementing experiments for a research paper.
Extract valuable legal question-answer pairs from lawyer-client communication records and generate structured knowledge base content. This skill should be used when users need to organize client consultation records, extract reusable legal knowledge from conversations, create Q&A knowledge bases, or prepare content marketing materials. Strict client information desensitization is supported.
Generates business/company names across 10 categories (Descriptive, Metaphoric, Invented, Founder-based, Acronym, Compound, Foreign, Playful, Geographic, Legacy) with USPTO trademark screening, domain availability checking, and 0-100 scoring. Use when users need company/product/brand naming for new business launches, rebranding, trademark strategy, IP protection naming, evaluating current name strength, or any naming/branding tasks requiring systematic analysis with legal clearance.
Scan and analyze a software repository or project for design quality using principles from A Philosophy of Software Design by John Ousterhout. Use when user asks to review, audit, scan, or evaluate code quality, design quality, architecture, or technical debt. Also trigger for: code review, design review, complexity analysis, code health check, module depth analysis, information hiding review, how good is my code, review my project, find design problems, what is wrong with my codebase, rate my code, or anything about evaluating software design quality at a structural level. This is not a linter or style checker. It evaluates deep design qualities like module depth, abstraction quality, information hiding, and complexity patterns.
Deep test, analyze, and audit Claude skills. Use this skill whenever the user wants to test a skill's behavior, analyze how it uses the Claude API, inspect inputs/outputs from scripts, or run security and code review audits against skill scripts. Trigger on: "test my skill", "analyze this skill", "audit skill scripts", "review skill for security issues", "what does this skill actually do when it runs", "inspect API calls from skill", "run a skill through its paces", "check my skill for bugs or vulnerabilities". Also trigger when the user shows you a SKILL.md and asks you to evaluate, critique, or stress-test it.
Bitcoin bottom-timing judgment model. By tracking 6 core indicators (RSI technical oversold, volume dry-up, MVRV ratio, social media fear index, miner shutdown price, long-term holder behavior), it comprehensively evaluates whether Bitcoin has entered a bottom-fishing zone and outputs a bottom-fishing rating and position-building recommendations. When users mention topics such as Bitcoin bottom-fishing, whether BTC has bottomed out, Bitcoin oversold, MVRV, miner shutdown price, long-term holder LTH, Bitcoin fear index, whether to buy Bitcoin, BTC position entry timing, crypto market bottom signals, Bitcoin cycle bottom, etc., be sure to use this skill. Even if the user simply asks "Can I buy the dip on Bitcoin now?" or "Has BTC finished dropping?", this skill should be triggered to provide a structured analysis framework.
Decision-first data analysis with statistical rigor gates. Use when analyzing CSV, JSON, database exports, API responses, logs, or any structured data to support a business decision. Handles: trend analysis, cohort comparison, A/B test evaluation, distribution profiling, anomaly detection. Do NOT use for codebase analysis (use codebase-analyzer), codebase exploration (use explore-pipeline), or ML model training.
Resolve PR review feedback by evaluating validity and fixing issues in parallel. Use when addressing PR review comments, resolving review threads, or fixing code review feedback.