Browse Skills — Page 319

woz-benchmark

WithWoz/wozcode-plugin

Deprecated alias — use `/woz benchmark`.

woz-bug

WithWoz/wozcode-plugin

Deprecated alias — use `/woz-feedback` (bug reports).

woz-feedback

WithWoz/wozcode-plugin

Send feedback or a bug report to the WOZCODE team. Bug reports are tagged for triage and auto-attach session context (session id, anonymous id, OS, arch, Node version).

woz-knowledge

WithWoz/wozcode-plugin

Deprecated alias — use `/woz-kb <op>` (e.g. `/woz-kb status`).

woz-login

WithWoz/wozcode-plugin

Deprecated alias — use `/woz login`.

woz-logout

WithWoz/wozcode-plugin

Deprecated alias — use `/woz logout`.

woz-recall

WithWoz/wozcode-plugin

Semantically search past Claude Code sessions to recall commands, solutions, and context from prior conversations. TRIGGER on 'remember when', 'last time', 'we did this before', 'how did we', or /woz-recall.

woz-review

WithWoz/wozcode-plugin

Deprecated alias — use `/woz review`.

woz-savings

WithWoz/wozcode-plugin

Show the WOZCODE savings report — calls saved, time saved, tokens saved, and lifetime totals.

woz-settings

WithWoz/wozcode-plugin

Deprecated alias — use `/woz settings`.

woz-share

WithWoz/wozcode-plugin

Deprecated alias — use `/woz share`.

woz-status

WithWoz/wozcode-plugin

Deprecated alias — use `/woz status`.

woz-update

WithWoz/wozcode-plugin

Deprecated alias — use `/woz update`.

wp-performance-review

elvismdev/claude-wordpress-skills

WordPress performance code review and optimization analysis. Use when reviewing WordPress PHP code for performance issues, auditing themes/plugins for scalability, optimizing WP_Query, analyzing caching strategies, checking code before launch, or detecting anti-patterns, or when user mentions "performance review", "optimization audit", "slow WordPress", "slow queries", "high-traffic", "scale WordPress", "code review", "timeout", "500 error", "out of memory", or "site won't load". Detects anti-patterns in database queries, hooks, object caching, AJAX, and template loading.

wps-events

wavetermdev/waveterm

Guide for working with Wave Terminal's WPS (Wave PubSub) event system. Use when implementing new event types, publishing events, subscribing to events, or adding asynchronous communication between components.

wpt-update

cloudflare/workerd

>-

openai/wrangler

openai/plugins

Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

cloudflare/wrangler

cloudflare/skills

Run or troubleshoot Wrangler CLI commands in projects that have a wrangler.jsonc, wrangler.json, or wrangler.toml file, including local development, Previews, deployment, and resource management. For new projects and projects without a Wrangler configuration file, use the cf CLI instead.

wrap

ViryaZheng/wrap-skill

>

wrap-up

alirezarezvani/claude-skills

Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says "wrap up", "close this out", "what do I own now", "give me the summary", "recap the agent", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained ./my-agent/agent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.

wrap-up

anthropics/launch-your-agent

Close out (or revisit) a Claude Managed Agent build — refresh the overview page, recap every primitive the founder now owns, show the run log and live status, suggest 1–2 tailored next upgrades, and sweep hygiene (sessions archived, key only in .env, no literal dates in deployment kickoffs). Use when the founder says "/wrap-up", "wrap up", "close it out", "where do things stand with my agent", or at the end of a /launch-your-agent build.

wrike

vm0-ai/vm0-skills

Wrike API for project management. Use when user mentions "Wrike", "wrike.com",

wrike-automation

benjaminasterA/antigravity-awesome-skills

Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas.

wrike-automation-v2

diegosouzapw/awesome-omni-skills

Wrike Automation via Rube MCP workflow skill. Use this skill when the user needs Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

write

ohad6k/emulo

Use for marketing, social, replies, product copy, launch copy, and writing in the user's voice when their Emulo writing profile should guide the task. Do not use for unrelated execution or UI/UX design alone.

Write Tweet

aaronjmars/aeon

Generate 10 tweet drafts across 5 size tiers (2 variations each) on a topic from today's outputs

write_changeset

stripe/stripe-cli-ts-plugin-bootstrap

Create a changeset file documenting changes for the next release.

write-a-prd

softspark/ai-toolkit

Creates PRD via interactive interview + codebase exploration + module design. Triggers: write PRD, product requirements, plan new feature, PRD interview.

write-a-skill

alirezarezvani/claude-skills

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.

write-adr

existential-birds/beagle

Use when you want to generate Architecture Decision Records from this session. Triggers on \"write ADRs\", \"document our decisions\", \"create decision records\", \"record the choices we made\". Also useful after design discussions where decisions were reached but not documented. Does NOT extract decisions alone (use adr-decision-extraction) or provide MADR template (use adr-writing). Orchestrates the full workflow: subagent extraction, user confirmation, parallel generation, and verification.

write-agent-memory-system-review

zby/commonplace

Write or update a local code-grounded agent memory system review from a GitHub repository reference, including checkout refresh, optional sub-agent drafting, semantic QA, and validation.

write-an-adr

UKGovernmentBEIS/inspect_evals

Write an Architectural Decision Record (ADR) to document a significant design choice. Use when user asks to write/create/document an ADR, or to record an architectural decision.

write-api-reference

vercel/next.js

|

write-architecture-docs

prisma/prisma-next

>-

write-blog-post

techwolf-ai/ai-first-toolkit

Write or develop a blog post. Use for blog content - writing, drafting, developing ideas into drafts, or editing. Longer-form than LinkedIn (800-1200 words) with section structure.

write-bug-ticket

ClipboardHealth/core-utils

Use when creating a Linear bug report ticket from conversation context, investigation findings, or user-provided evidence. Focuses on structuring and writing — not investigating.

write-coding-standards-from-file

github/awesome-copilot

'Write a coding standards document for a project using the coding styles from the file(s) and/or folder(s) passed as arguments in the prompt.'

write-connector

langchain-ai/openwiki

Add a new built-in OpenWiki source connector. Use when a user asks to create or implement an OpenWiki connector.

write-content

inhouseseo/superseo-skills

Use when writing a complete SEO article. Includes the full anti-AI-slop ruleset (banned vocabulary, banned phrases, banned structural patterns) and voice rules. The agent researches the SERP itself if needed — no keyword data exports required.

write-endpoints

cloudflare/chanfana

Comprehensive guide for building OpenAPI endpoints with chanfana - schema definition, request validation, CRUD operations, D1 database integration, and exception handling

write-feature-ticket

ClipboardHealth/core-utils

Use when creating a Linear feature request ticket from conversation context, a brief description, or code/PR analysis. Interviews the user for clarity when context is insufficient.

write-file

openakita/openakita

Write content to file, creating new or overwriting existing. When you need to create new files, update file content, or save generated code/data.

write-frontend-tests

Significant-Gravitas/AutoGPT

Analyze the current branch diff against dev, plan integration tests for changed frontend pages/components, and write them. TRIGGER when user asks to write frontend tests, add test coverage, or 'write tests for my changes'.

write-gatekeeper

cloudflare/cloudflare-os

Guides implementation of Gatekeeper Workers that bridge Gadgets to external services. Covers auth, capability-based API design, approval queue integration, caching, and action simulation. Load when creating, modifying, or reviewing the implementation of a gatekeeper.

write-guide

vercel/next.js

|

write-judge-prompt

hamelsmu/evals-skills

>

write-linkedin-post

techwolf-ai/ai-first-toolkit

Write or develop a LinkedIn post. Use ALWAYS for LinkedIn content - writing, drafting, developing ideas into drafts, or editing.

write-my-release-notes

microsoft/vscode-docs

Generate VS Code release notes for the features you worked on in a milestone. ALWAYS use this skill when the user asks to "write release notes for my features", "document my milestone features", or "generate release notes from my issues". It gathers the milestone features you own from GitHub, analyzes each feature and its related issues, and writes user-focused feature sections into the milestone release notes file.

write-opinion

techwolf-ai/ai-first-toolkit

Write or develop an opinion piece (opiniestuk/op-ed). Use when asked to write opinion articles, newspaper pieces, or similar long-form opinion content.

write-paper

Aperivue/medsci-skills

Full-pipeline medical/scientific paper writing. 8-phase IMRAD workflow from outline to submission-ready manuscript. Supports original articles, case reports, case series, meta-analyses, AI validation studies, animal studies, and technical notes. Do NOT trigger for self-checking (use self-review instead).

write-plan

existential-birds/beagle

Use when you have a finalized brainstorm-beagle spec at `.beagle/concepts/<slug>/spec.md` and need a bite-sized, TDD-driven implementation plan before any code is written. Triggers on: \"write a plan\", \"plan this spec\", \"turn the spec into a plan\", \"now plan the implementation\", \"write-plan\". Reads the spec, designs the file structure, decomposes work into 2-5 minute TDD steps with exact paths and commands, self-reviews against the spec, gets user approval, then writes to `.beagle/concepts/<slug>/plan.md` and offers to generate an execution handoff prompt via the subagent-prompt skill. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.

write-prd

yonatangross/orchestkit

Write PRD — Product Requirements Documents with structured 8-section templates, user stories, acceptance criteria, and value proposition validation. Use when writing PRDs, defining product requirements, creating user stories with INVEST criteria, or building go/no-go decision frameworks.

write-product-spec

warpdotdev/oz-for-oss

Write a PRODUCT.md-style spec for a significant user-facing feature in this repository, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.

write-protocol

Aperivue/medsci-skills

>

write-query

anthropics/knowledge-work-plugins

Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.

write-review-artifact

lyndonkl/claude

Composes the final Technical Reviewer artifact at ops/technical-reviewer/YYYY-MM-DD-{slug}-review.md. Enforces frontmatter schema, section order (Summary → Blockers → Claims → Boundary-Break Suggestions → Glossary Alignment → Could-Not-Verify → Research Log), go/no-go decision rule, and never-modify-draft principle. Use exactly once per Technical Reviewer run as the last step. Trigger keywords: write review, technical review artifact, compose review, claim review output.

write-section-promise

lyndonkl/claude

Crafts the one-sentence promise a substacker section makes to its reader — specific, testable, non-overlapping with other sections, written in the writer's voice (not marketing). Use when propose-section stages a new section or when an existing promise is being revised. Trigger keywords: section promise, one-sentence promise, section statement, reader promise.

write-sequences

swaruplab/operon

Write biological sequences to files (FASTA, FASTQ, GenBank, EMBL) using Biopython Bio.SeqIO. Use when saving sequences, creating new sequence files, or outputting modified records.

write-spec

anthropics/knowledge-work-plugins

Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.

write-tech-debt-ticket

ClipboardHealth/core-utils

Use when creating a Linear tech debt ticket while working in the codebase — from code review, PR comments, codebase audits, or post-incident findings. Expects deep technical context; classifies debt, assesses interest/risk with evidence, and justifies impact.

write-tech-spec

warpdotdev/oz-for-oss

Write a TECH.md-style spec for a significant feature in this repository after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.

huggingface/write-tests

huggingface/OpenEnv

Write failing tests from requirements. Invoke for each todo before /implement.

github/write-tests

github/replica

Write meaningful Replica tests. Use when adding regression coverage, testing new behavior, or changing existing automated tests.

write-the-docs

supabase/supabase

>-

write-timestamp

langchain-ai/docs

Use when the user wants the current date and time written to a file via the bundled script inside the sandbox.

write-unit-tests

stripe/stripe-android

Use when writing or structuring unit tests or fake test implementations in stripe-android — covers scenarios, Turbine interaction tracking and Flow testing, and Truth assertions

write-weekly-digest

lyndonkl/claude

Renders the Trend Scout ranked keep-and-drop lists into ops/trend-scout/YYYY-WW-digest.md using the agent voice profile and including an appendix of all sources surveyed. Use once per weekly run as the terminal skill. Trigger keywords: weekly digest, write digest, Trend Scout digest, Saturday morning digest.

write-weekly-report

lyndonkl/claude

Composes the substacker final ops/growth-analyst/YYYY-WW-report.md from ingest + baseline + attribute + per-section + public-page outputs. Enforces 400-800 word budget, YAML frontmatter schema, seven-section body structure. Truncates weakest sections first when over budget. Injects data-caveats from any degraded-mode flags upstream. Use as the final compose step of the weekly pipeline. Trigger keywords: weekly report, compose report, growth report, Monday report.

writer

microsoft/aspnetcore-ja-handbook

ASP.NET Core ハンドブックの新規章コンテンツを作成する。Use when: 新しい章を書く、ドキュメントを作成する、チャプターを追加する、コンテンツを執筆する。技術ドキュメントのライティング、ASP.NET Core ガイドの執筆。

writer

rileyhilliard/claude-essentials

Writing style and tone guide for human-sounding content. Use when writing documentation, READMEs, commit messages, PR descriptions, blog posts, or any user-facing content.

writer-automation

ComposioHQ/awesome-claude-skills

"Automate Writer tasks via Rube MCP (Composio). Always search tools first for current schemas."

writer-v2

diegosouzapw/awesome-omni-skills

LibreOffice Writer workflow skill. Use this skill when the user needs Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

writing

swaruplab/operon

Use this skill to create high-quality academic papers, literature reviews, grant proposals, clinical reports, and other research and scientific documents backed by comprehensive research and real, verifiable citations. Use this skill whenever the user asks for written output such as a report, paper...etc.

Writing Evergreen Comments

obra/clank

Write comments explaining WHAT and WHY, never temporal context or history

Writing Hookify Rules

anthropics/claude-code

This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.

writing-agent-relay-workflows

AgentWorkforce/relay

Use when building multi-agent workflows with the relay broker-sdk - covers the WorkflowBuilder API, DAG step dependencies, agent definitions, step output chaining via {{steps.X.output}}, verification gates, evidence-based completion, owner decisions, dedicated channels, dynamic channel management (subscribe/unsubscribe/mute/unmute), swarm patterns, error handling, event listeners, step sizing rules, authoring best practices, and the lead+workers team pattern for complex steps

writing-agents-md

compozy/agh

Author lean AGENTS.md/CLAUDE.md instruction files — resident system-prompt context where every line pays rent. Use when writing an agent instruction file from scratch, auditing or trimming a bloated one, or gating whether a new rule earns residence and at which scope. Don't use for on-demand skills (use writing-skills) or human-facing docs and READMEs.

writing-assistant

infranodus/skills

Refine texts in any language: perfect grammar and spelling, paraphrase ideas, avoid AI detection while maintaining authentic voice. Detects grammatical patterns that signal cognitive states or structural issues—acting as a sensory system for deeper strategic insights.

writing-changelogs

supabase/supabase-go

Guides the writing and editing of changelog entries in the per-module CHANGELOG.md files. Use when a user-facing change needs an entry, when drafting or reshaping an Unreleased section, or when reviewing entries at release time. Covers the type headings, the entry shape and the succinctness bar - what an entry says and what it leaves to the docs.

writing-clearly-and-concisely

obra/the-elements-of-style

Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.

writing-clearly-and-concisely

jjmartres/opencode

Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.

writing-cli-skills

Kastalien-Research/thoughtbox

Guide for writing skills that wrap CLI tools. Use when creating a new CLI skill. For review, run through the Checklist section.

writing-commentary

supabase/supabase-go

Guides the content and style of all comments - Go doc comments on exported or internal identifiers, package overviews in doc.go, inline comments and comments in scripts, workflows, SQL and configuration files. Use when writing, editing or reviewing any comment on any surface, including comments authored in passing while implementing something else. Covers audience focus (API consumer versus codebase maintainer), contract-first phrasing and where rationale, history and cross-component notes belong instead.

writing-data

durable-streams/durable-streams

>

writing-dna-discovery

robertguss/claude-code-toolkit

Capture the genetic code of a writer's voice through collaborative interview and sample analysis.

writing-docs

medusajs/medusa

Writes and updates Medusa documentation MDX files for the book, resources, ui, user-guide, and cloud projects. Use when making documentation changes based on code diffs, adding new pages, updating existing content, or updating component examples. ALWAYS load this skill before modifying any MDX file in www/apps/.

writing-docs

remotion-dev/remotion

Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.

writing-examples

supabase/supabase-go

Guides the creation, update, merging and deletion of examples - the runnable Example functions that render on pkg.go.dev, the code snippets inside doc comments and the example programs under examples/. Use when adding an example, reworking one or deciding whether an existing example is replaced, upgraded, folded into a sibling or removed outright. Covers the removal test and when an example earns its place.

writing-for-agents

e2b-dev/herdr-e2b-sandbox

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

writing-great-skills

trailofbits/skills-curated

>-

writing-guidelines

rohitg00/pro-workflow

Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes. Use when writing or editing documentation, interface copy, or any text a human will read. Says "write the README", "improve this copy", "draft the docs", "word this error".

writing-guidelines

vercel-labs/agent-skills

Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".

writing-instructions

oaustegard/claude-skills

"Write effective instructions for Claude: project instructions, standalone prompts, and skill content. Use when users need help writing prompts, setting up project instructions, choosing between instruction formats, or improving how they communicate with Claude. Covers writing principles, model-aware calibration, and format selection. For building and testing complete skills, use skill-creator instead."

writing-job-descriptions

liqiongyu/lenny_skills_plus

Write outcome-based job descriptions and role scorecards.

writing-lean-proofs

trailofbits/skills

Writes and reviews structured Lean 4 proofs and designs Lean libraries following Mathlib conventions. Use when proving theorems in Lean, formalizing mathematics or specifications in Lean 4, defining new types or definitions in a Lean library, reviewing Lean proofs for readability and maintainability, refactoring long tactic proofs into lemmas, filling in sorry placeholders in a Lean development, setting up CI or linters for a Lean project, diagnosing slow proofs or maxHeartbeats timeouts, or writing custom tactics, macros, or linters.

writing-migration-guides

supabase/supabase-swift

>

writing-mstest-tests

microsoft/testfx

>

writing-north-star-metrics

liqiongyu/lenny_skills_plus

Define or refresh a product North Star metric + driver tree.

writing-orchestration

robertguss/claude-code-toolkit

This skill should be used when orchestrating complex writing workflows with multiple phases. It provides two-agent orchestration patterns, the two-gate content readiness assessment, 10 baseline writing strategies, 20+ situational strategies, and quality checkpoints. Inspired by the Spiral Writing System.

microsoft/writing-plans

microsoft/FluidFramework

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge