Fiction, scripts, blogs, editing, and proofreading (1.8K skills)
Create a writing scaffold teaching the genre conventions specific to an academic discipline. Use when students write lab reports, historical essays, or other discipline-specific text types.
The English summary is being prepared. Showing the original description.
Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.
The English summary is being prepared. Showing the original description.
When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. For writing new copy, see copywriting.
The English summary is being prepared. Showing the original description.
Expert guide for Monte Carlo's push ingestion model. Use this skill whenever a customer or engineer mentions: pushing data to Monte Carlo, the IngestionService, pycarlo push APIs, build me a collection script, push metadata/lineage/query logs, invocation_id tracing, custom lineage nodes or edges, deleting push tables, or any question about why pushed data is not showing up. Also trigger when they ask to generate code that collects metadata, table schema, row counts, freshness, lineage, or query history from any data warehouse or data source and sends it to Monte Carlo. If the user mentions any warehouse, database, or data platform alongside any Monte Carlo topic, this skill is almost certainly relevant.
The English summary is being prepared. Showing the original description.
AIが生成した日本語を推敲するスキル。利用者が yomiyasu の名前を出して頼んだとき（「/yomiyasu」、「$yomiyasu:yomiyasu」、「yomiyasu で推敲して」など）と、スキルを使った日本語の推敲をはっきり頼んだときだけ使う。CLAUDE.md、AGENTS.md、カスタム指示などで yomiyasu を使うよう求められているときも、名前を出して頼まれたものとして扱う。名前を出さずに日本語の文章を書かせる依頼や、コード、設定、ドキュメントの更新では使わない。意味と条件を保ち、不自然な比喩、曖昧な主述関係、不要な装飾やコピー調を整える。使用トリガー：'/yomiyasu', 'yomiyasuで推敲して', 'この文章を推敲して', '文章を自然にして', 'AI臭さを消して', '文章をリライトして'。
The English summary is being prepared. Showing the original description.
Medium-native long-form research, author-assistance, writing, editing, review, topic discovery, publication matching, and packaging workflow. Use when creating, outlining, researching, revising, auditing, or packaging Medium stories, essays, tutorials, reviews, explainers, comparisons, case studies, publication submissions, Medium 长文, Medium 选题, Medium Topics, or Medium publishing packs that need original author perspective, narrative craft, relevant topics, responsible AI disclosure, and reader-centered distribution readiness.
The English summary is being prepared. Showing the original description.
SEO-friendly article writing, audit, and humanization workflow for Markdown content. Use when creating, outlining, editing, auditing, rewriting, or quality-checking blog posts, tutorials, comparisons, listicles, explainers, FAQ sections, excerpts, SEO titles, meta descriptions, tags, or Google-friendly content briefs that need clear topics, natural keyword use, on-page SEO review, reader-friendly prose, and iterative optimization.
The English summary is being prepared. Showing the original description.
シミュレーションと数理最適化（モンテカルロ / Monte Carlo / 離散事象シミュレーション / DES / 待ち行列 / リスク分析 / シナリオ分析、線形計画 / LP / 整数計画 / MIP / スケジューリング / 配送計画 / VRP / 割当 / メタヒューリスティクス）を 実行したら必ずセットで出す図と値のルーター。SeedSequence.spawn, scipy.stats の rvs, simpy, SALib, pulp, LpProblem, mip.Model, ortools, pywraplp, cp_model, pyomo, cvxpy, linprog, milp がコードに現れたとき、または ユーザーが「シミュレーションして」「モンテカルロで見積もって」「待ち時間をシミュレートして」「最適化して」 「最適な割当を求めて」「スケジュールを組んで」と言ったときに使う。収束・標準誤差・ソルバー status・制約違反・ 感度分析に言及がなくても適用する。SKILL.md のルーティング表で手法を特定し、対応する references/<手法>.md を 読んでから実行する。MCMC は statistical-inference-diagnostics、ML のハイパラ探索は predictive-modeling-diagnostics を使う。
The English summary is being prepared. Showing the original description.
View markdown files with calm, book-like reading experience via HTTP server. Use for long-form content, documentation preview, novel reading, report viewing, distraction-free reading.
The English summary is being prepared. Showing the original description.
Script the first 1-3 second TikTok hook: the spoken line, the on-screen text, and the opening visual firing at once so the viewer cannot swipe. Picks a 2026 hook formula (cold-open result, pattern interrupt, number reveal, open-loop question, relatable call-out, story) by goal of completion, saves, comments, or shares. The single biggest retention lever on TikTok. Use to script a hook from a video idea. Not for the caption (use tt-caption-writer) or scrubbing a script (use tt-humanizer).
The English summary is being prepared. Showing the original description.
英文网文出海写作（Wattpad / Royal Road / Webnovel / Radish / KDP）。当用户要写英文小说、出海英文平台、把中文故事改写成英文原生（不是翻译腔）、问英文平台怎么写/选哪个、或要去掉英文里的"中国网文翻译腔/AI腔"时使用。按英文网文规则产出像当地作者写的英文。
The English summary is being prepared. Showing the original description.
中文网文错别字校对与敏感词/违禁内容过审检查。当用户要查错别字(的地得/在再/做作等)、查敏感词违禁词、投稿前过审自检、问"这段会不会被屏蔽/被标红/过不了审"、或要"像番茄那样标出错字并给一键替换建议"时使用。逐句扫描，给出"原词→建议词"对照供作者一键替换。
The English summary is being prepared. Showing the original description.
中文网文平台趋势与喜好实时调研。当用户想知道当下番茄/晋江/起点/UC/知乎盐选/Webnovel 平台流行什么题材、热门标签、上榜套路、读者偏好，或要做选题前的市场调研、追风口时使用。优先用联网搜索拉取最新数据，给可执行的选题/标签建议。
The English summary is being prepared. Showing the original description.
Write Persian with Persian words. Use when writing, editing, translating or reviewing Persian (Farsi) prose — articles, documentation, posts, essays, UI copy — to replace loanwords with Persian equivalents while leaving technical terminology, proper nouns and code untouched. Also use when the user asks for پارسی سره, سرهنویسی, فارسیسازی, or "make this text more Persian".
The English summary is being prepared. Showing the original description.
Storyboard a papercut script before any code. Writes the Camera / Cut table, one block per scene with frame-level events on each stressed word, the SFX plan and the proof beat. Use for "storyboard this script" or "plan the camera moves and cuts".
The English summary is being prepared. Showing the original description.
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.
The English summary is being prepared. Showing the original description.
Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"
The English summary is being prepared. Showing the original description.
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
The English summary is being prepared. Showing the original description.
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"
The English summary is being prepared. Showing the original description.
Reconstruct an open-source project's growth channels, key content, and stage-by-stage attribution from GitHub history and public web evidence. Use this skill when asked to research GitHub star growth, identify launch and amplification channels, explain viral milestones, find representative posts or videos, compare Product Hunt/Show HN/Reddit/KOL impact, or produce an evidence-backed OSS growth attribution report.
The English summary is being prepared. Showing the original description.
Engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with trend tracking. Per-person breakdowns, shipping streaks, and actionable improvements. Use when asked for "retro", "weekly review", "what did we ship", or "engineering retrospective".
The English summary is being prepared. Showing the original description.
Write, restructure, classify, and review documentation with the Diataxis framework. Use when the user asks to create, improve, audit, or reorganize documentation of any kind: knowledge bases, help centers, onboarding guides, process docs, manuals, runbooks, product or API docs, tutorials, how-to guides, references, explanations. Also use when the user mentions Diataxis, docs taxonomy, or documentation architecture, or asks why a document feels confusing. Also use for Simplified Technical English (ASD-STE100) or controlled-language rewrites of English technical docs. Not for marketing, legal, sales, press, or fiction writing unless the user wants a Diataxis-style analysis.
The English summary is being prepared. Showing the original description.
Act as the team's Scrum Master of record, or copilot to a human one: plan sprints, run daily pulses, close sprints, prepare and follow up retrospectives, track and escalate impediments, and detect process anti-patterns across sprint history. Use whenever the user asks for Scrum or agile process help, in any language — "plan the sprint", "chuẩn bị retro", "how is the sprint going", "our velocity dropped", "track this blocker", "the same problem keeps coming back" — even without the word "Scrum", and whenever `_project/scrum-master/` exists and the question touches sprints, ceremonies, impediments, or team process health. Not for delivery dates and budget (project-manager) or deciding what to build (product-manager).
The English summary is being prepared. Showing the original description.
Inspect and explain bmad-loop run artifacts under `.bmad-loop/runs/`. Use for live health checks ("is it stuck?", "is the loop alive?", "what is the agent doing?") and post-run forensics ("what happened?", "why did story X fail?", "where did the tokens go?"). Also triggers on "monitor/check/summarize the loop", "why did the run pause?", Vietnamese "theo dõi bmad loop", "phân tích run", "đọc log của run", and equivalent requests in other languages. Use only for bmad-loop's own run artifacts, not application runtime logs or CI-provider build logs.
The English summary is being prepared. Showing the original description.