Yao process documentation expert. ALWAYS invoke this skill when the user needs to discover available processes, read process signatures, or validate process names. Do not guess process APIs — use this skill first.
docs-page
docs-page is an open-source docs skill for Claude Code and compatible agents, published by nexu-io. Its author describes it as: “A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial".”. The project has 89k stars on GitHub and is available under the Apache-2.0 license. Add it to your setup with `/plugin marketplace add nexu-io/open-design`.
What docs-page does
Produce a single, three-column documentation page in one HTML file.
Installation
Add docs-page to your agent with:
/plugin marketplace add nexu-io/open-designAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for docs-page is organised into these sections:
- Workflow
- Output contract
When to use it
Reach for docs-page when you want docs help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear Apache-2.0 license — safe to read and adapt
- Ships in nexu-io/open-design, an established project with 88,812 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does docs-page do?
- A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial".
- How do I install docs-page?
- Run /plugin marketplace add nexu-io/open-design in your agent, then reload your skills. Review the source at https://github.com/nexu-io/open-design before installing.
- Is docs-page free to use?
- Yes. docs-page is free and open source under the Apache-2.0 license, so you can read, run, and adapt it within that license's terms.
- Where does docs-page come from?
- docs-page ships inside nexu-io/open-design, a repository that contains 61 catalogued skills in total. The repository's 88,812 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Docs →
Automated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks, React/UI conventions, and tests. Supports single-agent review with interactive fix selection or multi-agent reviewer-verifier review with risk-based auto-fix. To diagnose gaps in the skill after a review session, run `/gh-pr-review diag`.
三栏文档页: 侧导航 + 正文 + 右 TOC
Use only when a developer explicitly asks to clean, prune, tidy, or organize DeepChat SDD documentation after implementation and validation. Scans docs/features, docs/issues, and docs/architecture; prefers multi-agent review when available; removes completed issue docs when a linked GitHub issue is closed or implementation and validation evidence proves the bug no longer exists, drops stale plans and legacy task files from completed feature or architecture goals, and deletes obsolete feature or architecture docs.
Use before substantial DeepChat code, configuration, documentation, test, build, feature, issue, refactor, or architecture changes that need a durable RFC and an explicit execution path. Skip trivial style fixes, small localized logic changes, routine docs edits, and simple bugs unless the developer asks for SDD. Use plan.md as the only separate tracker when needed, default to implementation-first validation, and ask before optional GitHub issue sync unless the developer explicitly requested sync.