Total 31,619 skills
Showing 12 of 31619 skills
Use when designing Rails models - ActiveRecord patterns, validations, callbacks, scopes, associations, concerns, query objects, form objects
Use when implementing well-scoped Python tasks with clear requirements, writing unit tests, and producing documented code for senior-developer review.
Specialized literature review skill with review discovery, deep targeted research (15-30 papers per section), recency surveys, and convergence tracking for comprehensive literature reviews
General RPI (Research, Plan, Implement, Iterate) execution skill. It is used for engineering tasks where users require "research first, then plan, then implement, and finally iterate", or when tasks are highly complex, high-risk, or have unclear impact. This skill does not rely on specific command-line tools or platforms, and is applicable to any AI Agent that supports skill mechanisms.
Use when creating, modifying, or refactoring Claude Code skills that require structured multi-agent review and quality validation
MCP Status
Use when creating brand names, product names, or company names in 2026. Use when naming needs to work across languages, voice assistants, and AI recommendation engines. Use when previous name candidates failed trademark or had conflicts.
Create a living specification (Spec) or plan for a feature by analyzing requirements and codebase
Rails-AI introduction - explains how rails-ai (Rails domain layer) integrates with superpowers (universal workflows) for Rails development
Use when creating, adding, or modifying plugins in this Glean Claude Plugins marketplace repository. Triggers on "create plugin", "add plugin", "new plugin", "plugin checklist", "marketplace", or when working with plugin.json, marketplace.json, or the plugins/ directory. Ensures all required files are updated correctly.
Ensure AI agents work in an isolated Git worktree to prevent changes to the main working directory. Use when AI is about to make its first code modification in a session, or when the user requests isolated/safe editing. Triggers include starting to edit files, implementing features, or fixing bugs.
Scan the codebase for potential secret leaks including API keys, tokens, passwords, hardcoded project IDs, and sensitive identifiers. Use when the user says "check for secrets", "scan for leaks", "security check", or before committing sensitive changes.