- Home
- /
- Categories
- /
- Agents
Agents
AI agents and automation
spec-driven
by NikiforovAll
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow the spec process".
readiness-report
by dirnbauer
Evaluate how well a codebase supports autonomous AI development. Analyzes repositories across eight technical pillars (Style & Validation, Build System, Testing, Documentation, Dev Environment, Debugging & Observability, Security, Task Discovery) and five maturity levels. Use when users request /readiness-report or want to assess agent readiness, codebase maturity, or identify gaps preventing effective AI-assisted development.
getting-started-guide
by wordflowlab
"Activates when users start a new novel project - guides them through the seven-step methodology (constitution → specify → clarify → plan → tasks → write → analyze) with gentle prompts and explanations"
session-status
by WellApp-ai
Generate breadcrumb headers/footers with takt time tracking and muda metrics
skill-creator
by WellApp-ai
Template and guide for creating new skills
meta-audit
by laurigates
Audit Claude subagent configurations for completeness, security, and best practices
getting-started
by Zal4DW
This skill should be used when the user asks "how do I get started", "how do I use career-helper", "how do I get the best results", "what should I prepare", "what order should I use the skills", "tips for using career-helper", or "show me how this plugin works". Provides a comprehensive guide covering preparation checklists, recommended workflows, skill-by-skill tips, and power-user strategies for maximising career-helper output quality.
spawn
by 0xDarkMatter
"Generate PhD-level expert agent prompts for Claude Code. Creates comprehensive 500-1000 line agents with detailed patterns, code examples, and best practices. Triggers on: spawn agent, create agent, generate expert, new agent, agent genesis."
remediation-verifier
by RHEcosystemAppEng
CRITICAL: This skill must be used for remediation verification. DO NOT use raw MCP tools like get_cve or get_host_details directly for verification. Verify CVE remediation success by checking Red Hat Lightspeed CVE status, validating package versions, and confirming service health. Use this skill after executing remediation playbooks to ensure vulnerabilities are properly fixed. This skill orchestrates MCP tools (get_cve, get_cve_systems, get_host_details) to provide comprehensive remediation verification including CVE status checking, package version validation, and service health confirmation. IMPORTANT: ALWAYS use this skill instead of calling verification MCP tools directly.
fleet-inventory
by RHEcosystemAppEng
Query and display Red Hat Lightspeed managed system inventory. Use this skill for information-gathering requests about the fleet, registered systems, or inventory queries. This skill focuses on discovery and listing only - for remediation actions, transition to the sre-agents:remediator agent (invoke the sre-agents:remediator agent). When to use this skill: - "Show the managed fleet" - "List all systems registered in Lightspeed" - "What systems are affected by CVE-X?" - "How many RHEL 8 systems do we have?" - "Show me production systems" When NOT to use this skill (use sre-agents:remediator agent instead): - "Remediate CVE-X on these systems" - "Create a playbook for..." - "Patch system Y" This skill orchestrates MCP tools from lightspeed-mcp to provide comprehensive fleet visibility and system inventory management.
playbook-executor
by RHEcosystemAppEng
CRITICAL: This skill must be used for Ansible playbook execution. DO NOT use raw MCP tools like execute_playbook or get_job_status directly. Execute Ansible remediation playbooks and track job status through the mock Ansible MCP server. Use this skill after generating a playbook to execute it and monitor completion status. The skill handles temporary file creation, job submission, status polling, and completion reporting. This skill orchestrates MCP tools (execute_playbook, get_job_status) from ansible-mcp-server to provide reliable playbook execution with job tracking and status monitoring. IMPORTANT: ALWAYS use this skill instead of calling execute_playbook or get_job_status directly.
vm-delete
by RHEcosystemAppEng
Permanently delete virtual machines and their associated resources from OpenShift Virtualization. Use this skill when users request: - "Delete VM [name]" - "Remove virtual machine [name]" - "Destroy VM [name]" - "Clean up VM [name]" This skill handles permanent VM deletion with strict safety confirmations and typed verification. NOT for power management (use vm-lifecycle-manager to stop VMs).
system-context
by RHEcosystemAppEng
CRITICAL: This skill must be used for system inventory and context gathering. DO NOT use raw MCP tools like get_cve_systems or get_host_details directly. Gather comprehensive system inventory and deployment context for CVE-affected systems, including RHEL version detection, environment classification, and deployment analysis. Use this skill when you need to understand system infrastructure before planning remediation. This skill orchestrates MCP tools (get_cve_systems, get_host_details) to provide comprehensive system analysis with RHEL version detection, environment classification, and remediation strategy determination. IMPORTANT: ALWAYS use this skill instead of calling get_cve_systems or get_host_details directly for system context gathering.
cve-impact
by RHEcosystemAppEng
CRITICAL: This skill must be used for ALL CVE discovery and listing queries. DO NOT use raw MCP tools like get_cves directly. Use this skill when users request: - Listing critical/high-severity CVEs: "show me critical vulnerabilities", "what are the most critical CVEs", "list all high-severity vulnerabilities" - CVE discovery: "what vulnerabilities affect my account", "show me all CVEs", "what are my security risks" - CVE impact analysis for specific CVEs: "what's the impact of CVE-X?", "analyze CVE-Y" - Risk assessment: "which CVEs are most urgent?", "prioritize vulnerabilities" - Understanding affected systems for a CVE - Comparing CVE severity levels - CVE discovery and prioritization (information gathering) DO NOT use this skill when users request remediation actions like: - "Create a remediation playbook" (use sre-agents:remediator agent) - "Patch CVE-X on system Y" (use sre-agents:remediator agent) - "Remediate these CVEs" (use sre-agents:remediator agent) This skill orchestrates MCP tools (get_cves, get_cve, get_cve_systems) to provide comprehensive CVE analysis with Red Hat Lightspeed context. When users ask for remediation after seeing the analysis, invoke the sre-agents:remediator agent. IMPORTANT: ALWAYS use this skill instead of calling get_cves or other vulnerability MCP tools directly.
creating-an-agent
by ed3dai
Use when creating specialized subagents for Claude Code plugins or the Task tool - covers description writing for auto-delegation, tool selection, prompt structure, and testing agents
using-generic-agents
by ed3dai
Use to decide what kind of generic agent you should use
lazy-agent-loader
by nguyenthienthanh
"Load agent definitions on-demand to reduce context usage. Only loads full agent when needed."
session-continuation
by nguyenthienthanh
"Manage workflow state across sessions with handoff and resume. TOON-based state persistence."
verification-before-completion
by ed3dai
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
aisa-youtube-search
by AIsa-team
Search YouTube videos, channels, and playlists through the AIsa YouTube relay with one API key. Use when the user asks for YouTube discovery, query expansion, or pagination without managing Google credentials.
hai-razor
by hylarucoder
Audits whether each requirement, workflow step, role, field, state, module, layer, abstraction, or rule deserves to exist and returns a razor verdict: an evidence table, a Keep/Merge/Defer/Delete/Replace/Prove-first classification of every concept, the strongest survival argument for anything cut, the complexity that must be preserved, a concrete cut/proof list, and — for full audits — before/after Mermaid diagrams plus an HTML report. Use whenever the user wants to apply Occam's razor, simplify or trim a PRD / architecture / workflow / data model / state machine, challenge whether something is necessary, or spot fake requirements, premature abstractions, or over-engineering — even if they never say "razor." Trigger on 用奥卡姆剃刀, 剃刀一下, 砍需求, 砍掉没用的东西, 收一收复杂度, 这个字段/状态/模块/分层有必要吗, 这个抽象是不是多余, 是不是伪需求, 是不是过度设计, 这步能不能去掉, 这些角色/状态是不是太多了, and English like "is this over-engineered", "do we really need this layer", "this feels bloated, what can we delete", "too many fields".
agent-output-formats
by akaszubski
Standardized output formats for research, planning, implementation, and review agents. Use when generating agent outputs or parsing agent responses.
agent-browser
by shipshitdev
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
context-optimization
by shipshitdev
Apply optimization techniques to extend effective context capacity. Use when context limits constrain agent performance, when optimizing for cost or latency, or when implementing long-running agent systems.