Documents skills
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
signal-green-pptx
Reusable fixed-style PPTX generation skill for the Signal Green Atlas visual brand — fluorescent green (#0CDA76) dominant background, black (#000000) typography and rules, black-and-white imagery only, bold avant-garde editorial atlas aesthetic, oversized uppercase grotesk headlines, strict two-column information grids, sharp rectangular photo windows, black circular bullets, deliberate asymmetry, widescreen 16:9 editable .pptx output. Use this skill whenever the user mentions Signal Green Atlas, asks for a fluorescent-green editorial presentation, wants an avant-garde atlas or guidebook-style deck, requests a bold black-and-green presentation, or needs a deck using strict information grids and monochrome imagery. Also trigger for 'signal green', 'signal green atlas', 'fluorescent green deck', 'atlas pptx', 'black and green presentation', 'avant-garde atlas deck', 'guidebook style slides', or 'editorial atlas presentation'.
video-to-subtitle-summary
Use when user provides a short video platform URL or local video/audio file and wants subtitles/AI summary, or when user asks to list their own AI Douyin historical tasks. Triggers on v.douyin.com, xhslink.com, bilibili.com, b23.tv, YouTube URLs, local .mp4/.mp3/.wav files, or task history requests.
codex-imagen
Generate or edit raster images by calling the ChatGPT/Codex hosted image_generation flow with local Codex or OpenClaw OAuth credentials, then save decoded image files for OpenClaw and other agent workflows.
lina-openspec-archive-consolidate
按功能职责对已归档的 OpenSpec 迭代内容进行聚合分类和高价值摘要压缩，并要求插件相关聚合归档和 specs 目录以 <plugin-id> 前缀区分主框架内容。 必须用户手动触发，禁止自动触发该技能。
docs-lead
Use whenever the user mentions docs, the manual, documentation, terminology, translations, or screenshots — including indirect mentions like "이 PR 문서 영향 봐줘", "문서 점검", "용어 통일", "/docs-lead", or any phrasing about updating the Backend.AI WebUI user manual under packages/backend.ai-webui-docs/. Single entry point that runs docs-lint diagnosis, surfaces a prioritized queue via AskUserQuestion, and orchestrates the four docs worker subagents (planner / writer / screenshot-capturer / reviewer) through approval gates.
improve-documentation
Reviews and improves the pg_trickle documentation in docs/. Checks accuracy against source code, fixes broken links, removes duplication, identifies gaps, and enforces consistency. Use when auditing docs quality, preparing a release, or after significant code changes. Produces a prioritised proposal and optionally writes it to a file.
improving-docs
Audit, restructure, or incrementally improve an existing body of documentation using Diátaxis. Use when the task is to assess docs, untangle mixed-up content, or raise quality across a project rather than write a single new piece. Covers the iterative workflow and how to judge documentation quality. Load the `diataxis` skill to pick a mode, and the writing-* skills to act on each piece.
readout
Produce a polished, self-contained HTML "readout" document under ~/.readouts (with an auto-maintained index page), either by snapshotting the findings accumulated in the current conversation or — when invoked fresh, e.g. "/readout on how github webhook events are processed" — by sharpening scope with clarifying questions and researching the codebase before documenting. The work runs in a child agent so the main conversation's context stays clean. Use whenever the user invokes /readout, says "write this up", "turn this into a doc/page", "make a readout", or asks for a readable, shareable document capturing findings or explaining how something works.