Loading...
Loading...
Found 408 Skills
Claude Code skill that designs and builds high-converting questionnaire-style app onboarding flows modelled on proven conversion patterns from top subscription apps like Noom, Headspace, and Duolingo.
Extract experience from the current conversation and automatically generate reusable Claude Code Skills. Use when user wants to extract a skill, summarize into a skill, solidify experience, generate a skill, create a skill from context, save as a skill, or turn experience into a skill.
Comprehensive research toolkit for discovering patterns, best practices, and technical knowledge across Web search, MCP servers, GitHub repositories, and documentation. Use when researching technologies, exploring codebases, finding examples, or gathering requirements for skill development.
AI-powered web research assistant that leverages BrowserAct API to supplement restricted web access by searching the internet for additional information. Designed for OpenClaw and Claude Code.
Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.
Create Skills, write Skills, Skill templates. Help create and optimize Claude Code Skills in accordance with Testany's specifications.
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.
Core philosophy for designing Claude Code skills - when to use skills vs agents, the knowledge test, and what makes skills valuable. Use when deciding component type or evaluating skill quality.
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.
Use when creating, modifying, or refactoring Claude Code skills that require structured multi-agent review and quality validation
Guide for creating Claude Code skills to document @rytass packages (建立套件文件 skill 指南). Use when creating new package documentation skills, writing SKILL.md files, or designing skill structure.
We review Claude Code Skills based on official best practices and provide specific improvement suggestions. It is triggered by requests such as 'Review this skill', 'Check skill quality', 'Validate SKILL.md', 'I want to improve this skill'.