Claude Skills by radesjardins

This skill should be used when debugging Chrome extension issues, diagnosing Chrome Web Store rejections, or troubleshooting build problems. Trigger when: "extension not working", "CWS rejection", "Chrome Web Store rejected", "Yellow Magnesium", "Purple Potassium", "Blue Argon", "Red Magnesium", "extension build error", "manifest error", "extension debugging", "service worker not waking", "content script not injecting", "message not received", "extension permissions error", "pre-release check...

This skill should be used when building React UI for Chrome extensions or when the user asks about UI patterns in extensions. Trigger when: "React in extension", "extension popup React", "side panel React", "Shadow DOM React", "content script UI", "createShadowRootUi", "extension accessibility", "rem to px extension", "portal in extension", "React popup state", "extension UI patterns", "Radix in extension", "Shadcn extension", "extension keyboard navigation", "ARIA in extension", "focus manag...

Review my code, code review, is this ready to ship, check for bugs, security audit, review this PR, pre-merge check, is this safe to deploy, check code quality. Blame-aware diff scoping, 3-role adversarial review, AI slop detection (14 patterns), framework IDOR, WCAG 2.2, performance heuristics, severity-ranked findings, optional fix application. v3.0: Opus 4.7 optimized with parallel tool calls, JSON-first subagent output, compaction-safe checkpointing, non-interactive mode for agents/CI.

This skill should be used when the user says "decompile this prompt", "reverse engineer this prompt", "analyze this prompt", "break down this prompt", "what does this prompt do", "adapt this prompt for", "simplify this prompt", "split this prompt", "migrate this prompt", "why does this prompt work", "explain this system prompt", "what techniques is this using", "convert this prompt from X to Y", "what framework is this prompt using", "optimize this prompt", "look at this prompt", or pastes an...

This skill should be used when the user says "write a prompt", "prompt engineering", "system prompt", "optimize my prompt", "create instructions for", "context engineering", "CLAUDE.md", "few-shot examples", "write me a Midjourney prompt", "create a GPT prompt", "prompt for Claude Code", "agentic prompt", "tool description", or needs to create, improve, or optimize prompts for any AI platform. Covers prompt writing, system prompts, tool descriptions, agentic workflows, prompt chaining, and cr...

This skill should be used when performing operational actions against a Coolify instance using MCP tools — deploying applications, checking deployment status, viewing logs, diagnosing errors, managing environment variables, restarting services, checking server health, or performing any hands-on Coolify management task. Trigger when: "deploy my app", "check Coolify status", "show me Coolify logs", "what's running on Coolify", "restart my app on Coolify", "check server health", "why is my deplo...

This skill should be used when setting up CI/CD pipelines for Coolify, using the Coolify REST API, triggering deployments from GitHub Actions, configuring webhooks, deploying from GHCR or other registries, setting up PR preview environments, configuring branch-specific deployments, using the Coolify deploy webhook, integrating GitLab CI with Coolify, or managing API tokens. Trigger when: "Coolify CI/CD", "Coolify API", "deploy to Coolify from GitHub Actions", "Coolify webhook", "Coolify deplo...

This skill should be used when provisioning databases in Coolify, configuring database backups, restoring database backups, setting up S3-compatible backup storage, managing database SSL/TLS, connecting external clients to Coolify databases, rotating database credentials, running migrations against Coolify databases, tuning database resource limits, or choosing between standalone databases and service databases. Trigger when: "Coolify database", "create database in Coolify", "Coolify PostgreS...

Deploy to Coolify, which build pack, Nixpacks vs Dockerfile, Coolify rollback, zero-downtime deploy, deploy from registry, Coolify monorepo, Coolify environment variables, pre/post deployment script, Railpack, Coolify static site.

This skill should be used when configuring multi-server deployments in Coolify, setting up Docker Swarm with Coolify, configuring build servers, managing Coolify instance backups, migrating Coolify to a new server, setting up load balancing across Coolify servers, or managing Coolify infrastructure at scale. Trigger when: "Coolify multi-server", "Coolify multiple servers", "Coolify Swarm", "Docker Swarm Coolify", "Coolify build server", "Coolify backup", "backup Coolify", "migrate Coolify", "...

This skill should be used when configuring monitoring for Coolify, setting up Coolify Sentinel, configuring notification channels (Slack, Discord, email, Telegram, webhook), setting up log drains (Axiom, Loki, New Relic, FluentBit), integrating Uptime Kuma, monitoring container resources, configuring alerts for CPU or memory, or building observability stacks for Coolify-managed applications. Trigger when: "Coolify monitoring", "Coolify Sentinel", "Coolify notifications", "Coolify Slack notifi...

This skill should be used when securing Coolify deployments, managing secrets and environment variables, configuring Docker Build Secrets, setting up RBAC team roles, isolating containers on the network, configuring resource limits (CPU/memory), hardening firewall rules (UFW), managing terminal access, or auditing Coolify security. Trigger when: "Coolify security", "Coolify secrets", "Coolify environment variables security", "Docker Build Secrets Coolify", "Coolify RBAC", "Coolify team roles"...

This skill should be used when diagnosing Coolify deployment failures, HTTP errors (502, 504), Traefik routing issues, container restart loops, OOM kills, build failures, SSL certificate problems, Nixpacks build errors, health check failures, or Coolify self-repair. Trigger when: "Coolify 502", "Coolify 504", "Coolify bad gateway", "Traefik error Coolify", "container restart loop", "Coolify OOM", "Coolify build failed", "Nixpacks error", "SSL certificate Coolify", "Let's Encrypt Coolify", "Co...

This skill should be used when the user says "draft a pitch", "write a pitch for [project]", "one-pager", "executive summary", "investor pitch", "grant proposal", "pitch deck content", "partnership memo", "draft a funding pitch", "write a long-form pitch", or wants a longer-form pitch document (one-pager, executive summary, or deck-equivalent text) for a project. Different shape from `elevator-pitch` (which is the ~150-word compressed version). `draft-pitch` is for funding applications, grant...

This skill should be used when the user says "write me an elevator pitch", "give me an elevator pitch", "30-second pitch", "one-paragraph pitch", "quick pitch for [project]", "pitch this in 30 seconds", "short pitch", "compress this to an elevator pitch", or wants a roughly 150-word / 30-seconds-spoken pitch for a project. Output is grounded in repo source via check-grounding.py and avoids overpromising via check-overpromise.py. Different shape from `draft-pitch` (long-form one-pager / execut...

This skill should be used when the user says "explain this document", "interpret this file", "what does this plan commit me to", "what does this ADR say", "interpret this architecture doc", "what does this AI-generated plan actually mean", "decompile this doc", "what's this file saying", "explain this to me in plain English", "what are the implications of this doc", "where could this plan go wrong", or wants a specific repo file (a plan, an ADR, an architecture spec, an AI-generated proposal,...

This skill should be used when the user says "audit my README", "ground my README against the code", "check if my README overpromises", "review my README honestly", "rewrite my README without marketing language", "audit my marketplace listing", "check my plugin description", "ground this description against the code", "is my README honest", "does my README match the code", or wants to (a) audit an existing README/marketplace listing against actual code to find overpromise + unbacked claims, o...

This skill should be used when the user says "narrate this project", "explain this project in plain English", "describe what this repo does", "summarize this project for a non-developer", "write a project narrative", "tell me what this project is", "explain this codebase to a collaborator", "draft an onboarding brief", "explain this project to my parents", "non-dev summary", or wants a plain-language description of a project synthesized from its source artifacts (code, docs, planning files, R...

This skill should be used when the user says \"manage my calendar\", \"list my calendars\", \"update calendar settings\", \"share a calendar\", \"delete a calendar\", \"check free/busy time\", or wants to broadly manage Google Calendar. Covers calendars, events, ACL rules, free/busy queries, and settings.

This skill should be used when the user says \"append text to a doc\", \"add content to a Google Doc\", \"write to a document\", \"insert text at the end of a doc\", \"add a note to my doc\", or wants to append plain text to an existing Google Doc. Covers inserting text at the end of a document body.

This skill should be used when the user says \"read a Google Doc\", \"create a document\", \"get the contents of a doc\", \"update a document\", \"make a new Google Doc\", \"batch update a doc\", or wants to broadly work with Google Docs. Covers creating, reading, and batch-updating document content.

This skill should be used when the user says \"manage my Drive files\", \"search Google Drive\", \"list files in a folder\", \"share a file\", \"create a shared drive\", \"download a file from Drive\", or wants to broadly manage Google Drive. Covers files, folders, permissions, comments, shared drives, and revisions.

This skill should be used when the user says \"read this email\", \"show me the body of a message\", \"get the contents of an email\", \"what does this message say\", \"show headers for this email\", or wants to read a specific Gmail message by ID. Covers plain text body, HTML body, and message headers.

This skill should be used when the user says \"reply to this email\", \"send a reply\", \"respond to that message\", \"write back to sender\", \"reply to the sender only\", or wants to send a threaded reply to a single Gmail message. Covers in-reply-to threading, attachments, CC/BCC, and HTML replies.

This skill should be used when the user says \"send an email\", \"email someone\", \"compose a message\", \"write an email to\", \"send a Gmail\", \"draft and send\", or wants to send a new outbound email through Gmail. Covers recipients, subject, body, CC/BCC, attachments, HTML content, and send-as aliases.

This skill should be used when the user says \"show my unread emails\", \"what's in my inbox\", \"summarize my email\", \"check my inbox\", \"what emails do I have\", \"triage my inbox\", or wants a quick summary of unread Gmail messages. Covers sender, subject, date, labels, and custom search queries.

This skill should be used when the user says \"manage my Gmail\", \"work with email\", \"set up email filters\", \"manage labels\", \"check my Gmail profile\", \"manage email settings\", or wants to broadly manage Gmail. Covers messages, threads, labels, drafts, filters, and push notification settings.

This skill should be used when the CLI needs to authenticate with Google Workspace, apply global flags like --format or --dry-run, or follow security rules before any gws command. Not a user-facing service — this is the shared reference for gws CLI auth patterns, output formatting, shell escaping tips, and write-command safety rules used by all other gws-* skills.

This skill should be used when the user says \"add a row to a sheet\", \"append data to a spreadsheet\", \"log data to Sheets\", \"insert a new row\", \"write values to the bottom of a sheet\", or wants to append one or more rows to a Google Sheets spreadsheet. Covers single-row and multi-row bulk inserts.

This skill should be used when the user says \"read data from a sheet\", \"get values from a spreadsheet\", \"show me what's in this sheet\", \"pull data from a range\", \"read a cell range\", or wants to read values from a specific range in a Google Sheets spreadsheet. Covers named ranges and A1 notation cell ranges.

This skill should be used when the user says \"work with a spreadsheet\", \"create a Google Sheet\", \"update a spreadsheet\", \"batch update cells\", \"manage sheet data\", \"get spreadsheet metadata\", or wants to broadly manage Google Sheets. Covers creating spreadsheets, reading and writing values, and batch updates.

This skill should be used when the user says \"create a presentation\", \"read a Google Slides deck\", \"update a slide\", \"get a presentation\", \"add slides to a deck\", \"batch update a presentation\", or wants to work with Google Slides. Covers creating, reading, and batch-updating presentations and individual pages/slides.

This skill should be used when the user says "help me write this", "assemble my notes", "I have notes and need to create something", "intermediate packets", "archipelago of ideas", "I'm facing a blank page", "dial down the scope", "I'm overwhelmed by this project", "ship something smaller", "connect these ideas", "draft from my notes", "turn my research into output", or wants to assemble captured knowledge into creative output like articles, presentations, reports, or deliverables.

This skill should be used when the user says "hemingway bridge", "wrap up session", "save my progress", "where did I leave off", "session handoff", "end of session", "capture what I was working on", "pick up where I left off", "PARA handoff", "what should I do next session", or wants to capture session state in a PARA-aware format before stopping work. Integrates with rad-session's wrapup/startup cycle.

This skill should be used when the user says "organize my notes", "PARA method", "second brain", "set up PARA", "I'm overwhelmed with files", "productivity system", "knowledge management", "where does this go", "classify this note", "my system is broken", "digital organization", "clean slate", "project list", or wants to build, fix, or maintain a PARA-based knowledge management system. Covers PARA setup, classification, system diagnosis, and review workflows.

This skill should be used when the user says "summarize this note", "progressive summarization", "distill this", "bold the key points", "highlight the important parts", "executive summary", "layer 2", "layer 3", "layer 4", "make this scannable", "TL;DR this article", "distill my notes", or pastes a raw note, article, transcript, or long text and wants it condensed into layered, scannable summaries. Applies Tiago Forte's Progressive Summarization technique.

This skill should be used when the user says "12 favorite problems", "twelve favorite problems", "Feynman problems", "capture filter", "what should I save", "I save too much", "I don't know what to capture", "my captures are unfocused", "favorite problems workshop", "identify my problems", "what are my big questions", or wants to create, review, or use a list of guiding questions as a personal capture filter for their Second Brain.

This skill should be used when the user says "checkpoint", "save progress", "document and clear", "dump context", "save state", "prepare to clear", "session handoff", "wrap up this session", "context is getting long", "I need to clear", "save my work", "handoff", "I need to switch tasks", "before I close", or when the conversation is approaching context limits and work needs to be preserved before clearing the session. Also trigger proactively when detecting signs of context degradation (repe...

This skill should be used when the user says "what stack should I use", "evaluate my tech stack", "recommend a stack", "what framework for", "compare frameworks", "is this the right stack", "stack recommendation", "best framework for", "technology selection", "what database should I use", "Next.js vs Astro", "Supabase vs Firebase", "which ORM", "hosting recommendation", "deployment platform", or wants help choosing technologies for a new or existing project. Provides AI-native stack recommend...

This skill should be used when the user says "plan my project", "create an implementation plan", "help me architect this", "I need a plan before coding", "let's plan before we build", "improve my plan", "deepen the current milestone", "continue the plan", "continue planning", "let's continue planning", "continue the planning session", "pick up the plan", "where did we leave off in the plan", "where did we leave off planning", "continue from where we left off" (when planning context is implied...

This skill should be used when the user says "write me a project story", "summarize the project", "draft a state-of-the-project narrative", "explain where this project is", "what's the state of this project", "draft an onboarding brief", "give me a project update", "create a project story", "tell me the project story", "write a plain-English project summary", "narrate the project", or wants a plain-language narrative summary of a project synthesized from the canonical doc set (vision.md, deci...

This skill should be used when the user says "refresh the project story", "update the project story", "the story is stale", "regenerate the project narrative", "refresh project-story.md", "update PROJECT-STORY.md", "sync the story with the docs", "the story drifted", or wants an existing project-story file regenerated in place against the current canonical doc set. Detects which sections of the existing story have drifted from canonical source (vision.md, decisions/, planning/current.md, stat...

This skill should be used when the user says "review my plan", "audit this plan", "check my implementation plan", "is this plan complete", "what's missing from my plan", "validate my plan", "plan review", "check plan quality", "risk review", "check dependencies", "are there any risks in my plan", or has an existing implementation plan (PLAN.md, plan.md, implementation_plan.md, tasks.md) that needs quality assessment before execution begins.

This skill should be used when the user says "plan status", "where am I in the plan", "what's next", "what tasks are left", "show plan progress", "which tasks are blocked", "next eligible task", "plan progress", "how far along", "what can I work on next", or wants a quick read on an in-flight implementation plan without re-running the full review skill.

AEO, AI visibility, AI search optimization, generative engine optimization, LLM seeding, AI citations, answer engine optimization, brand presence in ChatGPT/Perplexity/Google AI Overviews. This skill optimizes the user's OWN content structure and distribution for AI-extractability. It does NOT measure actual AI citation rates — that requires direct AI-platform API integration (Path B).

Broken links, 404 errors, dead links, redirect chains, link checker, fix links. Scans the user's codebase for broken internal/external links, redirect chains, mixed-content issues, and unlinked brand mention opportunities. Real code work — no Path B dependencies.

Competitor analysis, competitor SEO, who ranks for, competitive audit, compare my SEO, competitor gap. Covers content gaps, technical SEO comparison (observable signals), SERP feature ownership, AI citation pattern observation, and qualitative link opportunity mapping. Does NOT report numerical backlink counts, domain authority, organic traffic, or actual AI citation rates — those require a backlink / traffic / AI-platform MCP (Path B).

Content strategy, content gaps, editorial calendar, topical authority, content plan, what should I write about. Covers topical authority mapping, gap analysis, brief generation, and 12-week editorial calendar. Most of this skill is strategic reasoning over observable content + WebSearch — no Path B dependencies except for Phase 3 traffic scoring (requires GSC/GA data, which the user can paste in or skip).

Fix my SEO, fix this SEO issue, fix missing meta, fix broken links, fix page speed code-level risk, fix schema — user has a specific SEO problem to remediate. Routes to specialized skills and applies fixes. For diagnosis without fixing, use full-seo-audit instead. Fixes that require numerical measurement (e.g., "fix my LCP to 2.5s") need a Path B MCP to verify — surfaced in the route.

Audit my SEO, run an SEO audit, SEO score, SEO health check, full SEO analysis — comprehensive multi-category request. Performs a scoped 6-phase audit over the user's codebase plus a user-provided URL list (typically 5-10 URLs). Covers technical SEO, on-page SEO, content/E-E-A-T, schema, internal linking, and AI-extractability. Does NOT crawl the entire live site, does NOT measure Core Web Vitals numerically, does NOT infer backlinks — those require Path B MCP integrations. For single-area re...