Total 53,207 skills, Documentation & Writing has 1507 skills
Showing 12 of 1507 skills
Generate high-quality, "All-Star" README files for open-source repositories. Use this skill when a user asks to create, update, or improve a README.md file for their project.
Guides users through structured three-stage collaborative documentation workflow including context gathering, iterative refinement, and reader testing. Use when asked to "write a doc", "draft a proposal", "create a spec", "write technical documentation", "create a PRD", or "draft an RFC". Implements systematic approach for PRDs, design docs, decision docs, technical specs, and proposals through clarifying questions, section-by-section iteration, and fresh-eye validation. Works with markdown documentation, technical specifications, and structured writing projects.
Maintain organized project documentation with metadata headers. Update existing docs before creating new ones. Use when writing or editing any project documentation.
Generate technical design documents using a standard template and save them to a group Yuque knowledge base. For group use — stores designs in group repos with review workflow. Requires group Token.
Use this tool when the user explicitly requests "update project guide", "sync guide", or "deposit insights into the guide". It saves newly generated reusable writing insights from conversations to the project guide file in real time, ensuring consistent terminology, stable structure, verifiability and reproducibility. The guide file path must be specified when invoking.
A skill for creating note articles in the interview format of kimny × Claude (AI). It defines release judgment rules based on quality gates (discovery, external anchor, one-sentence test), AIO optimization specifications, and dialogue format rules. Usage scenarios: (1) Creation and rewrite of note articles (2) Structuring interview-style articles (3) Converting historical conversations into articles (4) Article quality check. Example triggers: "I want to turn this into an article", "I want to write on note", "Use interview format", "Can this be made into an article?", "Rewrite the article", "Pass the quality gate", "AIO optimization", "note article"
Create ridiculously good content using Ann Handley's "Everybody Writes" methodology—practical, reader-focused writing that serves your audience and achieves your goals. Use when: **Write blog posts** that engage and convert readers; **Create email content** that gets opened and clicked; **Craft social media posts** that stop the scroll; **Develop website copy** that speaks to your audience; **Write thought leadership** that builds credibility
Remove signs of AI-generated writing from text. Use when editing or reviewing any content to make it sound more natural and human-written. Catches patterns like inflated language, rule of three, em dash overuse, vague attributions, copula avoidance, negative parallelisms, synonym cycling, filler phrases, excessive hedging, and soulless structure. Use when someone says "humanize this", "this sounds like AI", "make this sound human", "remove the AI", "clean this up", "de-AI this", "this reads like ChatGPT", or when reviewing any AI-assisted draft before publishing. Also use as a final pass on content from other skills like boring-remix or social-content. World Code integrated — applies voice.md rules when available.
Diagnose and fix problems in flash fiction and micro fiction. Use when flash fiction feels weak, when writing stories under 1500 words, when working with micro fiction, sudden fiction, or compressed narrative forms.
Use when creating or iterating on a detailed per-subsystem technical design specification from a system spec, before starting OpenSpec workflow. Triggers: "design spec", "subsystem spec", "write the spec for S1", "phase breakdown", "implementation phases", "mid-level spec", "technical design". Encodes opinionated progressive phase discipline with FP progression and contract boundaries. Do NOT use for high-level system specs (use brainstorming) or for OpenSpec artifacts (use openspec directly).
Polish Chinese technical blogs, remove redundant expressions, enhance professionalism and logic, eliminate "AI tone", and ensure code standardization.
Use this skill when writing, reviewing, or improving internal engineering documents - RFCs, design docs, post-mortems, runbooks, and knowledge base articles. Triggers on drafting a design proposal, writing an RFC, creating a post-mortem after an incident, building an operational runbook, organizing team knowledge, or improving existing documentation for clarity and completeness.