skill-generator
An intelligent generator for Claude Code Skills that automates the creation of structured prompts, YAML frontmatter, and supporting file architectures.
Discover reusable agent skills, browse implementation details, and find the right skill for your workflow.
349 skills found
An intelligent generator for Claude Code Skills that automates the creation of structured prompts, YAML frontmatter, and supporting file architectures.
Guidance and operational tips for identifying, reviewing, and managing pull requests created by the GitHub Copilot coding agent within your repository.
Generate production-ready Cloudscape Design System React + TypeScript UI code, components, and scaffolds with accessibility, responsive patterns, and robust state handling.
Generate daily and weekly planning reports from backlog and carryover state, applying WIP limits and priority rules from BaseContext.yaml with automatic git commit/push.
Comprehensive code quality validation for LibrAgent, covering TypeScript frontend and Rust/Tauri backend via automated linting, formatting, type checking, and build verification.
Guide for creating properly structured YAML configuration files for MassGen. Use this when creating new configs for examples, case studies, testing, or feature demonstrations.
Plan features through an interactive, multi-step process that generates comprehensive Product Requirements Documents (PRDs) with user stories, acceptance criteria, and technical specifications.
Enriches vague prompts by performing codebase research and asking targeted questions to clarify user intent before execution.
Audit Packmind documentation by cross-referencing MDX files against the codebase to detect broken links, outdated CLI references, and missing coverage.
Expert tool for auditing and validating the structural integrity, naming conventions, and best practices of Claude Code configurations, including skills, hooks, and commands.
Transform raw data into compelling, decision-driving narratives using visualization strategies, story frameworks, and persuasive structures for analytics and executive reporting.
Identify and document Customer Problems (CP) from business context. Use when starting requirements engineering or when stakeholders describe solutions instead of problems. Step 1 of Problem-Based SRS methodology.