From engineering
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/engineering:documentationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write clear, maintainable technical documentation for different audiences and purposes.
Write clear, maintainable technical documentation for different audiences and purposes.
Lark-native execution (depth core: LARK-PATTERNS, LARK-RECIPES, LARK-FUSION). Durable docs (READMEs, runbooks, API refs, onboarding guides, architecture docs) belong in Wiki, not chat (P8): before writing,
lark_doc_searchfor an existing page to update instead of duplicating ("link, don't duplicate"); create the page withlark_wiki_node_create(space_id, title)and fill the body with the lark-doc skill (DocxXML — block JSON by hand is brittle). Transient artifacts (generated diagrams, exports, attachments) go to Drive vialark_drive_upload. When a doc names owners/escalation contacts, resolve them toopen_idwithlark_contact_search(P1) so @-mentions resolve. Announce a new/updated doc with a shortlark_im_sendlink to the channel — but the doc lives in Wiki, the message is just a pointer. For a wiki-wide tidy-up delegate to doc-restructure; to fill a named template, doc-from-template.
npx claudepluginhub larkcowork/lark-cowork-plugins --plugin engineeringGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.