Total 50,320 skills, Documentation & Writing has 1450 skills
Showing 12 of 1450 skills
Writes delta specifications with requirements and Given/When/Then scenarios for a change. Trigger: /sdd-spec <change-name>, write specs, functional requirements, specification phase.
Assess documentation quality across readability, consistency, audience fit, and prose clarity. Produces a scored review with actionable findings. This skill should be used before releases, during doc reviews, or when documentation feels unclear or inconsistent.
Draft patent claims for an invention. Use when user says "撰写权利要求", "draft claims", "写权利要求书", "claim drafting", or wants to create patent claims. The core skill of the patent pipeline.
Zero-context verification that every number, comparison, and scope claim in the paper matches raw result files. Uses a fresh cross-model reviewer with NO prior context to prevent confirmation bias. Use when user says "审查论文数据", "check paper claims", "verify numbers", "论文数字核对", or before submission to ensure paper-to-evidence fidelity.
One-stop skill for the project architecture center — draft new architecture documents, refresh existing architecture documents, or conduct an architecture health check. Automatically determine the mode based on user input: `new` (draft)/ `update` (refresh to the latest code status)/ `check` (view only, generate issue list). The `check` mode has three sub-goals: consistency within a single feature design, alignment between design and code, and consistency among multiple documents under `easysdd/architecture/`. Single-target rule — only modify one document or check one target at a time. Trigger scenarios: User says "fill in an architecture doc", "draft an architecture document", "refresh the architecture directory", "write down the structure of this module", "conduct an architecture check", "is the design internally consistent?", "does the plan match the code?", "are there conflicts among several documents in the architecture folder?", or when it is found in the feature-design / feature-acceptance / implement phase that an architecture action needs to be performed first before proceeding.
One-stop skill for the project architecture center — draft new architecture documents, refresh existing ones, or conduct an architecture health check. Automatically determine the mode based on user input: `new` (draft)/ `update` (refresh to latest code status)/ `check` (review without modification, generate issue list). The `check` mode has three sub-objectives: consistency within a single feature design, alignment between design and code, and consistency among multiple documents under `codestable/architecture/`. Single-target rule — only modify one document or check one target at a time. Trigger scenarios: User says "fill in an architecture doc", "draft an architecture document", "refresh the architecture directory", "write down this module structure", "conduct an architecture check", "is the design internally consistent?", "does the plan match the code?", "are there conflicts among several documents in the architecture folder?", or when an architecture action is required before proceeding during the feature-design / feature-acceptance / implement phases.
Write multi-chapter books (technical, tutorial, monograph, etc.) end-to-end. Handles outline planning, per-chapter drafting that stays coherent across long manuscripts, chapter review, and final HTML/PDF build. Trigger when user mentions "写书", "写一本书", "出书", "技术书", "book writing", "逐章写作", "O'Reilly", "mdbook", or wants to author a multi-chapter book.
Use when the user needs to plan, de-risk, or ground a software engineering / computer science undergraduate thesis from a real codebase before final writing. Trigger for requests such as "根据项目写毕业论文", "先做论文大纲", "用真实项目材料规划论文", "检查论文是否脱离代码", "根据检测报告降查重", "根据AIGC报告改写定稿", "继续在手改初稿上改", or when an existing draft thesis must be reworked against a school format sample. Produces an evidence-backed outline, chapter rewrite plan, figure plan, and handoff package for academic-paper-composer.
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.
Structured workflow for fact-checking claims in journalism. Use when verifying statements for publication, rating claims for fact-check articles, or building pre-publication verification processes. Includes claim extraction, evidence gathering, rating scales, and correction protocols.
Structured producer who turns research insights into production-ready slide deck outlines and scripts. Triggers: 'create slides', 'write webinar script', 'build slide deck', 'webinar outline', 'produce webinar', or when user asks for the Producer.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision. Follows the standard ADR format with context, decision, and consequences. Invoked when the user says "write an ADR", "document this decision", or "create an architecture record".