RadOrigin-LLC
OrganizationMarketplace of plugins and skills for Claude Code
Categories
Indexed Skills (75)
draft-pitch
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 proposals, partnership memos, and pitch-deck text. Output is grounded in repo source via check-grounding.py; no overpromising via check-overpromise.py.
elevator-pitch
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 / executive summary / deck-equivalent) — `elevator-pitch` is the tight oral / cold-intro version.
explain-document
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, a contract-shaped doc, a config file) interpreted in plain English with attention to what it commits to, what it assumes, and where it could go wrong.
ground-readme
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, or (b) generate a README/listing from code with grounding controls so it doesn't overpromise. Two modes: `audit` (check existing) and `generate` (create new).
narrate-project
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, README, package.json). Works on any repo. Adapts to the named audience. Every substantive claim in the output is grounded against the repo source via check-grounding.py; no overpromising via check-overpromise.py. The output is prose for a human reader, not a planning artifact.
gws-admin-reports
This skill should be used when the user says "show audit logs", "pull admin reports", "list user activity", "check login history", "get usage stats for my org", "show drive activity logs", or wants to access Google Workspace Admin SDK reports. Covers activity logs, customer usage reports, entity usage, and user usage reports.
gws-calendar
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.
gws-chat
This skill should be used when the user says "manage Chat spaces", "list my Chat rooms", "create a Chat space", "delete a Chat space", "set up a group chat", "find a direct message", or wants to broadly manage Google Chat. Covers spaces, memberships, messages, custom emojis, and media uploads.
gws-classroom
This skill should be used when the user says "manage my classroom", "create a course", "list my classes", "add a student to a course", "assign coursework", "invite a teacher", or wants to manage Google Classroom. Covers courses, enrollments, coursework, announcements, topics, and guardian invitations.
gws-drive
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.
gws-events
This skill should be used when the user says "subscribe to Workspace events", "set up event notifications", "watch for Workspace changes", "manage event subscriptions", "list active subscriptions", or wants to broadly manage Google Workspace Events subscriptions. Covers creating, listing, updating, and reactivating subscriptions.
gws-gmail-forward
This skill should be used when the user says "forward this email", "forward to someone", "pass this email along", "send this message to", "forward with a note", or wants to forward a specific Gmail message to new recipients. Covers adding a note, CC/BCC, attachments, and HTML content.
gws-gmail-reply-all
This skill should be used when the user says "reply all to this email", "respond to everyone", "reply to the whole thread", "send to all recipients", "reply all with note", or wants to reply to a Gmail message including all original To/CC recipients. Covers recipient exclusions, extra CC/BCC, attachments, and HTML content.
gws-gmail-reply
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.
gws-gmail-send
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.
gws-people
This skill should be used when the user says "manage my contacts", "look up a contact", "add a new contact", "search my address book", "list contact groups", "update someone's contact info", or wants to manage Google People/Contacts. Covers personal contacts, contact groups, directory search, and profile photos.
gws-shared
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.
gws-sheets
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.
a11y-review
Static analysis pass over JSX/HTML/CSS source for WCAG 2.2 AA failure patterns. Does NOT run axe-core, does NOT measure real contrast, does NOT test runtime behavior — pair with a11y-testing for that. Use when the user asks for an accessibility review, a11y check, WCAG review, "is this accessible?", "does my site meet WCAG?", "check my component for accessibility", "review accessibility of", "check for a11y issues", "fix accessibility issues", or any request to scan a web page, component, or codebase for WCAG 2.2 AA failure patterns. Findings are tagged by detection confidence; the report does not produce a Pass/Fail verdict because static analysis cannot defensibly produce one.
rad-code-review
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. The specialist lanes and memory that the built-in /code-review doesn't have: it invokes the built-in engine for general bug-finding, then adds a mechanical hallucinated-imports validator (with a vendored slopsquat denylist; Python/JS/TS/Rust/Go), an AI-slop lane, framework IDOR heuristics, a Supabase/Firebase BaaS-RLS security lane, an optional codex-security specialist scan on deep/--security-deep, and a deterministic findings index that tracks CR-NNN IDs across runs (new / recurring / resolved). Fixes apply to the working tree only — never commits.
convene
Convene a council, ask the council, debate this, get a panel to critique, run this by a council of experts, council of advisors, devil's advocate panel, red-team this decision, what would a panel say, multi-perspective critique, stress-test this decision, get diverse expert opinions and a recommendation. Convenes 3–5 cognitive-framework advisors that debate any decision — repo plans, website/UX designs, product or codebase critiques, marketing plans, strategy choices — then vote and return one ranked, confidence-rated recommendation with dissent preserved and a single concrete next step. Use when a decision genuinely merits several opposed expert lenses; not for quick single-answer questions or line-by-line code review (use rad-code-review for that).
gws-calendar-agenda
This skill should be used when the user says "what's on my calendar", "show my schedule", "what do I have today", "show this week's events", "what's coming up", "show my agenda", or wants to view upcoming events across calendars. Covers listing today, tomorrow, this week, or N days ahead, with optional calendar filtering.
gws-calendar-insert
This skill should be used when the user says "create a calendar event", "schedule a meeting", "add an event to my calendar", "book a time slot", "set up a meeting with", "add a Google Meet to an event", or wants to create a new Google Calendar event. Covers title, start/end time, attendees, location, description, and Meet link.
gws-chat-send
This skill should be used when the user says "send a Chat message", "post to a Chat space", "message the team on Chat", "send a Google Chat notification", "post in the Chat room", or wants to send a plain-text message to a specific Google Chat space. Covers sending to a named space by ID.
gws-docs-write
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.
gws-docs
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.
gws-drive-upload
This skill should be used when the user says "upload a file to Drive", "put this file in Google Drive", "save a file to Drive", "upload to a folder", "push a file to Drive", or wants to upload a local file to Google Drive. Covers automatic MIME detection, parent folder targeting, and custom filenames.
gws-events-renew
This skill should be used when the user says "renew my Workspace subscription", "reactivate an event subscription", "my subscription expired", "keep subscriptions alive", "refresh expiring subscriptions", or wants to renew or reactivate Google Workspace Events subscriptions. Covers renewing by name or batch-renewing all subscriptions expiring within a time window.
gws-events-subscribe
This skill should be used when the user says "stream Workspace events", "listen for Chat messages", "subscribe to Drive changes", "watch events from a Workspace resource", "stream events as NDJSON", or wants to create a new Workspace Events subscription and stream events in real time. Covers Pub/Sub setup, filtering by event type, and writing events to a directory.
gws-forms
This skill should be used when the user says "create a Google Form", "read form responses", "update a form", "get form submissions", "set up a survey", "publish a form", or wants to work with Google Forms. Covers creating, reading, updating forms and retrieving responses.
gws-gmail-read
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.
gws-gmail-triage
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.
gws-gmail-watch
This skill should be used when the user says "watch for new emails", "stream incoming Gmail", "monitor my inbox for new messages", "set up a Gmail listener", "pipe incoming emails to a script", or wants to watch a Gmail mailbox and stream new messages in real time. Covers Pub/Sub integration, label filtering, and writing messages to a directory.
gws-gmail
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.
gws-keep
This skill should be used when the user says "create a Keep note", "add a note", "list my notes", "delete a note", "read a Google Keep note", "show my Keep notes", or wants to manage Google Keep. Covers creating, reading, listing, and deleting notes and their attachments.
gws-meet
This skill should be used when the user says "create a Meet space", "manage a meeting room", "end a Meet conference", "list past meetings", "get meeting recordings", "get meeting transcripts", or wants to manage Google Meet. Covers meeting spaces, conference records, participants, recordings, and transcripts.
gws-modelarmor-create-template
This skill should be used when the user says "create a Model Armor template", "set up a safety template", "create a jailbreak filter", "add a new content filter", "configure a Model Armor policy", or wants to create a new Google Model Armor template. Covers preset templates (jailbreak) and custom JSON-defined template configuration.
gws-modelarmor-sanitize-prompt
This skill should be used when the user says "sanitize a user prompt", "screen input for harmful content", "filter a user message before sending to AI", "run prompt through Model Armor", "check this input for safety", or wants to sanitize inbound user input through a Model Armor template. Covers text and JSON request bodies, and stdin input.
gws-modelarmor-sanitize-response
This skill should be used when the user says "sanitize a model response", "filter AI output for safety", "screen model output before showing the user", "run this response through Model Armor", "check AI output for harmful content", or wants to sanitize outbound model responses through a Model Armor template. Covers text and JSON request bodies, and stdin piping.
gws-modelarmor
This skill should be used when the user says "filter content for safety", "set up Model Armor", "sanitize AI input", "screen prompts for harmful content", "manage safety templates", or wants to broadly work with Google Model Armor. Covers creating templates and sanitizing prompts and model responses.
gws-script-push
Google Apps Script: Upload local files to an Apps Script project.
gws-sheets-append
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.
gws-sheets-read
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.
gws-slides
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.
astro-accessibility
This skill should be used when implementing accessibility in Astro, WCAG compliance in Astro, Astro ARIA patterns, keyboard navigation in Astro components, screen reader support in Astro, Astro semantic HTML, focus management in Astro, accessible forms in Astro, Astro accessibility testing, axe-core integration with Astro, accessible Astro islands, alt text for Astro images, focus trapping in modals, accessible view transitions, or color contrast requirements.
astro-best-practices
This skill should be used when working on any Astro project or when the user asks about Astro best practices, conventions, or patterns. Trigger when: working on an Astro project, creating Astro components/pages/layouts, configuring astro.config, setting up Content Collections, using Content Layer API, choosing client directives (client:load/idle/visible/media/only), using server:defer or server islands, deciding between SSR and SSG, working with Astro Actions for forms, configuring middleware, using Zod schemas for content, building with TypeScript in Astro, creating API endpoints, using @astro/autoload, working with .astro files, Astro 5 or Astro 6 development.
astro-performance
This skill should be used when optimizing Astro performance, improving Core Web Vitals in Astro, fixing LCP/CLS/INP issues, auditing client directives, reducing JavaScript bundle size, configuring Astro prefetching, using server:defer for performance, optimizing Astro images, configuring Astro fonts, CSS optimization in Astro, HTML streaming, Astro build optimization, Astro CDN configuration, Route Caching API, Lighthouse audit for Astro, hydration performance, client:visible vs client:load, or Astro asset pipeline.
astro-security
This skill should be used when implementing Astro security, configuring Content Security Policy in Astro, preventing XSS in Astro, using set:html safely, handling secrets in Astro, configuring astro:env, Astro authentication patterns, Astro Session API, CSRF protection in Astro, configuring security.checkOrigin, Astro cookie security, middleware security patterns, Astro CORS configuration, protecting API endpoints, security.allowedDomains, environment variable security in Astro, import.meta.env secret leakage
astro-troubleshooting
This skill should be used when debugging Astro issues, identifying Astro anti-patterns, fixing common Astro mistakes, troubleshooting Astro errors, resolving "document is not defined" in Astro, resolving "window is not defined" in Astro, diagnosing a component not interactive, fixing content validation errors, investigating why an Astro build fails, debugging hydration issues, solving Astro 5 migration problems, fixing slug vs id errors, resolving render method not found, diagnosing Astro performance problems, reducing too much JavaScript in Astro, fixing Astro routing errors, or addressing form resubmission warnings.
fastify-best-practices
This skill should be used when working on any Fastify project or when the user asks about Fastify best practices, conventions, or patterns. Trigger when: working on a Fastify project, creating Fastify plugins, registering routes, using decorators, organizing Fastify application structure, using @fastify/autoload, creating encapsulated contexts, working with fastify-plugin, building Fastify APIs, configuring Fastify server options, using the register API, understanding Fastify encapsulation, project scaffolding with fastify-cli
fastify-hooks-lifecycle
This skill should be used when implementing Fastify hooks, understanding hook execution order, using onRequest/preParsing/preValidation/preHandler/preSerialization/onError/onSend/onResponse hooks, using onReady/onListen/onClose/onRoute/onRegister application hooks, debugging hook chain issues, adding authentication hooks, implementing request lifecycle interceptors, working with Fastify lifecycle events, or understanding when request.body is available.
fastify-logging
This skill should be used when configuring Fastify logging, setting up Pino logger, using child loggers, implementing log redaction, configuring log transports, using pino-pretty for development, async logging with sonic-boom, structured JSON logging, request correlation IDs, log levels, configuring pino.final for crash handling, multi-target log transports, or Fastify observability.
fastify-production
This skill should be used when deploying Fastify to production, configuring Fastify security headers, setting up reverse proxy with Fastify, implementing graceful shutdown, configuring @fastify/helmet, @fastify/cors, @fastify/rate-limit, trustProxy settings, Kubernetes Fastify deployment, Fastify performance tuning, request timeouts, handler timeouts, return503OnClosing, prototype poisoning protection, production Fastify checklist, or hardening Fastify server.
fastify-schemas-validation
This skill should be used when writing Fastify JSON schemas, configuring Ajv validation, using fast-json-stringify serialization, defining request body/querystring/params/headers schemas, sharing schemas with addSchema and $ref, using fluent-json-schema, configuring response schemas, handling validation errors, setting up custom validators, working with Fastify schema design, coercion issues, nullable types, or allErrors configuration.
fastify-testing
This skill should be used when testing Fastify applications, using .inject() for HTTP testing, writing Fastify unit tests, testing Fastify plugins in isolation, separating app from server for testing, using light-my-request, testing route handlers, integration testing Fastify, test setup and teardown with Fastify, parallel test execution, testing Fastify hooks, or mocking in Fastify tests.
fastify-troubleshooting
This skill should be used when debugging Fastify issues, identifying Fastify anti-patterns, diagnosing common Fastify mistakes, performing Fastify error troubleshooting, investigating request.body undefined in hook, fixing decorator shared across requests, resolving hook executing twice, handling reply already sent error, debugging encapsulation not working, fixing schema validation bypassed, diagnosing serialization error 500, handling Fastify crash unhandled rejection, troubleshooting plugin not loading, resolving decorator not found, or diagnosing Fastify performance problems.
fastify-typescript
This skill should be used when using TypeScript with Fastify, configuring type providers, using @fastify/type-provider-typebox, using @fastify/type-provider-json-schema-to-ts, typing Fastify plugins, declaration merging for decorators, typing route handlers, FastifyInstance generics, FastifyRequest generics, FastifyReply generics, withTypeProvider, typing custom decorators, or Fastify TypeScript configuration.
a11y-aria-patterns
Use this skill when the user asks about ARIA, ARIA roles, ARIA attributes, aria-label, aria-labelledby, aria-describedby, aria-expanded, aria-hidden, aria-live, aria-required, aria-invalid, "WAI-ARIA", "ARIA Authoring Practices", "APG pattern", "accessible name", "accessible description", live regions, custom widgets, dialogs, menus, tabs, accordions, comboboxes, tooltips, tree views, carousels, or is building any custom interactive component that requires ARIA roles and keyboard behavior beyond native HTML elements.
a11y-forms
Use this skill when the user asks about accessible forms, form labels, form errors, input accessibility, "aria-required", "aria-invalid", "aria-describedby", fieldset and legend, "form validation accessibility", required fields, error messages, placeholder accessibility, password fields, file uploads, date inputs, select elements, checkbox groups, radio groups, "WCAG 3.3", "label instructions", or is building any form that needs to be screen reader compatible and keyboard accessible.
a11y-keyboard-focus
Use this skill when the user asks about keyboard navigation, keyboard accessibility, focus management, focus trapping, focus ring, focus indicator, ":focus-visible", skip links, "tabindex", "Tab key navigation", "focus order", "focus returns", "orphaned focus", "focus lost", "modal focus trap", "focus after close", "roving tabindex", "keyboard trap", or is building modals, dialogs, drawers, dropdowns, or any component requiring programmatic focus management. Also use when diagnosing why keyboard navigation feels broken.
a11y-semantic-html
Use this skill when the user asks about semantic HTML structure, heading hierarchy, landmark regions, div soup, divitis, "which HTML element should I use", "semantic markup", "HTML accessibility", "ARIA landmarks", "page structure", "section vs div", "article vs section", "when to use aside", or is writing HTML templates, page layouts, or component markup that requires accessible structural decisions. Also use when reviewing HTML for screen reader compatibility or document outline correctness.
a11y-testing
Use this skill when the user asks about accessibility testing, axe-core, jest-axe, "@testing-library", "@axe-core/playwright", "Playwright accessibility testing", "WAVE", "Lighthouse accessibility", "automated a11y tests", "accessibility CI/CD", "eslint-plugin-jsx-a11y", "a11y linting", "axe DevTools", setting up accessibility tests, writing accessibility tests for React components, integrating a11y checks into a test suite, or understanding what automated tools can and cannot catch. Also use when asked to add automated a11y testing to a project.
chrome-ext-best-practices
This skill should be used when working on any Chrome extension project or when the user asks about Chrome extension best practices, conventions, or patterns. Trigger when: setting up a new Chrome extension, configuring WXT, asking about MV3 architecture, "Chrome extension project structure", "WXT config", "extension entrypoints", "manifest v3 setup", "when to use content script vs service worker", "extension context boundaries", "Chrome extension build", "wxt.config.ts", "extension packaging", "Chrome Web Store submission", "cross-browser extension".
chrome-ext-messaging
This skill should be used when implementing messaging between Chrome extension components or when the user asks about inter-process communication in extensions. Trigger when: "extension messaging", "chrome.runtime.sendMessage", "chrome.tabs.sendMessage", "content script messaging", "port.postMessage", "runtime.connect", "Protocol Map", "@webext-core/messaging", "message passing", "extension IPC", "sendMessage vs connect", "async message response", "return true onMessage", "typed messaging", "message schema".
chrome-ext-permissions
This skill should be used when working on Chrome extension permissions or Chrome Web Store compliance. Trigger when: declaring extension permissions, "manifest permissions", "activeTab vs tabs", "optional_permissions", "host_permissions", "Chrome Web Store rejection", "permission minimization", "over-permissioning", "CWS review", "Purple Potassium", "extension permission audit", "narrowest permission", "permission warnings", "chrome.permissions.request", "permission justification".
chrome-ext-security
This skill should be used when working on security aspects of a Chrome extension or when the user asks about Chrome extension security best practices. Trigger when: implementing Content Security Policy in extensions, "extension CSP", "eval in extension", "content script security", "extension XSS", "remote code in extension", "MV3 security", "unsafe-eval", "content script isolation", "DOM safety in extension", "Trusted Types", "extension sandbox", "chrome extension security audit", "innerHTML in extension", "message validation".
chrome-ext-service-worker
This skill should be used when working with Chrome extension service workers or background scripts. Trigger when: "service worker lifecycle", "background script", "extension service worker", "chrome.alarms", "offscreen document", "service worker restart", "top-level listener", "service worker idle", "event listener registration", "chrome.offscreen", "service worker termination", "state rehydration", "persistent background", "MV3 background", "service worker wake-up", "keepalive", "setTimeout in service worker".
chrome-ext-storage
This skill should be used when working with data storage in Chrome extensions or when the user asks about extension storage patterns. Trigger when: "chrome.storage", "extension storage", "storage.local", "storage.sync", "storage.session", "IndexedDB in extension", "extension data persistence", "write-through cache", "storage quota", "unlimitedStorage", "chrome.storage.onChanged", "reactive storage", "WXT storage", "storage.defineItem", "storage migration", "sync vs local storage".
chrome-ext-testing
This skill should be used when writing or setting up tests for a Chrome extension. Trigger when: "test chrome extension", "extension unit test", "extension e2e test", "Vitest extension", "Playwright extension", "@webext-core/fake-browser", "test content script", "test service worker", "test messaging", "test storage", "extension integration test", "test permission flow", "extension test framework", "mock chrome API", "browser mode testing".
chrome-ext-troubleshooting
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 checklist", "extension review".
chrome-ext-ui-react
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 management extension".
loop-goal-engineering
This skill should be used when the user wants to author agentic loops or goal/completion conditions — "write a loop prompt", "loop engineering", "set up a ralph loop", "run Claude overnight", "write a /goal condition", "goal mode", "goal engineering", "stop condition for my agent", "completion criteria", "definition of done for the agent", "long-horizon task setup", "keep the agent working until", "make Codex run until tests pass", "PLANS.md", "harness for a long run", "my agent stops too early", "my agent never finishes", or wants Claude Code /loop, /goal, Stop hooks, or Codex Goal Mode set up well. Covers loop prompt authoring, goal condition design, the four-file long-horizon scaffold, and anti-reward-hacking hardening. For ordinary single-shot prompts, use prompt-engineering instead.
prompt-decompiler
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 existing prompt and wants it analyzed, adapted, simplified, or understood. Covers prompt anatomy, technique identification, structural analysis, cross-platform migration, and weakness mapping.
prompt-engineering
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 cross-model migration. Use for any prompt-related task, even simple ones.
gws-script
Manage Google Apps Script projects.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.