Total 52,553 skills, Documentation & Writing has 1495 skills
Showing 12 of 1495 skills
For when you're asked to write a design doc or specification, especially after a brainstorm or feature design session.
Read and understand novel texts, and summarize them into smooth story outlines. Suitable for initial novel screening and generating 500-800 word story outlines
Review technical prose for accessibility, jargon density, and gatekeeping language. Ensures content passes the 'Grandma Test' and avoids 'obviously', 'simply' (Gatekeeping). Use this to refine technical explanations.
Best practices for documenting APIs and code interfaces, eliminating redundant documentation guidance per agent.
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.
Short Web Fiction Deconstruction. Analyze the narrative structure, emotional curve, twist techniques, and hook design of hit short stories. Trigger methods: /story-short-analyze, /短篇拆文, "Help me deconstruct this short story", "Analyze this story"
Story decision capture and mining — recording what was decided, what was rejected, and why, inline with the artifacts they relate to. Use whenever story direction is being chosen, brainstorm options are being narrowed, character or world choices are being made, or past decisions need to be recovered from session history.
Write or update external guide documents for the project —— dev-guide (for contributors / integrators / downstream developers) and user-guide (for end users). The output is stored in the project's docs/ directory, maintained alongside the code, and searchable by search tools. Difference from libdoc: guidedoc is task-oriented ("How to do Y with X"), while libdoc is reference-oriented ("What each part of X looks like"). Trigger scenarios: When the user says "write documentation", "developer guide", "user guide", or proactively push when feature-acceptance is completed.
Use when you need durable, repo-specific context (architecture, domain model, how a flow works, standards, gotchas, decisions) before engineering or reviewing, or when you have learned something worth recording. Reads and writes an in-repo Obsidian knowledge base (docs/<repo>-vault/), synced by git.
Write personalized cold outreach emails to hiring managers and founders — specific, human, not a pitch deck
Rewrite Python docs and docstrings from source code. Use when Codex needs to refresh the docs.
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.