mastodon-style
Use when drafting or editing a post (toot) for Mastodon / the fediverse.
- License 许可
- Apache-2.0
- 所属仓库
- vercel/eve
- 最近更新
- 2026-11-15
- Stars
- ★ 5.9k
- Forks
- 656
01 前言 Front Matter
- description
- Use when drafting or editing a post (toot) for Mastodon / the fediverse.
02 资源文件 3
- 参考文档references/banned-words.json289 B
- 参考文档references/best-practices.md2.9 KB
- 参考文档references/post-specs.md1.9 KB
03 SKILL.md 正文
Mastodon voice & style
When writing or editing a post for Mastodon:
- Fediverse culture is earnest and community-first, with no ads and no algorithm pushing reach. Write like a member of the community, not a brand broadcasting to it: lead with value or a real question, never announcement-speak or growth-hacking.
- ~500 characters (the common default; some instances allow more). No need to fill it.
- Link directly to the source. Every link counts as a flat 23 characters, so don't use a shortener; Mastodon's docs discourage it.
- Add alt text to every image. It's a strong, near-universal accessibility norm, not a nicety.
- Use a content warning (CW) for sensitive, spoiler, or long content so it collapses behind a short label; it's considerate, not censorship, and doubles as a subject line.
- Topical hashtags drive discovery: public posts surface in search mainly via their tags (full-text search is opt-in). Use a few relevant ones in CamelCase (e.g.
#WebDev) so screen readers parse the words; a handful, not a wall, and never numbers only. - The feed is chronological, so write each post to stand on its own.
Structure
- Open: the honest hook or the question, line one.
- Body: the substance, plainly.
- Close: the takeaway or a genuine invitation, then a few CamelCase hashtags.
References
references/best-practices.md: researched tactics as a checklist, with sources.references/post-specs.md: hard constraints (character limit, links, CW, alt text, hashtags).references/banned-words.json: the words to avoid. Thelint_against_styletool checks a draft against this list (surfacemastodon), so run the tool rather than reading the file.
General prose quality (AI-tell phrases to avoid, plain-English word swaps) is covered by the writing-quality skill; apply it to every draft alongside this one.
04 同仓库更多 Skills
writing-quality
The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.
writing-quality
Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.
seo-aeo-best-practices
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity/functions, @sanity/blueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.
portable-text-serialization
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.
portable-text-conversion
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext/markdown (markdownToPortableText), @portabletext/block-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.