Productivity

whyashthakker Bundle

Writes and rewrites landing pages for products, services, offers, launches, and campaigns. Use when the user asks for landing page copy, hero sections, section-by-section messaging, conversion-focused page structure, CTA rewrites, or page copy tailored to paid traffic, email traffic, or product launches.

whyashthakker Bundle

Writes upsell and cross-sell messaging for email, in-app, and sales surfaces. Use when the user asks to promote upgrades or adjacent offers.

whyashthakker Bundle

Writes feature announcements for email, in-app, changelog, social, and launch pages. Use when the user asks to announce a product update.

opengitcode Skill

Manage Things 3 via the `things` CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenShell to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.

korchasa Skill

Run all framework acceptance tests. Default is sequential (single `deno task acceptance-tests`). Use `--parallel` for 5-subagent parallel mode. Triggers on "run all acceptance tests", "acceptance-tests all", "/acceptance-tests-all".

korchasa Bundle

Show the current state of the project's tasks, hiding archived ones, by deriving the project's own task layout from AGENTS.md and generating a small project-local status script. Use when the user asks which tasks are open, in progress, or how far along the work is.

korchasa Bundle

Supplies the accepted task format — GODS, meaning Goal, Overview, Definition of Done, Solution — and its file template. Use when the user asks what that format is, or to write up an already-decided piece of work in it. NOT for planning work before coding — weighing variants and critiquing a plan belong to the planning skill, which writes the file itself.

aibangjuxin Bundle

Polish workplace emails into clear, natural, professional English with Chinese-English comparison output and focused vocabulary explanations. Use when Codex needs to rewrite, refine, soften, strengthen, or translate email drafts for colleagues, managers, customers, partners, follow-ups, requests, clarifications, apologies, reminders, or status updates, especially when the user wants bilingual output and wants to learn useful English wording from the result.

matthewharwood Skill

Playwright end-to-end tests pointed at the running dean-stack app — route workflows under `apps/web/tests/app/`, real IDB hydration via `page.evaluate`, BroadcastChannel cross-tab verification, IDB-seeded fixtures (no mocks). Triggers on: playwright app test, e2e workflow, app-level test, route workflow test, idb seeded test, idb assertion.

matthewharwood Skill

Local-only second-opinion lint pass via `eslint-plugin-sonarjs` — code-smell, cognitive-complexity, and bug-pattern rules layered on top of Biome (which owns formatting + the bulk of lint). NO SonarQube server, NO `sonar-scanner`, NO project token. Runs as `bun run check:sonar` (the workspace task) and as the standalone `.github/workflows/sonarjs.yml` workflow. Triggers on: sonar, sonarjs, eslint-plugin-sonarjs, cognitive-complexity, pseudo-random, no-nested-conditional, no-nested-functions, void-use, second-opinion lint, eslint.sonar.config.mjs.

tamnguyendinh Skill

Use when the task is to implement code changes from an assigned scope, including bug fixes, follow-ups, rejects, or current-worktree repair.

rudironsoni Skill

Answer Orlix architecture, ownership, decision, epic, story, task, capability, provenance, and relationship questions from the canonical docs ontology.

rudironsoni Bundle

Add or update Orlix knowledge in the canonical docs ontology. Use for architecture, decision, epic, story, task, capability, terminology, provenance, and durable lesson changes.

raphaelmansuy Skill

Read, search, and create notes in the Obsidian vault.

lofcz Skill

Work a task end-to-end with lean context gathering, implementation, and verification

lofcz Bundle

Create, verify, repair, and close durable Codex goals with measurable outcomes, evidence gates, plan templates, blocker handling, completion audits, and goal-backed workflow repair.

cody-hutson Bundle

Organizational Change Management (OCM) Lead Specialist — emulates an OCM Lead driving a go-live's organizational change end-to-end by composing the change-management function-skill across the full lifecycle. Composes change-management (impact · training · readiness · hypercare · adoption · comms) — invokes it through the core/ registry skill-chain, never re-implements it (ADR-019). Modes: Change Impact · Training & Adoption · Readiness Go/No-Go · Hypercare & Adoption Outcome · Change Comms Program. Use when the platform should act as the OCM lead, run or own the change program for a go-live, or drive organizational change as one coherent workflow. Triggers: "act as OCM lead", "run the change program", "own the change for this go-live", "drive organizational change", "lead the org change for this rollout", "manage the change end-to-end".

the-perfect-developer Bundle

This skill should be used when the user asks to "evaluate an implementation", "run the zen evaluation workflow", "check if the plan was properly implemented", "review implementation against a plan", or needs to assess implementation quality and surface improvement suggestions after a zen build cycle.

floomhq Skill

Read and send WhatsApp messages via SQLite DB access and a verified send script. Use when user says "check WhatsApp", "read WhatsApp", "messages from X", "send WhatsApp to X", "message X on WhatsApp", or any WhatsApp read/send task.

floomhq Skill

Systematic debugging workflow for any type of error or unexpected behavior. Use when user says "debug this", "why is this failing", "help me fix this error", "something is broken", or shares an error message or unexpected output. Follows a root-cause-first approach rather than trial-and-error patching.

floomhq Skill

Context vault operations: read/update todos, add log entries, search vault content, read strategy/project docs, update project files. Use when user says "vault", "add todo", "update todos", "log entry", "search vault", "check todos", "context vault", "add to log", or any operation on a personal context vault.

floomhq Skill

Pre-flight check before starting any significant work. Use when starting a new task, before making changes to production systems, or when asked to "check if this is safe", "should I do this", "validate my plan", or "bouncer check". Evaluates risk, reversibility, and whether the right preconditions are met before proceeding.

floomhq Skill

Daily briefing: unified status check across all systems. Unread email counts, open GitHub issues, active workplans, todos, system health. Use when user says "morning", "daily briefing", "status", "what's going on", "catch me up", "what did I miss", or starts a new day.

floomhq Skill

Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.

floomhq Skill

Negotiation analyst for high-stakes deals: co-founder exits, business separations, contract terms, salary negotiations, investor terms. Use when the user asks to: (1) analyze a counterparty's position or message, (2) score/review a draft message before sending, (3) draft a counter-offer, (4) structure BATNA/ZOPA analysis, (5) track concessions across rounds, (6) detect traps or information leakage in proposed terms, (7) prepare for a negotiation call or meeting. Triggers: "score this message", "analyze their position", "what's my BATNA", "review before I send", "draft a counter", "is this a trap", "negotiate", "negotiation", "counter-offer", "deal terms".

floomhq Skill

Check, read, and search emails across IMAP accounts. Use when user says "check email", "read inbox", "any new emails", "check mail", "email from X", "unread messages", or mentions checking specific email accounts.

floomhq Skill

Write effective cold outreach messages for sales, partnerships, networking, or job outreach. Use when user asks to "write a cold email", "draft an outreach message", "reach out to X", "send a pitch to", "write a connection request", or needs to contact someone they don't know professionally. Produces concise, personalized, non-spammy outreach.

floomhq Skill

Templates and patterns for spawning and coordinating subagents (parallel Claude instances). Use when a task benefits from parallelization, independent verification, or specialized sub-tasks. Triggers: "use subagents", "spawn agents", "parallelize this", "run in parallel", "use multiple agents", or when a task has clearly independent parallel workstreams.

ed3design Skill

Use when editing or expanding an already-GA-promoted skill (suffix-less name, banner says PROMOTED) to add a new capability/class/feature. Different from `skill-tdd-promotion-workflow` which covers DRAFT→GA. This skill covers GA→GA+Capability — the failure mode is silent-rename-or-expand without RED-test for the new capability (Iron-Law violation). Trigger on phrases like "extend skill with X", "add a new class to an existing skill", "extend asyncpg-skill with JSONB", "rename GA skill + extend capability", "skill rename with content expansion", "Cycle-2 capability for promoted skill". Do NOT load for new skill from scratch (`superpowers:writing-skills`), for DRAFT→GA promotion (`skill-tdd-promotion-workflow`), for minor edit without new capability (just edit), or when the target skill doesn't exist.

ed3design Skill

Use at the end of any productive session, when writing a Daily Note, when the user says "wrap up" / "remember" / "session done", or proactively after observing repeated workflow patterns within a session. Trigger on phrases like "end of session", "let's wrap up", "end of day", "session wrap-up", "end of day review", "what did Claude learn today", "is there a skill in here?", "post-session review", "skill candidate review". Do NOT load mid-session for active task work, for single-task sessions with nothing repeatable, or when the user is in mid-debug (they need closure, not meta-reflection).

ed3design Skill

Use when implementing a multi-task TDD plan via `superpowers:subagent-driven-development` AND all individual tasks have already passed their per-task two-stage review. Per-task reviews check one commit against one task — they cannot catch cross-commit drift that only appears when reading the full feature end-to-end. Triggers a final aggregate review looking for: state-machine/algorithm-order drift between spec and code, naming-inconsistency across commits, end-to-end data-flow integrity, commit-message honesty, pre-commit-hook coverage gaps (lazy imports), test-suite cohesion. Trigger phrases like "Tasks 1-N all done", "aggregate review before live-run", "cross-commit drift check", "verify end-to-end behavior against spec". Do NOT load for single-commit reviews, per-task reviews within SDD, branches with <3 atomic feature-commits, or hotfixes without spec-text target.

ed3design Skill

Use BEFORE implementing a non-trivial decision-driven task where multiple outcomes are plausible — backtest planning, algorithm comparison, architecture choice, migration strategy, "should build X or not". Trigger on phrases like "should build X", "plan a backtest", "I need a decision", "test algo variants", "how do I measure success", "max-effort session", "choose refactoring strategy", "define Compound-GO". Produces a Plan-Note with explicit Hypothesis-Matrix (each H + counter-thesis + Distinguishing Metric), Compound-GO-Logic, Out-of-Scope, and Done-Definition. Do NOT load for single-path implementations with no decision ("fix this typo"), brainstorming/exploration phase (use `superpowers:brainstorming` first), plans without binary GO/NO-GO outcome (use `superpowers:writing-plans`), or tasks without a measurable success criterion.

ed3design Skill

Use when writing or reviewing Python code that uses `asyncio.run(...)` as entry-point AND inside the entry-coroutine uses `asyncio.create_task(...)` for fire-and-forget background work (notifications, telemetry, advisor-calls, fan-out HTTP/DB-writes). Without an explicit `await asyncio.gather(*pending_tasks)` before the entry-coroutine returns, `asyncio.run()` closes the event-loop and CANCELS still-pending tasks — silent data-loss of 0-50% of background work. Trigger on phrases like "asyncio.run + create_task", "fire-and-forget cancelled at loop-exit", "telemetry silent dropping", "Loop closed before task finished". Do NOT load for asyncio.Runner / gather-as-entry patterns, long-running daemons (uvicorn, asyncio.Event.wait), sync code with threading.Thread, or non-Python async (JS/Go).

archieindian Skill

Structured ideation before any implementation. Use when starting any non-trivial task.

archieindian Skill

Executes plans task-by-task with verification. Use when implementing a plan.

archieindian Skill

Parallel subagent execution for complex tasks. Use when a task has independent parallel workstreams.