Writing Claude Skills
1 882 writing skills from 445 authors. They draft and edit prose. Half of them fit into 1 924 tokens or less — that is what one costs your context window when the agent loads it. 283 ship runnable scripts rather than instructions alone. We also found 239 copies of these same skills sitting in other people's repositories — counted once here, not 239 times.
1 882 unique 445 authors 185 from vendors
Keep a Changelog format guidelines and entry writing best practices. Use when writing changelog entries, updating CHANGELOG.md, or following Keep a Changelog specification.
Write documents using the HWPR/AWOR framework -- separating human value judgments from AI-expanded content so critical information is not buried. Triggers when the user requests writing, rewriting, or reviewing document quality.
Professional User Story and documentation system construction. Assists in writing high-quality User Story documents through guided interviews to uncover requirements context and acceptance criteria, and places documents precisely in the standardized docs directory structure. Triggers when the user requests writing User Stories, describing feature requirements, or initializing project documentation structure.
Kiểm tra chính tả, dấu câu, khoảng trắng, cấu trúc câu, tham chiếu đại từ và kết hợp từ trong văn bản tiếng Việt. Dùng khi người dùng yêu cầu soát lỗi hoặc proofread; không dùng để áp một phong cách, đổi nội dung, sửa code/URL/identifier, hay coi lựa chọn register và phương ngữ là lỗi ngữ pháp.
Turn user-provided data, notes, research, product facts, or structured inputs into AnyCap-style blog posts and then enrich those posts with first-party evidence blocks when needed. Use when a user wants a blog, article, tutorial, learn page, or SEO content draft written in the tone of the AnyCap website. Best fit when the input is data-first rather than prose-first: spreadsheets, JSON, bullets, notes, source URLs, benchmarks, product facts, or rough research. Trigger on: write blog from data, turn notes into article, blog drafting, article production, learn page drafting, SEO article in AnyCap tone, or requests to convert structured inputs into publish-ready content.
Build topic reserves by searching your entire system, or run discovery mode to find what connects across territories. Use when consolidating scattered knowledge on a topic, before writing/sharing, or when curiosity has no specific target.
>- Specialized prompt-building methodology for content and communications tasks. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output) for writing, editing, content strategy, copywriting, audience analysis, editorial evaluation, cross-channel adaptation, and persuasion design. Use when building a Claude prompt or system prompt for content creation, editorial workflows, or communications tasks. copywriting," "prompt for blog posts," "prompt for email sequences," "system prompt for editorial," "prompt for messaging framework," "content brief prompt," "prompt for audience analysis," "prompt that produces better content." Do NOT use for writing content directly — this Skill builds prompts that produce better content. Do NOT use for evaluating or scoring existing prompts — use rootnode-prompt-validation if available. Do NOT use for general prompt compilation — use rootnode-prompt-compilation if available.
>- Conversational profile builder. Produces validated JSON config files for any rootnode Skill that consumes profile-shaped configuration (handoff trigger check, mode router, critic gate, future Skills). Reads a target JSON Schema (draft-07), conducts a progressive-depth interview using plain-language questions, validates answers, and writes the resulting JSON to a destination path. Schema-agnostic — works with any profile schema conforming to draft-07. Use when a user needs to create, clone, or revise a profile and you do not want them hand-editing JSON. Trigger "set up my profile," "edit my profile," "clone the X profile," "walk me through making a profile." Do NOT use when the user already has a working profile and only wants to invoke the consuming Skill, when the schema cannot be located, or for non-profile JSON config work. Always validate before writing.
Board meeting preparation, investor updates, and executive communication. Use when preparing board decks, writing investor updates, handling bad news with the board, structuring QBRs, or building board-level metric discipline. Includes the "Three Things" narrative model, the 4-tier metric hierarchy, and the pre-brief pattern that prevents board surprises.
Use when App Store listing text must be translated or market-adapted across locales, including descriptions, keywords, What's New, subtitles, names, privacy text, and App Store Connect languages. Not for non-translation metadata edits, release-note drafting, or subscription/IAP display-name localization.
Use when App Store listing metadata in canonical `./metadata` JSON needs field edits, validation, push, keyword sync, or legacy fastlane migration. Not for translation-first localization, release-note drafting, or subscription/IAP display-name localizations.
Use when the requested App Store artifact is What's New release notes or promotional text, drafted from git history, bullets, or free text and optionally localized. Not for full listing translation, canonical metadata field sync, or subscription/IAP display names.
Infer a player's underlying values and motivational priorities from behavior, then translate those into design implications. Use when designing personalization, segmentation, dynamic guidance, live-ops targeting, adaptive missions, re-engagement strategies, or feature prioritization; when behavior suggests that what players actually care about differs from what the design assumes; or when a team needs a behavior-first player profile rather than a demographic or archetype-only model.
Use when publishing or updating a Zeabur template to the marketplace. Use when user says "publish template", "update template online", "push template to Zeabur", or "create template on Zeabur". Do NOT use for deploying templates (use zeabur-template-deploy instead). Do NOT use for editing template YAML (use zeabur-template instead).
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Use when the user says 'export my site', 'backup my pages before editing', 'download my content locally', or 'migrate content to my other site'. Exports pages, posts, and custom posts to portable local packages with builder data, media, and markdown, then imports elsewhere with ID remapping.
Use this skill for any task involving writing Thai-language social media captions, posts, or short-form copy. Trigger whenever the user asks to: write a caption for Facebook, Instagram, TikTok, Threads, X (Twitter), Pantip, or LINE TIMELINE in Thai, draft a Thai social post, write a Thai product/review/giveaway post, pick hashtags for a Thai audience, or adapt copy for a Thai social channel. Also trigger for requests like "เขียนแคปชั่น", "caption ภาษาไทย", "เขียน TikTok caption", "โพสต์ Facebook", "ลงไอจี", "caption social media Thai", "เขียนรีวิว", or any variation. If the output is a short Thai post designed to be published on a social platform, use this skill.
Use this skill for any task involving English-Thai or Thai-English translation, localization, or rewording. Trigger whenever the user asks to: translate text between Thai and English, localize content for a Thai audience, render English idioms in Thai (or vice versa), pick the right pronouns and register, choose between keeping a term in English vs ทับศัพท์, or fix awkward translations. Also trigger for requests like "แปลเป็นไทย", "แปลอังกฤษเป็นไทย", "ช่วยแปลหน่อย", "localize Thai", "translate this", "Thai version", or any variation. If the task involves moving meaning between Thai and English at any level — word, sentence, document — use this skill.
> Apply Sam Dumont's personal writing voice and style when drafting reports, blog posts, technical documentation, client communications, Slack messages, LinkedIn posts, or any written content. Use this skill whenever Sam asks to write, draft, review, or improve text in his voice - including phrases like "write this for me", "draft a post", "in my style", "my voice", "write a report", "blog post", "client email", "Slack message", or any content creation task where Sam's personal tone should come through. Also trigger when Sam asks to translate content while maintaining his voice. Works in both English and French.
Use when writing a technical blog post from raw project data like research notes, session logs, Reddit/LinkedIn drafts, code, hex dumps, or screenshots. Also use when Sam says "write a blog post about [project]" or "turn this into a post".
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\
> A complete fiction-writing studio, run as a team of named specialist agents, that guides an author from a bare idea to a polished prose manuscript. Use this skill whenever the user wants to write, plan, or revise fiction — a novel, novella, short story, or series. Trigger on requests like "help me write a novel", "I have an idea for a story", "develop my characters", "build a world for my fantasy", "outline my plot", "fix this scene", "my dialogue feels flat", "give me beta-reader feedback", or any time the user is doing creative storytelling and would benefit from structured, craft-aware guidance. Also trigger when the user names a studio member (Homer, Aristotle, Fyodor, Tolkien, Scheherazade, Oscar, Max, Virginia, Borges, Bloom) or asks to switch creative roles / bring in a specialist.
> Audit and improve user-provided writing for clarity, concision, and impact. Use when the user asks to audit, review, improve, edit, or rewrite text. Apply seven checks (sentence length, clutter, unsupported modifiers, weasel words, jargon/acronyms, "so what", and flow), then return severity-ranked findings and a full rewrite suggestion.
> Conversational design workshop for substantial work. Interviews the human one question at a time, explores 2-3 approaches with trade-offs, and presents the design section by section for approval before writing the spec. Combines requirements discovery with codebase research and architecture design. Use when the user explicitly requests a spec or when atelier-orchestrator selects a Spec-backed Plan. Ambiguous design or discovery requests route through atelier-orchestrator.
Add a new design.md catalog entry to ko-design-md. Use this skill IMMEDIATELY when the user wants to onboard a new brand into THIS project's catalog — produce services/{slug}.md (Stitch v0.1 format) plus services/{slug}.tokens.json (token-card sidecar) plus public/preview/{slug}/{light,dark}.html plus the OG image. Trigger phrases include "add to design.md catalog", "new design.md entry for X", "onboard X to ko-design-md", "X를 ko-design-md에 추가", "X의 design.md 만들어줘", "/design-md", "X 카탈로그 항목 만들기", or any variant where the user is asking to populate this catalog with a new brand entry. Do NOT use for editing prose in an existing entry, fixing one frontmatter field, generating non-catalog design docs, or working in any other repository. The skill operates only inside the ko-design-md repo and verifies this via `package.json` name.
将经过匿名化的真实经历、观察和观点转化为具有 ALLY 式跨域判断、商业洞察、人格反差和脱口秀节奏的中文内容。用于生成或修改口播稿、短视频脚本、X 长文、标题、开头、结尾、暴论和社交媒体文案；也用于内容“太像AI、太像老师、不够狠、不够好笑、没有本人”时的重写。不得暴露真实姓名或可反向识别的私人信息，不得伪造 ALLY 的个人经历、交易结果或商业事实。
Build and configure the DevExpress Blazor Scheduler (DxScheduler) — a calendar/appointment scheduling component for Blazor Server, WebAssembly, and Hybrid apps. Use for day/week/work-week/month/timeline views; data binding via DxSchedulerDataStorage and AppointmentMappings; appointment creation, editing, deletion, drag-and-drop and resize; recurring appointments (RecurrenceInfo / recurrence rules); resources (rooms/people); labels/statuses; and time/work-time configuration. Also use for DxScheduler, scheduler, calendar, appointment calendar, recurring appointments, and scheduling feature comparisons or migration scenarios.
> ODataStore, and CustomStore. Use when someone asks about binding components to data, loading data from a REST API, configuring an OData endpoint, implementing a custom data source, client-side vs server-side data processing, paging, sorting, filtering, or editing through a store. "custom store", "load function", "byKey", "loadMode", "remoteOperations", "data binding", "server-side paging", "REST API data", "data layer".
> Help developers use the DevExtreme DataGrid component (dxDataGrid) in Angular, React, Vue, and jQuery. Use when someone asks about DataGrid configuration, columns, data binding, editing, filtering, sorting, grouping, selection, paging, scrolling, summaries, export, toolbar customization, column templates, master-detail, remote operations, AI columns, or any scenario involving dxDataGrid or DataGrid. "grid filtering", "grid paging", "grid export", "grid selection", "grid grouping", "row editing", "cell editing", "inline edit", "grid toolbar", "master detail", "remote operations", "AI column", "AI insights", "grid AI".
> Build calendar/scheduling UI with DevExtreme Scheduler. Covers data binding and field mapping, view configuration, appointment types (one-time, all-day, recurring), editing, resources and grouping, remote data with lazy loading, toolbar customization, and templates.
Build .NET applications with the DevExpress AI-Powered Extensions for Office File API to add NLP-powered document processing capabilities — proofreading, translation, and text transformation for Word documents, PDF files, and PowerPoint presentations. Use when integrating AI language models (Azure OpenAI, OpenAI, Ollama, Google Gemini) with document processing workflows, translating documents programmatically, or proofreading documents with AI. Also use when someone mentions "DevExpress AI", "AIIntegration.Docs", "AIDocProcessingService", "proofread Word document", "translate PDF", "AI document processing .NET", or asks about AI-powered document automation with DevExpress. Requires DevExpress v25.2+.
Expert skill for creating and modifying DevExpress XtraReport layout code in Visual Studio and JetBrains Rider — writing and editing *.Designer.cs files, InitializeComponent structure, bands, controls, expression bindings, styles, parameters, and data source wiring. Use this skill whenever someone asks to create a DevExpress report, add controls to a report, modify a *.Designer.cs file, fix designer-generated code, work with XRTable/XRLabel/XRPictureBox/bands, set up data binding expressions, define report parameters, or troubleshoot why a report won't open in the Visual Studio or JetBrains Rider designer. Also use when someone asks about XtraReports InitializeComponent patterns, report band hierarchy, Criteria Language expressions, summary functions, or JetBrains Rider report designer limitations.
DevExpress WinForms PropertyGridControl — displays and edits the public properties of any object. Covers NuGet setup (DevExpress.Win.VerticalGrid, namespace DevExpress.XtraVerticalGrid), assigning objects via SelectedObject and SelectedObjects, Classic vs Office view (ActiveViewType), automatic row generation from reflection, manual rows (EditorRow, CategoryRow, MultiEditorRow), configuring rows (FieldName, Caption, RowEdit, Format, Visible, ReadOnly), DefaultEditors type-to-editor mapping, CustomPropertyDescriptors and CustomRowCreated events, category rows from CategoryAttribute, nested row hierarchy, Office-view tabs via TabPanelCustomize, expanding nested objects via ExpandableObjectConverter, collection editing via OptionsCollectionEditor (UseDXCollectionEditor), EditorAttribute overrides, PropertyDescriptionControl, and the search/find panel (FindPanelVisible, OptionsFind). Use for any WinForms settings panel, inspector window, or configuration editor built on PropertyGridControl.
Expert sales council with 6 advisors (Cialdini, Hormozi, Rackham, Voss, Klaff, Schwartz) for pricing, persuasion, negotiation, copywriting, and pitch strategies.
| iOS/macOS app localization management for Tuist-based projects with .strings files. (3) Syncing translations across languages, (4) AI-powered translation from English to other locales, (5) Checking placeholder consistency (%@, %d), (6) Generating localization reports, (7) Updating Swift code to use localized strings instead of hardcoded text.
> Generate comprehensive App Store listing documentation for iOS/macOS apps with multilingual support. Use when (1) Creating App Store listing content for a new app, (2) Generating multilingual App Store descriptions (English, Simplified Chinese, Traditional Chinese), (3) Preparing app metadata (title, subtitle, keywords, description), (4) Writing release notes or promotional text, (5) User asks to "generate appstore info", "create app listing", or "write app description".
> Use when the user wants to create or bootstrap a project-local CLAUDE.md - the auto-loading "настрой контекст проекта для агента", "забутстрапь CLAUDE.md", "CLAUDE.md для проекта". rules and gotchas as IF-THEN with primacy+recency placement, a work protocol including a keep-docs-live rule, and progressive-disclosure pointers to docs/ and project memory. Extends an existing CLAUDE.md instead of overwriting. Do NOT use for editing arbitrary files, the generic codebase summary that built-in /init produces, or non-CLAUDE.md docs.
> Vermeidet KI-typische Schreibmuster und erzeugt hochwertige Sach- und Fachtexte, die gelesen, gespeichert und erinnert werden. Trigger bei Anfragen wie "schreibe einen Artikel", "erstelle einen LinkedIn-Post", "verfasse einen Blog-Beitrag", "schreibe einen Text ueber", "ueberarbeite diesen Artikel", "schreibe einen Fachtext", "erstelle einen Sachtext", "schreibe etwas ueber". Auch triggern bei "mach den Text menschlicher", "klingt zu sehr nach KI", "natuerlicher schreiben". Basiert auf Wikipedia Signs of AI Writing (August 2025) und Journalismus-Forschung zu Leser-Retention.
Develop software with validation requirements first. Emphasizes writing tests before implementation to guide design decisions.
Expert Architecture Decision Record (ADR) creation and lifecycle management based on Olaf Zimmermann's methodology. Use when creating ADRs, reviewing architectural decisions, evaluating decision readiness, writing MADR templates, assessing decision quality, or managing ADR logs. Covers the full lifecycle from readiness (START criteria) through creation, MADR formatting, completion (ECADR criteria), and ongoing maintenance.
Expert competitive intelligence and strategy guidance for B2B/SaaS companies. Use when conducting competitive research, creating battlecards, analyzing win/loss data, building market landscape maps, positioning against alternatives, handling competitive objections, writing comparison pages, or developing sales enablement for competitive situations. Use for competitive monitoring, feature comparisons, and market intelligence gathering.
Expert event marketing guidance for conferences, webinars, and field programs. Use when planning event strategy, creating booth presence, running webinars, producing virtual events, writing event promotion copy, preparing speakers, designing follow-up sequences, or measuring event ROI. Use for conference sponsorships, trade shows, user conferences, meetups, field marketing, and hybrid events.
Expert PR and media relations guidance for earned media, press coverage, and reputation building. Use when writing press releases, crafting media pitches, developing journalist relationships, planning embargo strategies, managing crisis communication, placing thought leadership, building analyst relations, submitting award applications, or measuring PR coverage. Use for media outreach, press kits, speaking opportunities, and earned media strategy.
Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.
Expert website copywriting for SaaS and B2B companies. Use when writing homepage copy, feature pages, about pages, pricing pages, comparison pages, product tours, integration pages, use case pages, demo/contact pages, or navigation microcopy. Use for website messaging hierarchy, value proposition development, and page-level conversion optimization.
> Load this skill whenever writing, editing, or reviewing any web content, copy, headings, labels, error messages, or instructions. Under no circumstances write inaccessible content — every piece of text must be clear, structured, and usable by people with cognitive, visual, and language differences. Absolutely always apply plain language, logical heading hierarchy, and meaningful link text.
> Load this skill whenever the project involves writing, editing, or reviewing content for a general audience, including UI copy, help text, error messages, documentation, and instructions. Under no circumstances use jargon, complex sentence structures, or unexplained acronyms without providing plain alternatives. Absolutely always target a reading level accessible to the broadest possible audience. Load alongside content-design/SKILL.md for all content work.
Structure, classify, and write documentation using the Diátaxis framework. Use when writing docs, README files, guides, tutorials, how-to guides, API references, or organizing documentation architecture. Also use when asked to improve documentation, restructure docs, decide what type of doc to write, or classify existing content. Covers tutorials, how-to guides, reference, and explanation.