Loading...
Loading...
Found 2,896 Skills
Transform projects into professional open-source repositories with standard components. Use when users ask to "make this open source", "add open source files", "setup OSS standards", "create contributing guide", "add license", or want to prepare a project for public release with README, CONTRIBUTING, LICENSE, and GitHub templates.
Evaluate skill quality against best practices. Use when asked to "rate this skill", "review skill quality", "check skill formatting", "is this skill good", "evaluate SKILL.md", "grade this skill", or when validating skill files before publishing.
Read Codex logs for this repo and synthesize docs in docs/.
Create a structured problem statement document for a feature, bugfix, or project. Use when starting a project, adding a feature, or fixing a bug and you need to clearly define the problem, context, desired outcome, and success criteria. Accepts input from Jira tickets (via MCP), document links, or text descriptions.
This is the OpenAPI specification for the [Figma REST API](https://www.figma.com/developers/api).. Use when working with the Figma API or when the user needs to interact with this API.
Track management methodology - creating and managing logical work units (features, bugs, refactors) through specification, planning, and implementation phases.
Coding assistance for [GemBox components](https://www.gemboxsoftware.com/). Use when users ask about any GemBox component or coding task that can be performed with a GemBox component. This includes GemBox.Spreadsheet (.NET read/write Excel files), GemBox.Document (.NET read/write Word files), GemBox.Pdf (.NET read/write PDF files), GemBox.Presentation (.NET read/write PowerPoint files), GemBox.Email (.NET read/write email files, send/receive emails), GemBox.Imaging (.NET read/write image files), and GemBox.PdfViewer (JavaScript display/print/save PDF files).
Summarize work done in a spec/plan document.
Plain text formatting that's readable raw AND rendered
Document creative decisions and protocol evolution in structured chronicle format.
Explore and analyze TUI applications to document their features for cloning. Use when asked to reverse-engineer, analyze, document, or understand a terminal UI like Claude Code, OpenCode, Codex, lazygit, or any ratatui/ncurses-based application. Launches the target TUI in tmux, systematically explores all views and keybindings, captures ASCII diagrams of each screen, and writes findings incrementally to a markdown file (survives context compaction).
This skill is used when users request phrases such as 'handle PR review issues', 'fix review items', 'resolve PR feedback', 'process review issues one by one', 'complete review tasks', 'run pr review resolver', 'resolve PR review', 'address review comments', 'fix review findings', or 'handle code review'. It reads the review comments of the PR associated with the current branch, discusses each unresolved issue with the user one by one, lets the user decide on the handling approach, and executes fixes in parallel as background subtasks.