Total 43,566 skills, Documentation & Writing has 1289 skills
Showing 12 of 1289 skills
Vellum — Deep navy canvas with warm-yellow italic Cormorant serifs and a single dusty teal accent. A quiet, scholarly aesthetic. Anything that should feel scholarly, literary, and quietly intelligent: research synthesis, white papers, academic and policy briefs, advisory deliverables, longform editorial pieces, founder reflections.
Monochrome — Ivory ledger paper with all-black type; Lora serif headlines, Jost body, no color at all. Anything that should feel like a hand-typeset ledger: user research synthesis, white papers, longform reports, academic and policy briefs, advisory deliverables, bilingual EN/CN reports.
Full content production pipeline from blank page to publish-ready piece. Covers competitive research, content briefs, drafting, SEO optimization, readability scoring, editorial quality gates, and internal linking. Use when writing blog posts, articles, guides, or long-form content end-to-end, or when user mentions write a post, draft an article, create content, content pipeline, editorial workflow, content operations, content calendar management, repurposing, or content at scale.
Advanced 47-marker voice analysis engine — analyzes your writing to build a comprehensive Voice Profile for AuthorClaw
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.
Extract an Allium specification from an existing codebase. Use when the user has existing code and wants to distil behaviour into a spec, reverse engineer a specification from implementation, generate a spec from code, turn implementation into a behavioural specification, or document what a codebase does in Allium terms.
Update repo documentation and agent-facing guidance such as AGENTS.md, README.md, docs/, specs, plans, and runbooks. Use when code, skill, or infrastructure changes risk doc drift or when documentation needs cleanup or restructuring. Do not use for code review, runtime verification, or `agent-readiness` setup.
Story brainstorming capture — minimal notes that preserve creative freedom. Use when exploring narrative ideas, discussing characters, planning chapters, or thinking through story possibilities. Supports interactive conversation and autonomous report mode for fan-out exploration.
Complete coaching skills for Taiwanese nursing staff to write evidence-based nursing reports (evidence-based reading reports, evidence-based case analyses), designed specifically for the N1–N4 nursing advancement system and the review formats of the Taiwan Nurses Association and Taiwan Evidence-Based Nursing Association. This skill must be triggered when users mention terms such as "evidence-based nursing report", "evidence-based case analysis", "evidence-based reading report", "N2 report", "N3 report", "N4 report", "nursing advancement report", "nursing promotion", "PICO", "5A Steps", "CASP Appraisal", "nursing EBP", "EBN", "evidence-based nursing", "evidence-based care", "evidence level", "literature appraisal", or when any nursing staff asks about promotion writing, transforming clinical problems into evidence-based topics, evidence-based literature search strategies, CASP appraisal forms, Oxford evidence levels, APA 7th edition format, applying evidence-based interventions to cases, challenging nursing routines, dispelling nursing myths, etc. Even if users casually say "I need to write a report", "I want to advance to N3", "Help me find a topic", "Help me set up PICO", "How to appraise this literature", this skill should be actively activated to provide complete structures, sentence patterns, and writing strategies with the highest review pass rate.
Generate comprehensive codebase documentation for a repository. Uploads the wiki to view in the Factory app.
Help a researcher plan a paper submission to an academic conference, from target selection through submission day. Use this skill whenever the user is thinking about submitting to a conference (NeurIPS, ICML, CVPR, ICLR, ACL, CHI, etc.), asks about submission timelines, wants to know if their work is ready, wants to do a pre-submission strategy review, or mentions a specific submission deadline. Trigger on phrases like "submit to NeurIPS", "paper deadline", "T-6 months", "submission strategy", "is my paper ready", "conference deadline", or whenever the user is choosing a target venue or building a submission timeline. Also trigger when the user is deciding between venues or considering whether to submit vs. continue developing the work.
McKinsey-style storyline framework for building presentation decks. Use when users need to structure presentations, pitch decks, or strategic communications. Creates logical flow where each storyline becomes a slide title, progressing from problem to solution.