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
用户旅程地图助手适合内容创作者、市场营销、运营、内容媒体在用户提出“用户卡在哪一步”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成转化问题诊断、文案和结构建议、实验清单。
HR 专业助手适合人力资源、manager、运营、software在用户提出“HR 文档怎么更稳”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成转化问题诊断、文案和结构建议、实验清单。
中文润色去AI味 助手适合市场营销、运营、内容创作者、产品在用户提出“怎么去AI味”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成AI 写作痕迹诊断、自然化改写稿、问题片段说明。
销售线索判断助手适合销售、市场营销、运营、software在用户提出“这个线索值得跟吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成转化问题诊断、文案和结构建议、实验清单。
AI 视频剪辑诊断助手适合市场营销、运营、software、内容媒体在用户提出“这段素材怎么剪”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成剪辑结构诊断、片段取舍和时间点建议、字幕配音与平台重构清单。
文案诊断助手适合内容创作者、运营、市场营销、内容媒体在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。
文案诊断助手适合市场营销、运营、产品、software在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。
转化实验助手适合市场营销、运营、产品、销售在用户提出“这个改动值得测吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。
文案诊断助手适合technical、管理者、software、知识库在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。
文案诊断助手适合运营、市场营销、内容媒体、电商在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。
文案诊断助手适合运营、市场营销、retail、内容媒体在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。
爆款文案助手适合内容创作者、运营、市场营销、内容媒体在用户提出“小红书怎么写才有人看”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。
文案诊断助手适合内容创作者、运营、市场营销、内容媒体在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。
Master Shopify Liquid templating language. Use this skill for writing Liquid code, using objects, filters, and tags, accessing product/collection/cart data, creating dynamic content, handling conditionals and loops, and working with Liquid best practices. Essential for theme customization.
Develops consulting proposals and runs the business development pursuit lifecycle from opportunity assessment through oral defense. Use when analyzing an RFP, deciding go/no-go on a pursuit, writing a proposal or executive summary, drafting a Statement of Work, building a pitch deck, articulating a value proposition, or developing win themes and competitive positioning for a client bid. Covers RFP scoring, evaluation-criteria breakdown, SOW scope and commercial terms, and outcome-led proposal structure. Front-loads RFP analysis and proposal writing, the two most common entry points.
Structure complex business problems with hypothesis-driven MECE decomposition and named strategic frameworks (Five Forces, PESTLE, SWOT, 7S, VRIO, Balanced Scorecard, Ansoff, Growth-Share Matrix, Nine-Box, Three Horizons, Value Chain, Business Model Canvas, Strategy Canvas, Platform Strategy). Use when framing an ambiguous question, building issue trees, writing testable hypotheses, designing an analytical workplan, or running framework-based analysis for competitive positioning, market entry, growth strategy, organizational alignment, or portfolio allocation. For broad or high-stakes questions, apply two or more frameworks and synthesize across them. For narrow questions, one framework applied rigorously beats two applied superficially.
Consulting writing standards that enforce tone, sentence discipline, depth calibration, and content integrity across every deliverable. Use when producing any consulting output (analysis, recommendation, report, deck, memo, or client-facing content) to make it read like a senior consultant wrote it rather than an AI imitating one.
Inject creative absurdity to break AI pattern-thinking before creative tasks. Randomly samples surreal micro-stories to spark unconventional thinking. Use before brainstorming, naming, writing, or any task needing fresh perspective.
Read the latest real-time transcription. Use when user asks to see, read, or show a transcription that was captured via live-transcribe. Triggers on: 'תקריא תמלול', 'מה תמללתי', 'התמלול האחרון', 'show transcription', 'what did I say', 'read the transcript', 'מה נכתב בתמלול', 'תראה לי את התמלול'. Also use when user references transcription content without being explicit — e.g. 'summarize what I said', 'translate the transcription'.
Translate video subtitles to any language with native-quality refinement. Full pipeline: transcribe → translate → refine → embed RTL-safe subtitles. Use for: translate video, תרגם סרטון, video translation, foreign subtitles, Hebrew subtitles, translated captions.
Publish posts to WordPress. Use for: publish blog post, upload to WordPress, פרסם בבלוג.
Orchestrate the complete malware analysis lifecycle across triage, dynamic analysis, detection engineering, and report writing. Use as the single entry point for any malware analysis task — routes to specialized sub-skills by file type and phase, carries findings between phases, and supports multi-sample batch workflows.
> Rewrites text to remove AI writing patterns and inject human voice. Use this skill whenever the user asks to "humanize", "de-AI", "make this sound human", "remove AI tells", "fix AI slop", "make it less ChatGPT-y", "rewrite this so it doesn't sound like a bot", or shares text and asks for it to sound more natural, more like them, or less like a press release. Also use proactively when the user is reviewing copy that will be public-facing (blog posts, marketing pages, social posts, emails, READMEs) and you can see obvious AI tells — em-dash overuse, "stands as a testament to", rule-of-three lists, sycophantic openers, generic "in conclusion" wrap-ups. The skill identifies specific patterns from Wikipedia's "Signs of AI writing" page and rewrites them while preserving meaning and tone.
Standards for internationalization and string handling. Apply when touching files with user-facing strings or preparing strings for translation.
Enforces PHP documentation standards for PHPStorm IDE support. Apply when writing or reviewing PHP classes, methods, docblocks, type hints, or magic property annotations.
JavaScript standards and patterns. Apply when writing or modifying JavaScript modules, event handling, lazy loading, scroll behavior, or browser-side utilities.
Build single-purpose, throwaway HTML editors for one specific piece of data — drag-and-drop boards, form-based config editors, side-by-side prompt tuners, dataset curators, annotation tools. Always end with a Submit button (calls `submitToClaude`) so the result can be sent back to the agent. Use whenever the user wants to triage, reorder, edit, annotate, curate, prioritize, or pick values where typing prose would be tedious — Linear tickets, feature flags, prompts, datasets, transcripts, anything. Secret values (API keys, tokens, passwords) are never embedded verbatim — they are masked to references; the artifact and submit payload carry key names and masked previews only.
Practical guidance for choosing, writing, loading, and debugging eBPF programs. Prioritizes correct toolchain and hook selection, map choice, kernel-version fit, verifier triage, and concise production-ready examples using libbpf, ebpf-go, and bpftrace.
Pull version-current Convex docs for the version this project uses — pin the installed version, fetch page-as-markdown or check node_modules types, freshness hierarchy — instead of writing a possibly-stale API from memory.
Use this skill whenever the user says "assess this use case", "score my AI use case", "prioritise these agent ideas", "generate a use case assessment report", or "update my AI use case report" — or when they attach a use-case document, SDR, or prior `*_AI_UseCase_Assessment_Report_*.html` and ask you to assess, strengthen, score, or refresh it. Invoke BEFORE writing any assessment content and BEFORE generating any report.
Use this skill when the user asks to restructure, reorganise, improve, rewrite, tighten, or strengthen a blog post, article, newsletter, essay, or thought-leadership draft.
Use this skill when the user asks to audit, review, score, rationalise, prioritise, refresh, or improve blog posts, article libraries, newsletters, or thought-leadership content.
Use this skill when the user asks to rewrite, humanise, de-AI, polish, localise, or align draft text to a brand voice, house style, named audience, or writing profile.
>- Use this skill whenever you create or edit ANY file for the user in the Copilot Studio container — a document, spreadsheet, slide deck, code file, data export, anything. It keeps your work-in-progress durable and shows the user an updated version after every change, so the two of you refine the same file together across turns — the user sees real progress each round, earlier work is never lost, and neither of you has to start over. Apply it from the very first file you make.
Create, polish, rewrite, review, repurpose, brainstorm, or configure evidence-led LinkedIn posts, captions, comments, hooks, ideas, and conversation-scoped writing profiles from facts, notes, drafts, research, announcements, or lived experience. Use for the initial LinkedIn request and every follow-up clarification, revision, correction, constraint, or preference in the active task.
| Writes natural, first-person spoken presenter scripts (talk tracks) for the slides in a PowerPoint deck, from slide images, or from pasted slide text. Treats existing speaker notes as AUTHORITATIVE when they contradict slide text. Produces one spoken script per slide with delivery cues, calibrated to a target duration and speaking pace, plus a timing table. Use when the user says "write a script for these slides", "I'm presenting slides X-Y, what should I say", "create a presenter script", "turn my speaker notes into a talk track", or "make a 6-minute script for these slides". Do NOT use to create or edit the visible content of slides, to summarize a recorded meeting or transcript, or for general document writing.
>- Use this skill whenever the user shares a Power BI or Analysis Services semantic model (a TMDL export, a BIM/JSON model definition, or a pasted list of tables, relationships, and measures) and asks for a model review, a performance check, or help fixing DAX, before writing or correcting any DAX measure for that model.
Use this skill whenever the user asks to write, rewrite, humanise, de-AI, or polish prose so it doesn't read as AI-generated — or to review a draft for signs of AI writing. Apply it before returning any substantial prose the user will publish.
RouterOS v7 domain knowledge for AI agents. Use when: working with MikroTik RouterOS, writing RouterOS CLI/script commands, calling RouterOS REST API, debugging why a Linux command fails on RouterOS, or when the user mentions MikroTik, RouterOS, CHR, or /ip /system /interface paths. Scope: RouterOS 7.x (long-term and newer) only — v6 is NOT covered and accuracy for v6 problems will be low.
RouterOS hotspot captive portal for wired/wireless access control. Use when: configuring hotspot on RouterOS, setting up captive portal, writing hotspot profiles or instances, configuring walled garden, setting DHCP option 114 (RFC 8910 captive portal URI), integrating RADIUS with hotspot, or when the user mentions /ip/hotspot, walled-garden, hotspot profile, or captive portal on MikroTik.
RouterOS firewall filter, NAT, mangle, and address-list configuration. Use when: writing firewall rules in RouterOS, configuring NAT, setting up address-lists or interface-lists, writing idempotent firewall scripts, configuring DNS redirect or port forwarding, or when the user mentions /ip/firewall, chain=forward, chain=input, connection-state, address-list, interface-list, or layer7-protocol on MikroTik.
RouterOS /app YAML format for container applications (7.21+ builtin app, 7.22+ custom YAML creation). Use when: writing or validating RouterOS /app YAML files, working with MikroTik container apps, building docker-compose-like definitions for RouterOS, creating /app store schemas, debugging /app validation errors, or when the user mentions /app, tikapp, or RouterOS container YAML.
RouterOS scripting language and CLI configuration idioms for .rsc files and interactive commands. Use when: writing or reviewing RouterOS scripts, scheduler/netwatch/on-event snippets, idempotent CLI config, :local/:global/:foreach/:do syntax, [find] selectors, print as-value handling, script permissions, or when the user mentions .rsc, RouterOS script, scripting tips, or CLI config automation.
Keep a Changelog format guidelines and entry writing best practices. Use when writing changelog entries, updating CHANGELOG.md, or following Keep a Changelog specification.
Keep a Changelog format guidelines and entry writing best practices. Use when writing changelog entries, updating CHANGELOG.md, or following Keep a Changelog specification.
Keep a Changelog format guidelines and entry writing best practices. Use when writing changelog entries, updating CHANGELOG.md, or following Keep a Changelog specification.
Keep a Changelog format guidelines and entry writing best practices. Use when writing changelog entries, updating CHANGELOG.md, or following Keep a Changelog specification.
Keep a Changelog format guidelines and entry writing best practices. Use when writing changelog entries, updating CHANGELOG.md, or following Keep a Changelog specification.