Agent Skill 目录与安装教程 — ClawHub、SkillsMP 与开源 Skill

io.github.joe-bell/cva/writing-guidelines

Review or write docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", "check this page against the writing handbook" — and proactively whenever writing or editing content under docs/src/content/docs/, since that's this repo's default docs style.

io.github.compozy/compozy/writing-tech-post

Authors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.

io.github.compozy/compozy/writing-skills

Author, refactor, and debug agent skills. Use when creating a new skill from scratch, pruning or restructuring a bloated SKILL.md, tightening a skill description's triggers, or diagnosing bundled references the agent ignores. Don't use for agent instruction files like CLAUDE.md or AGENTS.md (use agent-md-refactor), general documentation, or READMEs.

io.github.PostHog/posthog/writing-skills

Guide for writing PostHog agent skills — job-to-be-done templates that teach agents how to use MCP tools to achieve a goal. Use when adding new product functionality that agents should know how to work with, creating a new skill, or updating existing skills in products/*/skills/.

io.github.ArcReel/ArcReel/writing-great-skills

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

io.github.openclaw/clawhub/writing-evals

Scaffolds evaluation suites for the Axiom AI SDK. Generates eval files, scorers, flag schemas, and config from natural-language descriptions. Use when creating evals, writing scorers, setting up flag schemas, or configuring axiom.config.ts.

io.github.ChromeDevTools/devtools-frontend/devtools-ux-writing-refactor

Refactor user-facing UIStrings and localization comments in a DevTools module folder according to UX writing guidelines (child task of b/40799900). Use when simplifying wording, checking sentence case, or improving L10n comments in UIStrings for a specific folder or issue. Don’t use for general code changes or non-UIStrings files.

io.github.dotnet/skills/writing-mstest-tests

Write, create, modernize, or fix comprehensive MSTest unit tests with MSTest 3.x/4.x APIs. USE FOR: write, create, review, or modernize MSTest tests and assertions, better MSTest assertion than Assert.IsTrue, replace hard cast with IsInstanceOfType, MSTest assertion APIs (Contains, ContainsSingle, HasCount, IsEmpty, IsNotEmpty, DoesNotContain, AreSame, IsNull, StartsWith, EndsWith, MatchesRegex, IsGreaterThan, IsLessThan, IsInRange), swapped/reversed Assert.AreEqual args (Expected/Actual backwards), replace ExpectedException with Assert.Throws, data-driven (DataRow, DynamicData, ValueTuples), lifecycle (TestInitialize, TestCleanup, TestContext), async and cancellation tests, conditional execution/retry/cleanup (OSCondition, Retry), parallelization (Parallelize/DoNotParallelize), MSTest.Sdk setup, MSTESTxxxx analyzer fixes. DO NOT USE FOR: test quality audits (use test-anti-patterns), running tests (use run-tests), MSTest version migration (use migrate-mstest skills), xUnit/NUnit/TUnit, or non-.NET languages.

io.github.PostHog/posthog/writing-tests

Gates whether a new test should exist and forces it to be efficient, protecting CI from low-value test bloat. Use before adding or substantially changing any pytest, Jest, or Playwright test — whenever an agent or engineer is about to write tests for a new feature, bugfix, or PR. Front-loads the value bar (every test must catch a realistic regression no existing test already catches; test behavior through the public interface, not implementation details; collapse near-duplicates into parameterized cases) and the efficiency bar (deterministic, isolated, fast; pick the cheapest test level; Django TestCase over TransactionTestCase; no sleeps, no real network). Includes a "don't write it" decision tree. For fixing an existing flaky test use `/fixing-flaky-tests`; after this gate says a Playwright test is warranted, use `/playwright-test` for mechanics.

io.github.c15t/c15t/writing-docs

Author or edit c15t documentation in docs/**/*.mdx — the source for both the c15t.com site and the docs bundled into published packages. Use when writing guides, integration pages, reference docs, changing package-bundled docs (packages/*/docs, packages/*/AGENTS.md), or fixing docs lint failures.

io.github.actualbudget/actual/writing-release-notes

Use whenever adding, writing, drafting, or fixing a release note in the Actual Budget repo. This is the changelog entry that ships with a code change, living as a Markdown file in `upcoming-release-notes/`. Trigger for asks like "add a release note", "write the changelog entry", "add the release note for this PR/change", "create the upcoming release note", or any time finishing a user-facing change in this repo where a release note is the natural next step. These notes are published for humans to read, so they must be short, plain-language, and free of technical detail. Writing them like a commit message or with implementation jargon produces entries that get flagged and rewritten in review.

io.github.vinvcn/mattpocock-skills-zh-CN/writing-fragments

一种追问式会话，用来从用户那里挖掘片段，也就是各类写作素材（主张、小场景、尖锐句子、半成形想法），并追加到单一文档中，作为未来文章的原始素材。适用于用户想在施加结构前发展想法，或提到 “fragments”、“ideate”、“raw material” 写作素材时。

io.github.vinvcn/mattpocock-skills-zh-CN/writing-beats

以自选路径风格，把文章塑造成一段节拍旅程。用户从原始素材中选择起始节拍，你只写这一段，然后提供下一步转向选项，逐个节拍推进，直到文章自然结束。适用于用户已有原始素材，并想把它组装成叙事而不是论证时。

io.github.vinvcn/mattpocock-skills-zh-CN/writing-shape

通过对话会话，把一份原始素材 Markdown 文件塑造成文章：起草候选开头，逐段扩展，并在每一步讨论格式（列表、表格、提示块、引用）。适用于用户有一堆笔记、片段或粗稿，并希望把它变成可发布作品时。

io.github.nexu-io/open-design/writing-guidelines

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".

io.github.crbnos/carbon/writing-skills

House guide for creating or editing agent skills in this repo (.ai/skills/). Use when writing a new skill, restructuring an existing one, or reviewing skills for quality. Covers the frontmatter contract, the install wiring, the house template, and the weak-executor writing rules every Carbon skill follows.

io.github.nukeop/nuclear/writing-plugins

Use when writing, scaffolding, or modifying Nuclear plugins. Covers plugin structure, manifest, entry point, provider types, available APIs, and publishing. Trigger phrases include "create a plugin", "write a plugin", "plugin scaffold", "streaming provider", "metadata provider".

io.github.handsontable/handsontable/writing-docs-pages

Use when creating or editing documentation pages in docs/content/guides/ - covers YAML frontmatter, page structure, framework-specific example embedding, writing style, and sidebar registration

io.github.code-yeongyu/lazycodex/writing-design-plans

Use when you have a design brief or strategy and need to break implementation into reviewable chunks — creates step-by-step plans with verification criteria for each task

io.github.Klotzkette/claude-fuer-deutsches-recht/writing-dokumente-intake

Dokumentenintake: sortiert Dokumente, erkennt Lücken, ordnet Beweiswert und formuliert gezielte Rückfragen.

io.github.TriliumNext/Trilium/writing-unit-tests

Use when writing, extending, or debugging Vitest unit tests anywhere in the Trilium monorepo — Preact components, jQuery widgets, client services, or the server/trilium-core backend. Covers how to render components (zero new deps), the easy-froca/becca fixtures, supertest API patterns, the honest coverage config, running a single test, and the known gotchas.

io.github.marin-community/marin/writing-style

Marin house writing style. Use when drafting or revising Marin-authored prose.