Total 50,341 skills, Documentation & Writing has 1451 skills
Showing 12 of 1451 skills
Rewrite "abstract conclusions from the author's perspective" into "specific pain point entrances from the reader's perspective", to avoid articles being too broad and empty, concept-first, and causing readers to swipe away. Suitable for WeChat Official Account articles, long-form articles, AI/platform/cognition/workplace/creator-oriented articles.
Use idiomatic doc comments to provide a professional API surface.
Use when the user needs professional email drafting, tone adjustment, template creation, or communication strategy for business correspondence. Trigger conditions: draft professional email, adjust email tone, create email template, write cold outreach, compose follow-up, draft escalation email, write apology email, craft meeting request, compose status update, plan email communication strategy.
This skill should be used when the user asks to "create a character", "update a character", "add a character", "build a family tree", "character relationships", "character timeline", "character arc", "character profile", or needs to manage characters in a story project.
This skill should be used when the user asks to "start a new story", "initialize a story project", "create a story", "new book", "set up a story", or wants to begin a new fiction writing project from scratch.
Use this skill whenever creating or editing any markdown file. Do not wait for an explicit request — if a markdown file is being created or edited, this skill applies.
When the user wants to create, optimize, or audit a HowTo section block—an in-page block of ordered steps with optional Schema.org HowTo JSON-LD. Also use when the user mentions "HowTo section," "how-to section," "steps section," "quick start," "walkthrough," "tutorial block," "3 steps," "N steps," "simple steps," "tutorial steps," "step-by-step block," "HowTo schema," "HowTo JSON-LD," "instruction steps," "numbered steps SEO," "horizontal tabs for steps," or "procedure section." This skill is for a section inside a page, not a full page template—use article-page-generator, docs-page-generator, or tools-page-generator for page-level layout. For FAQ Q&A blocks, use faq-page-generator. For structured data details beyond HowTo, use schema-markup. For article body copy only, use article-content.
Revise brand and corporate communications into clear, respectful, considered writing. Use when editing or drafting marketing copy, product descriptions, brand guidelines, corporate communications, emails, or any customer-facing content. Inspired by Aesop's philosophy: formality with warmth, clarity over cleverness, precision over excess.
Copywriting and content creation standards for website pages, blog posts, and all written copy. Covers headlines, ledes, readability, niche vocabulary, scannable formatting, and persuasive structure. Cross-cutting skill — apply whenever...
Use when the user mentions cover letters, job applications, HR questions, recommendation letters, job application Q&A, self-introductions, applications, or asks for help responding to recruiter questions or preparing application materials.
Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification.
Handle common employee questions and requests through structured FAQ systems, escalation paths, and self-service resources