Total 44,022 skills, Documentation & Writing has 1301 skills
Showing 12 of 1301 skills
Create the perception of cultural depth through strategic juxtaposition of familiar and unfamiliar elements. Use when settings feel shallow, when you need centuries of implied history without exposition, or when worldbuilding lacks the texture of real cultural evolution.
Create comprehensive troubleshooting guides, FAQ documents, known issues lists, and debug guides. Use when documenting common problems, error messages, or debugging procedures.
Create comprehensive API reference documentation with OpenAPI/Swagger specs, REST endpoints, authentication, examples, and SDKs. Use when documenting REST APIs, GraphQL APIs, endpoint documentation, or OpenAPI specifications.
Use this when the user wants to review, polish, or proofread articles. Triggers include requests such as "polish my article", "check this", "revise my writing", "proofread this", "look over my article"
Use this when the user explicitly requests to "write/polish NSFC grant abstract", "generate Chinese and English abstracts", or "translate Chinese abstract to English abstract". Output both Chinese and English versions: The English version must be a faithful translation of the Chinese version (no additional information, no omission of key constraints). The default limit for Chinese abstract is ≤400 characters (including punctuation), and ≤4000 characters for English abstract (including punctuation); the final limit shall prevail as specified in `skills/nsfc-abstract/config.yaml:limits`. Also output **title suggestions**: By default, provide 1 recommended title + 5 candidate titles with justifications (the quantity shall follow `config.yaml:title.title_candidates_default`). Output method: Write the results to `NSFC-ABSTRACTS.md` in the **working directory** (the file name shall follow `config.yaml:output.filename`), which includes in order `# Title Suggestions`, Chinese abstract, English abstract, and length self-check. ⚠️ Not applicable in the following cases: - The user only wants to translate a general text unrelated to grant proposals (direct translation is required instead) - The user only wants to write the main body of project justification/research content/research foundation (use the corresponding NSFC series skill instead)
Main entry for cross-platform content creation. Coordinates the entire creation process: Research → Image Selection → Writing → Polishing → Platform Conversion. Used for creating articles, developing content, conducting topic research, and publishing to Zhihu/Xiaohongshu/WeChat Official Accounts.
Use when drafting patent applications, writing claims, analyzing prior art, or responding to office actions - covers USPTO practice, claim strategies, and specification requirementsUse when ", " mentioned.
Use when understanding legacy or undocumented systems, creating documentation for existing code, or extracting specifications from implementations. Invoke for legacy analysis, code archaeology, undocumented features.
Create comprehensive developer onboarding documentation including setup guides, README files, contributing guidelines, and getting started tutorials. Use when onboarding new developers or creating setup documentation.
Expert technical writing guidelines for creating clear, in-depth developer tutorials and documentation with practical, implementable knowledge
Creates 2 backend docs (api_spec.md, database_schema.md). L3 Worker invoked CONDITIONALLY when hasBackend or hasDatabase detected.
Write and maintain knowledge base articles from resolved support issues. Use when a ticket has been resolved and the solution should be documented, when updating existing KB articles, or when creating how-to guides, troubleshooting docs, or FAQ entries.