Loading...
Loading...
Found 2,123 Skills
Use when tasks involve reading and summarising an academic paper from either a PDF file or an arXiv URL. If the input is a PDF, convert it to images for accurate reading (equations/figures). If the input is an arXiv URL, download the LaTeX source to read. Output the summary as a standalone LaTeX file.
Validates skills against production-level criteria with 9-category scoring. This skill should be used when reviewing, auditing, or improving skills to ensure quality standards. Evaluates structure, content, user interaction, documentation, domain standards, technical robustness, maintainability, zero-shot implementation, and reusability. Returns actionable validation report with scores and improvement recommendations.
Amazon Bedrock Model Customization with fine-tuning, continued pre-training, reinforcement fine-tuning (NEW 2025 - 66% accuracy gains), and distillation. Create customization jobs, monitor training, deploy custom models, and evaluate performance. Use when customizing Claude, Titan, or other Bedrock models for domain-specific tasks, adapting to proprietary data, improving accuracy on specialized workflows, or distilling large models to smaller ones.
Guide architectural design decisions for software systems. Use this skill when designing new systems, evaluating architecture trade-offs, or creating technical design documents. Helps produce clear, well-structured design artifacts including component diagrams, data flow, and decision records.
Use this skill for project management: planning, progress tracking, task coordination, timeline/milestone management, risk assessment, resource allocation, and execution guidance. Examples: <example>User organizing complex development: "Starting feature with frontend, backend, infrastructure changes. Need project plan." → Creates plan with task breakdown, timeline, coordination strategy.</example> <example>User facing delays: "Project behind schedule, unsure how to prioritize tasks." → Analyzes situation, provides recovery plan with prioritized actions.</example>
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.
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.
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.